Skip to main content

Conversations API

A single thread per contact-channel pair, regardless of which channel the message came in on. Conversations are how the inbox UI groups inbound messages, AI replies, and agent replies — and how you’d integrate the same lifecycle into your own UI. Base path: /api/v1/conversations Authentication: API key (X-API-Key) or session JWT. This page is a curated map of the whole surface, grouped by task. Every endpoint below is live and callable. For per-endpoint request/response schemas and copy-pasteable code samples in six languages, see the full Conversations endpoint reference.

Read & inspect

Lifecycle

Assignment & routing

assign targets an individual agent only — pass agent_id: null to unassign. To route a conversation into a team’s queue instead of to one person, use handoff with a target_queue; omit it to place the conversation in the org-wide queue.

AI handoff & copilot

For AI-led conversations, Orbit provides explicit handoff mechanics so a human agent picks up exactly where the AI left off.

Custom fields, translation & sharing

Followers

Side conversations

Loop an external vendor or subject-matter expert into a child thread tied to the parent conversation, without exposing it to the customer.

Example — reply on whatever channel the conversation is on

The reply is sent over the same channel the conversation is on (SMS, WhatsApp, email, …). For WhatsApp specifically, the 24-hour customer-care window is enforced — if the contact hasn’t messaged you in 24 hours, the API will return a WHATSAPP_OUTSIDE_24H_WINDOW error and you’ll need to send an approved template via the Messaging API instead.

See also