Get conversation details
Fetch a single conversation by ID, scoped to the partner the API key belongs to. Use the include query parameter to expand related resources (assignee, sites, etc.) inline. customProperties holds the conversation’s custom property values keyed by property id, and is always returned. Requires the conversation:read scope.
Authorizations
Send the API key in the x-api-key header.
Path Parameters
"57f2d879-20f8-4106-9abb-44fa099e0448"
Query Parameters
Comma-separated relations to expand
"sites,participants,requester,labels,assignee,conversationAssigneeGroup"
Response
Conversation details
support_ticket, member_services, non_support_event, null new, open, snoozed, on_hold, solved, closed, null urgent, normal, low, life_safety, null Custom property values, keyed by property id. Ids and value types come from the properties defined for your partner, so this object cannot be described field by field here — call the custom-property list endpoint to resolve an id to its name and type. A property never given a value takes the default configured for it, and is left out rather than returned as null when there is no default either. A value stored before its property was changed — an option renamed or removed, the type switched — is returned as stored, so it may not match the type the property has today; an absent key is the only reliable sign that nothing is set.
- Option 1
- Option 2
- Option 1
- Option 2