assistant
POST /v1/assistant/conversations/{conversationId}/escalate
Turn a conversation into a support ticket.
Authentication
Send an API key as a bearer token. The key must carry the tickets.reply permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/assistant/conversations/{conversationId}/escalate \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
⭐ The point of `needs_human`. Opens a ticket carrying the whole transcript, so the customer does not start again somewhere else and the agent opens something that already contains the question and what the assistant could not do. **Idempotent** — a second call returns the same ticket with `200` rather than opening a duplicate. Requires `tickets.reply`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
conversationId (path) | Uuid | Yes | The conversation's id. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
ticket_id | Uuid | Yes | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429