public

POST `/v1/public/chat/{publicKey}/conversations/{conversationId}/ticket/solved`

"That solved it" on the chat's ticket form (our own websites only).

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

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/public/chat/{publicKey}/conversations/{conversationId}/ticket/solved \
  -H "Content-Type: application/json" \
  -d '{ "deflection_id": <Uuid> }'

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

Anonymous, authorised by X-Zinn-Chat-Token (s1014 L39). Counts the answer from answerPublicChatTicket as a ticket the AI prevented. Moves only a PUBLIC answer from the last 24 hours; 204 whether or not anything moved.

Parameters

Name	Type	Required	What it is
`publicKey (path)`	`string`	Yes	The widget's public key. Public by design — it ships in the page source of every site that embeds the widget — so it NAMES a widget and authorises nothing; the `Origin` header is…
`conversationId (path)`	`string`	Yes	—

Request body

Name	Type	Required	What it is
`deflection_id`	`Uuid`	Yes	UUIDv7 identifier — sortable by creation time (docs/02 §8).

Errors this endpoint can return

404 · 429

POST /v1/public/chat/{publicKey}/conversations/{conversationId}/ticket/solved