Update conversation.

PATCH/api/v1/conversations/{id}

Browse API endpoints

Conversations / CRM REST API

Scope: conversations:write

Request body:

Code example

{
  "status": "closed",
  "assignedTo": "user_id_here"
}

Both fields are optional. Set assignedTo to null to unassign.

Loading endpoint details...

Build a request

Request example

Documented defaults and example values are ready. Change only the parameters you need.

Connection

Your CRM deployment URL

Replace the Bearer API key placeholder in the copied server-side code. No API key is entered or sent here.

Sub-account ID Agency keys onlyAgency-scoped keys require the X-Sub-Account-Id header.

Path parameters

id Required

Body parameters

status

assignedTo

Edit the full JSON body

cURL

curl --request PATCH \
  --url 'https://your-crm.example.com/api/v1/conversations/ID_HERE' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{"status":"closed","assignedTo":"user_id_here"}'

This shows a static response from the documentation. It does not send a request to your CRM or use an API key.