Skip to main content
PATCH
Reopen a conversation

Authorizations

x-api-key
string
header
required

Your workspace API key. Create one in Settings → API Keys; the plaintext value is shown once and never again.

Keys are scoped. A key needs conversations:send to send, conversations:read to read threads and messages, templates:read to list templates, and channels:read to list channels. A key missing the scope for an endpoint gets 403.

The CRM endpoints use the same resource:action form: leads:read, leads:create, leads:update, leads:delete, customers:read, customers:create, customers:update, customers:delete, customers:manage.

Several resources have no scope of their own and borrow one:

Grant only what the integration needs — a key that only sends notifications should hold conversations:send and nothing else.

X-Tenant-Id
string
header
required

Your workspace UUID. Required on every request in addition to x-api-key.

It does not select the workspace — data access is always scoped to the workspace that owns the API key, and a mismatched value cannot read anyone else's data.

Path Parameters

id
string<uuid>
required

Response

The reopened conversation.

id
string<uuid>
channel_id
string<uuid> | null

Which connected account this thread arrived through.

external_thread_id
string

The contact's identifier on the platform (WhatsApp JID, Telegram chat id, …).

status
enum<string>
Available options:
open,
closed,
snoozed,
pending
contact_id
string<uuid> | null
customer_id
string<uuid> | null
lead_id
string<uuid> | null
assigned_to_user_id
string<uuid> | null

The agent who owns this thread, if any.

last_message_at
string<date-time> | null
is_group
boolean

True for WhatsApp group threads.

group_subject
string | null
group_participant_count
integer | null
created_at
string<date-time>
updated_at
string<date-time>