Update conversation
Update mutable fields on a conversation: assignee, status, priority, labels, and the free-form attribute map. Only the fields you include in the request body are modified; omitted fields are left as-is. customProperties accepts the custom properties defined for your partner, keyed by property id; send null to clear one. Requires the conversation:write scope.
Authorizations
Send the API key in the x-api-key header.
Path Parameters
"57f2d879-20f8-4106-9abb-44fa099e0448"
Body
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: an unknown id or a value that does not match the property type is rejected with 400. Only the ids you send are modified — omit a property to leave it untouched. To clear one, send null; a blank string and an empty array count as empty too, for every property type alike.
Response
Updated conversation
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