Skip to main content
PATCH
Update conversation

Authorizations

x-api-key
string
header
required

Send the API key in the x-api-key header.

Path Parameters

id
string<uuid>
required
Example:

"57f2d879-20f8-4106-9abb-44fa099e0448"

Body

application/json
subject
string
type
enum<string> | null
Available options:
support_ticket,
member_services,
non_support_event,
null
snoozeUntil
string<date-time>
status
enum<string> | null
Available options:
new,
open,
snoozed,
on_hold,
solved,
closed,
null
urgency
enum<string> | null
Available options:
urgent,
normal,
low,
life_safety,
null
assigneeId
string
conversationAssigneeGroupId
string<uuid>
requesterId
string<uuid>
customProperties
object

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.

Example:

Response

Updated conversation

id
string
required
friendlyId
string
required
subject
string
required
type
enum<string> | null
required
Available options:
support_ticket,
member_services,
non_support_event,
null
snoozeUntil
string<date-time> | null
required
createdAt
string<date-time>
required
deletedAt
string<date-time> | null
required
assigneeGroupUpdatedAt
string<date-time> | null
required
assigneeUpdatedAt
string<date-time> | null
required
conversationStatusUpdatedAt
string<date-time> | null
required
lastMessageReceivedAt
string<date-time> | null
required
requesterUpdatedAt
string<date-time> | null
required
status
enum<string> | null
required
Available options:
new,
open,
snoozed,
on_hold,
solved,
closed,
null
urgency
enum<string> | null
required
Available options:
urgent,
normal,
low,
life_safety,
null
customProperties
object
required

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.

Example:
sites
object[] | null
assigneeId
string | null
assignee
object | null
conversationAssigneeGroupId
string<uuid> | null
conversationAssigneeGroup
object | null
requesterId
string<uuid> | null
requester
object
participants
object · object · null[] | null
labels
string[] | null