Skip to main content
POST
Create a conversation

Authorizations

x-api-key
string
header
required

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

Body

application/json
subject
string
required
requesterId
string
required
Pattern: ^ovcid-.*$
type
enum<string> | null
Available options:
support_ticket,
member_services,
non_support_event,
null
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
snoozeUntil
string<date-time>
assigneeId
string

Platform user id. Newer ids are ovuid-<uuid>; legacy users may have bare (e.g. numeric) ids.

Minimum string length: 1
Example:

"ovuid-2b6d4d8e-9f1a-4b2c-8d4e-5f6011223344"

conversationAssigneeGroupId
string<uuid>
senderId
string

Platform user id. Newer ids are ovuid-<uuid>; legacy users may have bare (e.g. numeric) ids.

Minimum string length: 1
Example:

"ovuid-2b6d4d8e-9f1a-4b2c-8d4e-5f6011223344"

message
object
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

Created conversation

conversation
object
required
message
object
required