Skip to main content

Endpoint

Authentication

This endpoint requires authentication via API key. Include your API key in the X-API-Key header:

Path Parameters

Query Parameters

Request Example

Response

Success Response

Status Code: 200 OK

Response Fields

Step Run Object Fields

Variable Object Fields

Used in both step_run.variables and variables_to_approve.

File Object Fields

Only populated when include_files=true. Contains presigned download info for file-type variables.

Error Responses

401 Unauthorized

Returned when authentication fails. See the authentication errors section for details.

404 Not Found

Returned when the task doesn’t exist or you don’t have access to it.

409 Conflict

Returned when the task is not currently at a pending approval step.

422 Validation Error

Returned when request parameters are invalid.

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 this endpoint before calling Approve Task to verify the task is ready for approval and inspect what variables need review. Set include_files=true when you need to download file attachments for review.
Presigned download URLs in the files array expire. Check the expires_at field and request new URLs if they have expired.

Use Cases

This endpoint is useful for:
  • Custom approval UIs - Build approval interfaces that display full context including variables and files
  • Pre-approval validation - Check eligible approvers and pending variables before submitting a decision
  • 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