Skip to main content
DELETE
Delete Conversation

Authorizations

Authorization
string
header
required

Every request authenticates with an API key: Authorization: Bearer {API_KEY}. App endpoints take an app API key; knowledge endpoints take a knowledge base API key (Get Started).

Keep keys server-side; never embed them in client code. Requests with a missing or invalid key fail with HTTP 401 (unauthorized).

Path Parameters

conversation_id
string
required

ID of the conversation to delete. Get conversation IDs from List Conversations.

Body

application/json

A JSON body is always required, even when user is omitted; send {} in that case.

user
string

End-user identifier, defined by your app and unique within it. See End User Identity.

Response

Conversation deleted successfully. No content returned.