Skip to main content
PATCH
Update conversation
Replace {your-subdomain} with your workspace’s subdomain.
Learn how to find your subdomain in Workspace subdomain.

Headers

X-Api-Key
string
default:your-api-key
required

Use the X-Api-Key header to provide your workspace API key. Refer to Authentication for more information.

Accept
enum<string>
default:application/json
required

Specifies the expected response format. Must be set to application/json for proper API communication.

Available options:
application/json

Path Parameters

conversation_id
string<uuid>
required

Id of the conversation. You can get conversation_id by listing conversations using our List conversations API.

Example:

"de414e85-a1b5-4240-a465-7b32606980ce"

Body

application/json
title
string
Example:

"Refund for order #1042"

status
string

Status of the conversation. It must be one of the statuses of your workspace.

Example:

"closed"

priority
enum<string>
Available options:
low,
medium,
high,
urgent
Example:

"medium"

assignee_email
string<email>

Email of the team member to assign the conversation to. It is ignored when no team member has this email.

Example:

"oliver@example.com"

group_name
string

Name of the group to assign the conversation to. It is ignored when no group has this name.

Example:

"Billing"

tags
string[]

Names of the tags the conversation should have. This replaces the conversation's current tags, and tags that don't exist yet are created.

Example:
ticket_fields
object

Ticket field values keyed by the field's name. Use the option label for dropdown fields, an array of labels for multi-select fields and true or false for checkbox fields.

Example:

Response

OK - Request succeeded

conversation
object