Skip to main content
GET
Read one conversation answer record

Authorizations

x-api-key
string
header
required

Path Parameters

route_name
string
required
message_id
string
required

Response

Success.

data
ConversationRecordView · object
required

A conversation answer record as a read door serves it. An admin read carries every field; the caller-scoped read withholds the route-key's internal detail — channel, our_identity, provider_message_id, callback_url, error, outbound_message_ids and attempts are present only for an admin caller and are absent from the caller_view subset.