---
title: "Update conversation"
method: PATCH
path: "/api/v1/conversations/{id}"
tags: ["conversations"]
---

# Update conversation

`PATCH /api/v1/conversations/{id}`

## Request

- Base URL: `https://app.blueticked.com`
- URL: `https://app.blueticked.com/api/v1/conversations/{id}`
- Auth: HTTP bearer

Assign, resolve, or reopen a conversation from support tooling.

status: open | pending | resolved. assigned_to: a workspace user id, or null to unassign.

The assignee must be a current member of this workspace who can open the conversation: access to its business, or an owner or admin when it has none. Otherwise the call answers validation_failed with details.reason assignee_not_member or assignee_cannot_open, and nothing changes.

Resolving hands the conversation back to automation, as Done in the Inbox does: a hand-over pause is lifted, so flows answer the customer's next message. While a ticket on the conversation is open or in progress, the hand-over stays.

To reply into a conversation, use POST /api/v1/messages; the send pipeline routes by contact.

## Path parameters

- `id` string, required

## Request body

- object
  - `status` string
  - `assigned_to` string, nullable

## Response `200`

Success

- object
  - `conversation` object, required
    - `business_id` string, uuid, nullable, required
    - `contact_id` string, uuid, required
    - `unread_count` number, required
    - `last_message_at` string, date-time, required
    - `created_at` string, date-time, required
    - `updated_at` string, date-time, required
    - `id` string, uuid, required
    - `channel` 'whatsapp' | 'sms' | 'email' | 'telegram', required
    - `status` 'open' | 'pending' | 'resolved', required
    - `assigned_to` string, nullable, required
  - `request_id` string, required

## Other responses

- `400`: Validation failed
- `401`: Unauthorized: missing or invalid API key
- `402`: Insufficient wallet balance
- `403`: Forbidden: scope, plan limit, or suspension
- `404`: Not found
- `409`: Conflict (idempotency-key reuse or resource in use)
- `413`: Request body above the endpoint's size limit
- `422`: Understood but refused: the request is well-formed, the action is not permitted for this resource
- `429`: Rate limited
- `500`: Internal error
- `502`: An upstream provider refused or failed the request
- `503`: Channel or send queue unavailable

---

[API](https://skmtc.dev/blueticked/apis/blueticked-api.md) · [All operations](https://skmtc.dev/blueticked/apis/blueticked-api/llms.txt) · [OpenAPI document](https://skmtc.dev/blueticked/apis/blueticked-api/revisions/07132284f4ff?raw)