Tasks API
Tasks are the to-dos and follow-ups attached to your account — optionally linked to a contact, deal, or campaign. They move through the stages of your task boar
Tasks API Tasks are the to-dos and follow-ups attached to your account — optionally linked to a contact, deal, or campaign. They move through the stages of your task board (your kanban columns) and have a type and priority . This guide covers managing them over the API. Base URL — https://api.relaytiv.com/v1 Authentication — your API key (see Authentication ) Errors & paging — see Errors & Pagination All examples below show the ?apiKey= query form in cURL and the X-API-Key header in JavaScript and Python — either works on every endpoint. The task object { "id": "tsk_abc123", "title": "Call Jane about her quote", "description": "She asked for pricing on the annual plan.", "type": "to_do", "priority": "high", "stage": "stage-1", "due_date": "2026-06-15T09:00:00.000Z", "contact": "contacts/uid_whatsapp_15551234567", "campaign": "campaigns/abc123", "tags": ["sales"], "notes": "", "source": "api" } type — to_do , faq_update , or your configured task types (see List task types ). priority — none , low , normal , high , or urgent . stage — the id of a stage on your task board (see List task stages ). When omitted on create, the task lands in your first stage. Create a task POST /tasks — only title is required. 📝 Note: due_date accepts an ISO 8601 timestamp. contact_id , deal_id , and campaign_id link the task to those records. assigned_to is a team member's user id. cURL curl -X POST "https://api.relaytiv.com/v1/tasks?apiKey=YOUR_API_KEY" \ -H "Content-Type: application/jso