Get Conversation by ID
Messaging
Get Conversation by ID
Retrieve a single SMS conversation and its messages by its ID
GET
Get Conversation by ID
Enterprise Feature - SMS is only available on Enterprise plans. Contact your Bland representative for access.
Headers
Your API key for authentication
Path Parameters
The unique ID of the conversation to retrieve.
Response
The full conversation object, including its messages.
The unique ID of the conversation.
ISO timestamp for when the conversation was created.
ISO timestamp for when the conversation was last updated.
The user’s phone number in the conversation.
The assistant’s phone number in the conversation.
Variables stored on the conversation, or
null if none.The current node ID in the pathway, if any.
The UUID of the current pathway being used in this conversation.
The specific version of the pathway being used (e.g., “latest”, “v1.0”).
ISO timestamp when the conversation timed out due to inactivity, if applicable. When set, the conversation will not respond to new user messages but will store them.
Whether the conversation is still active.
The resolved delivery channel for this conversation:
"sms", "rcs", or "whatsapp". Determined based on the input channel and whether the messaging service supports RCS.AI-generated conversation summary, produced when the conversation ends and a summary prompt is configured on the SMS number.
Extracted citation variable values from the conversation transcript. Keys are variable names, values are the extracted data. Only populated when citation schemas are configured.
The first successful outcome result tag. Provides a quick classification of the conversation outcome without needing to inspect the full
disposition_logs.An array of message objects in the conversation, sorted chronologically.
Unique ID of the message.
ISO timestamp of when the message was created.
The message body.
Sender phone number.
Receiver phone number.
Either
"USER" or "AGENT" to indicate who sent the message.Delivery status of the message. Possible values:
"pending", "queued", "sent", "delivered", "read", "failed", "undelivered". The "read" status is available for RCS and WhatsApp channels.Twilio error code if the message failed, otherwise
null.An array of outcome run results for this conversation. Each entry represents one outcome that was evaluated when the conversation ended.
The ID of the outcome that was run.
The version of the outcome’s transformation code that was executed.
The execution status.
"COMPLETE" indicates the outcome ran successfully, "ERROR" indicates a failure.The extracted outcome values, or
null if the run failed.Error message if the outcome run failed, otherwise
null.Execution time in milliseconds.
null on success, or a list of error objects if a failure occurred.Docs for agents: llms.txt