Skip to main content
SMS conversations are stored as SMS-channel call records. Use these endpoints to build inboxes, customer timelines, exports, and conversation cleanup flows.
Authentication uses the standard flexible auth path: API key, JWT bearer token, or dashboard session.

Conversation Object

List Conversations

Deleted/archived SMS threads are excluded.

Get Conversation

Returns one conversation object or 404.

Get Messages

Response
Returns recent related call/SMS records for the same customer and assistant context.
Response

Export Conversation

Supported format values: txt, csv, json. This endpoint returns a file download with Content-Disposition, not a JSON wrapper.

Archive Conversation

Archiving an SMS conversation:
  • Marks the SMS call record as deleted via call_meta.sms_deleted.
  • Deletes chat messages for the SMS conversation.
  • Deletes SMS audit and message logs linked to that conversation.
  • Clears related Redis keys on a best-effort basis.
  • Allows future messages between the same numbers to start a fresh conversation.
Response

SMS Sessions

Session endpoints expose Redis-backed active SMS session state.
GET /api/v1/sms-sessions/ returns:
Response
DELETE /api/v1/sms-sessions/ clears sessions:
Response