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

Request Body

The request body must be a JSON object with the following fields:

Required Fields

Optional Fields

Request Example

Response

Success Response

Status Code: 200 OK

Response Fields

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 at an approval step or has already been approved/rejected.

422 Validation Error

Returned when the request body is invalid or variables don’t match the expected schema.

500 Internal Server Error

Returned when submission fails due to a server error.

Notes

When a task is approved, the workflow continues to the next step. When rejected, the workflow typically ends or follows a rejection path defined in the workflow.
Use the comment field to document the reasoning behind approval or rejection decisions for audit and compliance purposes.
Ensure the task is at an approval step before calling this endpoint. Check the current_step_type from the Get Task endpoint.

Use Cases

This endpoint is useful for:
  • Automated approvals - Integrate approval workflows with external systems
  • Custom approval UIs - Build custom interfaces for task approval
  • Conditional approvals - Approve tasks based on external business logic
  • Bulk approvals - Process multiple approval requests programmatically