`GET /api/conversations/{id}` — one thread with a page of its messages.
const url = 'https://example.com/api/conversations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = {method: 'GET', headers: {cookie: 'supacloud_session=<supacloud_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/conversations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --cookie supacloud_session=<supacloud_session>Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Conversation id
Query Parameters
Section titled “Query Parameters”Messages per page (default 50, max 200)
Message offset
Responses
Section titled “Responses”The thread.
GET /api/conversations/{id} body — the head plus a page of its thread.
object
One row of the conversations board.
object
provider | local — WHICH SYSTEM owns the assignment. The UI must not
offer a local reassign control on a provider row; that assignment lives in
Chatwoot/Intercom and a local write would be silently overwritten on the
next delivery.
One message in a thread.
object
contact | agent | bot | system. agent is a human replying in the
provider’s own UI; bot is one of our own agent replies.
inbound (from the contact) | outbound (from an agent).
An internal note rather than a customer-visible message.
Gapless position in the thread — the ordering key. Deliberately exposed: the FE detects a gap (a dropped page) by sequence, not by timestamp, because provider clocks are not monotonic.
Total messages in the thread (the paging companion to messages).
Examplegenerated
{ "conversation": { "assigned_to": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "assignment_origin": "example", "channel": "example", "contact_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "created_at": "2026-04-15T12:00:00Z", "external_id": "example", "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "last_message_at": "2026-04-15T12:00:00Z", "status": "example", "subject": "example" }, "messages": [ { "author_kind": "example", "author_name": "example", "body": "example", "direction": "example", "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "occurred_at": "2026-04-15T12:00:00Z", "private": true, "sequence_num": 1 } ], "total_messages": 1}Authentication required
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}No such conversation in this workspace
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Structured server error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}