Skip to main content
GET
List Conversations
This is the inbox behind the Tuco unibox. One call gives you the conversation list with each thread’s messages, so you can build your own inbox UI.

Endpoint

  • Method: GET
  • Path: /api/unibox/conversations
  • Auth: Authorization: Bearer tuco_xxxxxxxxxxxxx (workspace key)

Two things that surprise people

A conversation is keyed by recipient, not by lead. There is no leadId on a conversation — it is identified by the phone number or email address at recipient. That is also why the deep link is ?conversation=<address>. The thread holds what actually went out or came in. Messages still queued, pending or scheduled are deliberately not in it — a conversation shows history, not intent. Read the outbound queue from /api/unibox/scheduled instead. If you expect “everything for this contact” here, you will wrongly conclude the follow-ups were lost.

Pagination

Filters

All are query params and all intersect.

Response

The pending queue

Anything not yet sent:
To stop it going out, see Cancel Pending Messages.
  • GET /api/unibox/tags — the tags you can filter on
  • GET /api/unibox/custom-properties — the property keys for propertyKey
  • GET /api/replies — a flat, paginated feed of inbound replies
  • POST /api/unibox/mark-read, /archive, /flag, /send-reply — act on a conversation
GET /api/unibox/stream (server-sent events) is browser-only and rejects API keys. For server-side updates use webhooks — message.reply fires on every inbound message.

Error responses