Documentation Index
Fetch the complete documentation index at: https://orbit-docs.devotel.io/llms.txt
Use this file to discover all available pages before exploring further.
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:/v1/conversations
Authentication: API key (X-API-Key) or session JWT.
Lifecycle
| Method | Path | Purpose |
|---|---|---|
GET | /v1/conversations | List all conversations |
GET | /v1/conversations/{id} | Get a single conversation |
GET | /v1/conversations/{id}/messages | Get messages in a conversation |
POST | /v1/conversations/{id}/reply | Reply in the conversation’s channel |
POST | /v1/conversations/{id}/assign | Assign to an agent or team |
PUT | /v1/conversations/{id}/tags | Update tags |
POST | /v1/conversations/{id}/close | Close (resolved) |
POST | /v1/conversations/{id}/snooze | Snooze until a future time |
POST | /v1/conversations/{id}/reopen | Reopen a closed/snoozed conversation |
POST | /v1/conversations/bulk | Bulk action across many conversation IDs |
AI handoff & copilot
For AI-led conversations, Orbit provides explicit handoff mechanics so a human agent picks up exactly where the AI left off.| Method | Path | Purpose |
|---|---|---|
POST | /v1/conversations/{id}/copilot/suggest | Suggest the next reply + next-best actions |
POST | /v1/conversations/{id}/handoff | Hand off from AI to a human agent |
POST | /v1/conversations/{id}/handoff/resolve | Mark a handoff as resolved (closes the AI pause) |
Example — reply on whatever channel the conversation is on
WHATSAPP_OUTSIDE_24H_WINDOW error and you’ll need to send an approved template via the Messaging API instead.
See also
- Inbox API — collaboration, saved views, routing rules, macros
- Webhooks → conversation events