Approve Task

Endpoint

POST /v2/tasks/{task_id}/approve

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:

Authorization: Bearer your_access_token

Required scope: tasks:write

The decision is submitted as the access token’s user, who must already be an eligible approver on the step. If they are not, the request returns 400 - it will not add them to the approver list.

Path Parameters

Parameter	Type	Required	Description
`task_id`	integer	Yes	Unique identifier for the task

Request Body

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

Required Fields

Field	Type	Description
`approved`	boolean	Whether the task is approved (`true`) or rejected (`false`)

Optional Fields

Field	Type	Description
`comment`	string	Optional comment explaining the approval or rejection decision
`variables`	array	Ignored on this endpoint
`user_email`	string	Ignored on this endpoint. The decision is always attributed to the access token’s user

variables is accepted for compatibility but not applied - the approval step does not collect variable values. Send any values you need through the workflow’s own steps instead.

Request Example

curl -X POST "https://platform.chamelio.ai/v2/tasks/12345/approve" \
  -H "Authorization: Bearer your_access_token" \
  -H "Content-Type: application/json" \
  -d '{
    "approved": true,
    "comment": "Contract terms look acceptable. Approved for signing."
  }'

import requests

task_id = 12345

url = f"https://platform.chamelio.ai/v2/tasks/{task_id}/approve"
headers = {
    "Authorization": "Bearer your_access_token",
    "Content-Type": "application/json"
}

payload = {
    "approved": True,
    "comment": "Contract terms look acceptable. Approved for signing."
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())

const taskId = 12345;

const response = await fetch(
  `https://platform.chamelio.ai/v2/tasks/${taskId}/approve`,
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer your_access_token',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      approved: true,
      comment: 'Contract terms look acceptable. Approved for signing.'
    })
  }
);

const data = await response.json();
console.log(data);

Response

Success Response

Status Code: 200 OK

{
  "task_id": 12345,
  "status": "in_progress",
  "approved": true,
  "message": "Approval submitted successfully"
}

Response Fields

Field	Type	Description
`task_id`	integer	ID of the task
`status`	string	Updated task status (typically `"in_progress"` as workflow continues to next step)
`approved`	boolean	Whether the task was approved or rejected
`message`	string	Success confirmation message

Error Responses

400 Bad Request

Returned when the access token’s user is not an eligible approver on the step, or when the 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.

{
  "detail": "Invalid request"
}

{
  "detail": "client_credentials tokens are not associated with a user"
}

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.

{
  "detail": "Invalid access token"
}

403 Forbidden

Returned when the token lacks the required scope:

{
  "detail": "Insufficient scope; this endpoint requires: tasks:write"
}

Or when the user may not act on this task:

{
  "detail": "You do not have access to this resource"
}

404 Not Found

Returned when the task does not exist.

{
  "detail": "Not found"
}

409 Conflict

Returned when the task is not at an approval step or has already been approved or rejected.

{
  "detail": "The task is not in a state that allows this operation"
}

422 Validation Error

Returned when the request body is invalid.

{
  "detail": [
    {
      "loc": ["body", "approved"],
      "msg": "field required",
      "type": "value_error.missing"
    }
  ]
}

429 Too Many Requests

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

{
  "detail": "Rate limit exceeded"
}

500 Internal Server Error

Returned when submission fails due to a server error.

{
  "detail": "Failed to submit approval"
}

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.

Call Get Approval Details first. It returns the eligible approver emails, so you can confirm the token’s user is among them before submitting.

Use the comment field to document the reasoning behind approval or rejection decisions for audit and compliance purposes.

Use Cases

This endpoint is useful for:

Custom approval UIs - Let approvers decide from your own interface, recorded as themselves
Chat and email integrations - Approve from Slack, Teams, or a mobile app
Auditable decisions - Guarantee the approver on record is the real person who decided

Overview

API Key Access

OAuth App Access

Webhooks

Endpoint

Authentication

Path Parameters

Request Body

Required Fields

Optional Fields

Request Example

Response

Success Response

Response Fields

Error Responses

400 Bad Request

401 Unauthorized

403 Forbidden

404 Not Found

409 Conflict

422 Validation Error

429 Too Many Requests

500 Internal Server Error

Notes

Use Cases

​Endpoint

​Authentication

​Path Parameters

​Request Body

​Required Fields

​Optional Fields

​Request Example

​Response

​Success Response

​Response Fields

​Error Responses

​400 Bad Request

​401 Unauthorized

​403 Forbidden

​404 Not Found

​409 Conflict

​422 Validation Error

​429 Too Many Requests

​500 Internal Server Error

​Notes

​Use Cases

Endpoint

Authentication

Path Parameters

Request Body

Required Fields

Optional Fields

Request Example

Response

Success Response

Response Fields

Error Responses

400 Bad Request

401 Unauthorized

403 Forbidden

404 Not Found

409 Conflict

422 Validation Error

429 Too Many Requests

500 Internal Server Error

Notes

Use Cases