Skip to main content

Endpoint

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:
Required scope: tasks:read

Path Parameters

Request Example

Response

Success Response

Status Code: 200 OK

Response Fields

Task Object Fields

Step Run Object Fields

Variable Object Fields

Used in both step_runs[].variables and the top-level variables array.

Error Responses

400 Bad Request

Returned when the access token has no user behind it. client_credentials tokens act as the admin who created the application, so this applies only to tokens issued before application creators were recorded.

401 Unauthorized

Returned when the access token is missing, unknown, revoked, or expired, or when an X-API-Key was sent instead of a bearer token. See OAuth error responses.

403 Forbidden

Returned when the token lacks the required scope:
Or when the user may not access this task:

404 Not Found

Returned when the task does not exist.

429 Too Many Requests

Returned when your organization exceeds its per-minute request limit.

500 Internal Server Error

Returned when the request fails due to a server error.

Notes

The task is read as the access token’s user. You get 403 unless that user is a participant on the task, an acl_read collaborator on it, or a collaborator or manager on its workflow.
Poll this endpoint periodically to monitor task progress.
Use current_step_id and current_step_type to understand which step the workflow is currently executing. If current_step_type is "approval", use the Get Approval Details endpoint for more information about the approval step.

Use Cases

This endpoint is useful for:
  • Status monitoring - Track workflow progress and completion
  • Variable retrieval - Get values collected during workflow execution
  • Step history - Review which steps have run and what data each collected
  • Debugging - Understand where a workflow is stuck or failed
  • User notifications - Display current workflow status in your application