Delete a chat record
⚠️
Preview — this feature is being built; the design below is the spec.
DELETE https://app.syntic.ai/v1/compliance/chats/{chat_id}Permanently delete a chat and its attachments for the whole organization, for example after an accidental disclosure. Refused while a legal hold covers it. Requires the compliance:write scope.
For how this fits into a full workflow, see Compliance API.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <admin key>: an Admin API key (sk_admin_...) that carries the compliance:read scope (plus compliance:write for deletions and holds). Enterprise plans only. See Compliance API. |
syntic-beta | Yes, while in preview | compliance-2026-12-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
chat_id | string | Starts with chat_. |
Response
200 OK, Content-Type: application/json
{
"id": "chat_01JCV7V9X1Z3B5D7F9H1",
"type": "chat_record",
"deleted": true,
"files_deleted": 2
}Examples
curl -sS -X DELETE "https://app.syntic.ai/v1/compliance/chats/chat_01JCV7V9X1Z3B5D7F9H1" \
-H "Authorization: Bearer $SYNTIC_ADMIN_KEY" \
-H "syntic-beta: compliance-2026-12-01"Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 409 | conflict_error | legal_hold | A legal hold covers this record. |
| 404 | not_found_error | chat_not_found | No chat record with this id. |
| 401 | authentication_error | invalid_api_key | The admin key is missing, unknown, revoked or expired. |
| 403 | permission_error | admin_key_required | An inference key was used. |
| 403 | permission_error | scope_missing | The admin key lacks the compliance:read (or, for writes, compliance:write) scope. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Was this page helpful?