assistant

DELETE `/v1/assistant/conversations/{conversationId}`

Delete a conversation and everything in it.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

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 DELETE https://api.zinndigital.com/v1/assistant/conversations/{conversationId} \
  -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

⭐ A real delete, cascading to the turns — not an archive flag. A customer asking us to forget a conversation about their own account is entitled to have it gone.

Parameters

Name	Type	Required	What it is
`conversationId (path)`	`Uuid`	Yes	The conversation's id.

Errors this endpoint can return

401 · 403 · 404 · 429

DELETE /v1/assistant/conversations/{conversationId}