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

HeaderRequiredValue
AuthorizationYesBearer <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-betaYes, while in previewcompliance-2026-12-01. Without it the call fails with 400 beta_required. See Versioning.

Path parameters

ParameterTypeDescription
chat_idstringStarts 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:

StatustypecodeWhen
400invalid_request_errorbeta_requiredThe syntic-beta header is missing.
409conflict_errorlegal_holdA legal hold covers this record.
404not_found_errorchat_not_foundNo chat record with this id.
401authentication_errorinvalid_api_keyThe admin key is missing, unknown, revoked or expired.
403permission_erroradmin_key_requiredAn inference key was used.
403permission_errorscope_missingThe admin key lacks the compliance:read (or, for writes, compliance:write) scope.
429rate_limit_errorrate_limitedToo many requests; wait for Retry-After. See Rate-limit headers.
Was this page helpful?