Skip to main content
Every messaging account’s inbox is exposed as conversations and messages, in the same shape whatever the platform underneath.
Paths live under /v1/inbox/conversations. The older /v1/conversations paths still serve the exact same responses — nothing to migrate.

List conversations

The response is { "data": [ … ], "pagination": { … } }. Each row carries its id, the contact, the account, the platform, the last message and whether it’s unread. Conversations and messages use id (not _id).

Read a conversation

Mark it read once your user has seen it:

Reply

Send an Idempotency-Key header so a network retry never sends the message twice. Sending is immediate and public to the recipient — there’s no undo. Show the exact text to whoever is approving it before you call this.

Start a conversation

The identifier depends on the platform: a phone number in international format on WhatsApp, an IGSID on Instagram. There’s also a direct path that bypasses the inbox entirely, when you hold the platform id and don’t need the thread:

The 24-hour window

Meta — Instagram, Facebook Messenger and WhatsApp — only accepts free-form messages within 24 hours of the contact’s last message. Past that:
  • WhatsApp: send an approved template.
  • Instagram / Facebook: the window is closed. The single exception is a private reply to a comment, once per comment, within 7 days — which is what comment → DM automations run on.

Sync from the platform

Inbound messages arrive by webhook in real time. When the inbox looks incomplete — a freshly connected account, or webhooks that were misconfigured for a while — pull the current state from the platform:
Returns how many conversations and messages were synced.

Reacting to inbound messages

Subscribe to message.received rather than polling the list. The payload carries the conversation and the message, so you can route it straight into your own system — see Webhooks.
Telegram inbound messages aren’t ingested yet, so Telegram bots don’t appear in the inbox. X DMs need elevated paid API access and aren’t exposed. Broadcasts exclude X for the same reason — see Campaigns.