Skip to main content
A thread is one conversation between an end user and your agent. Threads are created automatically when you send a message without a thread_id — the created id comes back in the response, and you pass it on subsequent messages to continue the conversation.
Coming from an earlier integration? Threads are what used to be called tasks, and there is no longer a separate “create task” step.

Read a thread’s transcript

cURL

GET /messaging/v1/threads/{threadId}/messages

Returns the thread’s full transcript in chronological order — one entry per message, both the user’s and the agent’s.

Welcome message

Open your conversation UI with the agent’s configured greeting — before any message has been sent:
cURL

GET /messaging/v1/welcome-message

Returns the welcome message of your agent’s live version:
200

Follow-up suggestions

Generate suggested next prompts from a context you provide — useful for offering the end user quick next questions:
cURL

POST /messaging/v1/followup-suggestions

context
object
The context the suggestions are generated from — any JSON object describing where the user is in your product or conversation.
200
The agent’s replies also carry followup_suggestions inline — this endpoint is for generating suggestions outside a turn, e.g. when the user lands on a page.

Managing threads

Listing, filtering, renaming, and auditing threads across your organization live on the management surface — see Management → Threads.