Endpoint
Authentication
This endpoint requires an OAuth access token. Send it as a bearer token:tasks:read
Path Parameters
Query Parameters
Request Example
Response
Success Response
Status Code:200 OK
Response Fields
Step Run Object Fields
Variable Object Fields
Used in bothstep_run.variables and variables_to_approve.
File Object Fields
Only populated wheninclude_files=true. Contains presigned download info for file-type variables.
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 anX-API-Key was
sent instead of a bearer token. See OAuth error responses.
403 Forbidden
Returned when the token lacks the required scope:404 Not Found
Returned when the task does not exist.409 Conflict
Returned when the task is not currently at a pending approval step.422 Validation Error
Returned when request parameters are invalid.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
For sequential approval workflows,
eligible_approvers_active shows the approver(s) whose turn it
is now, while next_eligible_approvers shows who comes after. For parallel approval workflows, all
eligible approvers appear in eligible_approvers_active and next_eligible_approvers is empty.Use Cases
This endpoint is useful for:- Custom approval UIs - Build approval interfaces that display full context including variables and files
- Pre-approval validation - Confirm the current user is an eligible approver before submitting
- File review workflows - Download file attachments for external review before approving
- Approval routing - Determine sequential vs parallel approval order and who is next in line