Skip to main content

Overview

The Conversations API gives you programmatic access to Sendora’s unified inbox (Unibox): the place where all inbound replies across SMS, email, LinkedIn, and WhatsApp land in a single thread per lead. With the API you can:
  • List all conversations with filtering and pagination
  • Read full message threads for any lead
  • Send a message to a lead on any text channel
  • Set the traffic-light signal (green / yellow / red) to classify intent
  • Have a chat agent start a conversation

Listing conversations

One endpoint lists conversations and returns a single thread.
Query parameters:

Reading a thread

Get all messages for a specific lead in chronological order:
Returns a ConversationThread with the lead’s info and all messages:
If the most recent conversation was a voice call, call_recording contains the recording URL and transcript.

Sending a message

Send a message to a lead on any text channel:
Sendora chooses the sending account for you: the account the lead’s existing conversation runs on, and otherwise one picked by Sendora’s sender rotation.

Replying by email

An email reply goes into one exact thread, because a lead can have several. Read the thread with GET /api/v1/public/conversations?lead_id=LEAD_ID, take the conversation_id of the message you are replying to, and send it with the reply:
An email reply without conversation_id is refused instead of being sent to a guessed thread. The reply keeps the thread’s subject. conversation_id is ignored on the other channels.

Sending a one-off email to any address

To email someone who is not in a thread yet, send to, subject and content to the same endpoint. Sendora creates the lead if the address is new and checks the do-not-contact list first.
delivery has two options:
  • scheduled (default): the mail engine sends at a human-paced time shortly after you call, which protects your sender reputation. Opens and replies are tracked. The response has status: "queued".
  • instant: the email is handed to the mail server right away and is not tracked. The response has status: "sent". Use it for time-sensitive messages, and keep volume low.
Send an Idempotency-Key header so a retry never sends twice. Template variables are not filled in a one-off email, so write the final text.
A workspace that is restricted for trust and safety reasons cannot send messages through the API, just as it cannot send from the inbox. Reading conversations and setting the traffic light keep working.
Voice (VOICE) is not supported via the conversations API, outbound calls are initiated through campaigns or the voice agent dashboard.
Valid channels: SMS, EMAIL, LINKEDIN, WHATSAPP

Having a chat agent start the conversation

Instead of sending text yourself, name a chat agent and the agent writes the first message on SMS or WhatsApp, then carries the conversation:
See Chat agents for the rules that can refuse a start.

Setting the traffic light

Classify a lead’s intent to help prioritize follow-up. The signal is a field on the lead, so set it with Update lead:
Accepted values are green, yellow, red and unknown, in any case. Sendora’s AI classifier sets this automatically when a reply arrives, but you can override it here.

Webhook integration

Subscribe to reply.received to trigger your workflow the moment a lead responds:
The webhook payload includes channel, message_preview, and lead_id so you can load the full thread on demand.