Resource

Tasks

Operator follow-ups, manual or flow-spawned.

Endpoints · 3

Read · GET

Fetch data — accept query filters, return JSON. Read-only and idempotent.

GET
List tasks
/v1/tasks
/v1/tasks

Create · POST

Create new records. Send a JSON body; the response is the created resource.

POST
Create a task
/v1/tasks
/v1/tasks
POST
Mark a task complete
/v1/tasks/{id}/complete
/v1/tasks/{id}/complete
Idempotent. Completed tasks linger in the table indefinitely (no auto-delete).

Object shape

The tasks object

Tasks object

{
  "id": "5a8b3c2d-9e4f-1a2b-3c4d-5e6f7a8b9c0d",
  "title": "Call Ankit to confirm Tuesday demo",
  "description": "Confirm the 4 PM IST slot on the Tuesday before send.",
  "status": "open",
  "priority": 1,
  "due_at": "2026-05-04T16:00:00.000+05:30",
  "assignee_id": "b1f2c3d4-5678-90ab-cdef-1234567890ab",
  "contact_id": "c2a8a93a-2f1c-4c5b-8f3d-9c1e3a8b5d12",
  "suggested_action": "call",
  "flow_enrollment_id": null,
  "created_at": "2026-05-01T10:00:00.000+05:30"
}

Was this page helpful?

Your vote stays in this browser. We'll use it to prioritise rewrites.