Connect the process that is specific to your team.
Use the supported REST resources and signed events to connect internal systems, with scoped access, delivery visibility and the permissions your workspace requires.
Get started freeSome workflows need more than a ready made connection. The public API provides supported workspace resources for your own integration, while webhooks let a service react to changes. Choose suitable credentials, check the reference and account for permissions, pagination and delivery retries. Building and operating the external system remains part of your team's implementation.
Explore the details
- REST API and OpenAPI reference
- Consult the public API reference to identify supported resources, request shapes and responses before connecting a service to the workspace.
- Scoped, expiring and revocable tokens
- Create a token with the available read or write scope, choose an expiry and revoke the credential when the integration no longer needs access.
- Workspace locations and task resources
- Work with supported spaces, folders, lists and tasks, using the documented operations rather than relying on an interface route as an API.
- Comments, fields, tags and task details
- Use documented comment, custom field, tag, checklist, relationship and attachment operations to connect the detail that makes a task useful.
- Time, goals, views, documents, chat and templates
- Connect supported time, goal, view, document, chat and template resources through the documented endpoints, checking which operations each resource actually offers.
- People, teams and audit information
- Access supported people, team and audit resources with the account permissions and plan availability required for that information in the workspace.
- Signed events and delivery health
- Subscribe to supported signed webhooks, verify incoming signatures and inspect delivery health when an external endpoint is failing or retrying.
- OAuth apps and workflow connectors
- Configure supported OAuth applications and automation connections so external services can request the appropriate authorised access to the workspace.
- Permissions, pagination and rate limits
- Respect endpoint permissions, follow pagination and handle documented rate limits and errors when building a service that works reliably with the API.
Create work from an internal request system
Use a scoped credential to create a task after an internal request is approved. Subscribe to the relevant signed event when its status changes, verify the signature and handle repeated delivery IDs. Keep the external process linked through the task identifier.
An example you can adapt to your own team.
Make space for the work that matters.
Bring your next project into Talqivo. Start with a task, invite your team and build from there.
Get started free