conversations

Update conversation

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.

patch/api/v1/conversations/{id}

Request

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

Path parameters

idstring required

The resource's unique identifier.

Request body

statusstring
assigned_tostring nullable

Example request

{
  "status": "resolved"
}

Response

Success

request_idstring required

Example response

{
  "conversation": {
    "id": "fa3efd47-67b2-428c-b75f-17d1dd2e9790"
  },
  "request_id": "req_b2e3d610e10f1b07468721ee98f0e1d2"
}

Changes

No recorded changes to this operation across all 1 revision of this API.