WARNING: This operation PERMANENTLY deletes the chat, all of its messages, changedmanage-claude/compliance-content-data
Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+13added
Lines−13removed
From line
31
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits14to this page, all time
The whole hunk
from line 31, old and new numbered
/
from line 31
3131```bash cURL
3232curl --fail-with-body -sS -G \
3333 "https://api.anthropic.com/v1/compliance/apps/chats" \
34 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
35 --header "anthropic-version: 2023-06-01" \
34 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
35 -H "anthropic-version: 2023-06-01" \
3636 --data-urlencode "order_by=updated_at" \
3737 --data-urlencode "updated_at.gte=2025-06-01T00:00:00Z" \
3838 --data-urlencode "limit=100"
from line 69
6969
7070A few constraints apply to these organization-wide queries. Cursors are opaque and bound to the sort key, so an `after_id` issued under one `order_by` value is rejected with a 400 error under the other. Time-filter bounds must match the sort key too: pair `updated_at.*` bounds with `order_by=updated_at`, and `created_at.*` bounds with the default `order_by=created_at`. Backward pagination with `before_id` is not supported, and the `project_ids[]` filter is not available. See [List chats](https://platform.claude.com/docs/en/api/compliance/apps/chats/list) for the full filter reference.
7171
72To scope the list to specific users instead (for example, a legal hold on named custodians), pass 1–10 `user_ids[]` values. Obtain the IDs from [List organization users](https://platform.claude.com/docs/en/manage-claude/compliance-org-data#list-organization-users). User-filtered queries always sort by `created_at` (passing `order_by=updated_at` returns a 400 error) and support both `after_id` and `before_id`. Filtering by `project_ids[]` is only available in this user-filtered form. Combining `user_ids[]` with any `updated_at.*` bound is deprecated and will be rejected with a 400 error after 2026-09-22; to keep a custodian set current by update time, run the org-wide `order_by=updated_at` walk without `user_ids[]` and select the custodians' chats from its results, and keep the user-filtered listing for `created_at`-ordered exports.
72To scope the list to specific users instead (for example, a legal hold on named custodians), pass 1–10 `user_ids[]` values. Obtain the IDs from [List organization users](https://platform.claude.com/docs/en/manage-claude/compliance-org-data#list-organization-users). User-filtered queries always sort by `created_at` (passing `order_by=updated_at` returns a 400 error) and support both `after_id` and `before_id`. Filtering by `project_ids[]` is only available in this user-filtered form. Combining `user_ids[]` with any `updated_at.*` bound is deprecated and will be rejected with a 400 error after 2026-09-22; to keep a custodian set current by update time, run the organization-wide `order_by=updated_at` walk without `user_ids[]` and select the custodians' chats from its results, and keep the user-filtered listing for `created_at`-ordered exports.
7373
7474```bash cURL
7575curl --fail-with-body -sS -G \
from line 86
8686```bash cURL
8787curl --fail-with-body -sS \
8888 "https://api.anthropic.com/v1/compliance/apps/chats/claude_chat_01H5CWunD7RpVJ5bHa8RCkja/messages" \
89 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
90 --header "anthropic-version: 2023-06-01"
89 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
90 -H "anthropic-version: 2023-06-01"
9191```
9292
9393The messages endpoint returns the chat's metadata plus a `chat_messages` array sorted by `created_at`. When `limit` is omitted, the full message set is returned in one response; pass `limit`, `after_id`, or `before_id` to page through very long chats. The endpoint also accepts `created_at.*` and `updated_at.*` range bounds (`gt`, `gte`, `lt`, `lte`) and an `order` parameter (`asc` or `desc`). See [Get chat messages](https://platform.claude.com/docs/en/api/compliance/apps/chats/messages/list) for the full parameter list. For user messages, `created_at` is when the message was sent; for assistant messages, it is when Claude finished generating the message. Each message carries its text content and, when present, any uploaded files (typically on user messages), any tool-generated files, and any artifacts the assistant produced or updated (typically on assistant messages):
from line 195
195195```bash cURL
196196curl --fail-with-body -sS \
197197 "https://api.anthropic.com/v1/compliance/apps/chats/files/claude_file_01UaT9wBcDfGhJkLmNpQrSv7/content" \
198 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
199 --header "anthropic-version: 2023-06-01" \
198 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
199 -H "anthropic-version: 2023-06-01" \
200200 --output "dashboard_mockup_v1.pdf"
201201```
202202
from line 228
228228```bash cURL
229229curl --fail-with-body -sS -G \
230230 "https://api.anthropic.com/v1/compliance/apps/projects/claude_proj_01KGp4eZNug9ri4kE35RSppq/attachments" \
231 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
232 --header "anthropic-version: 2023-06-01"
231 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
232 -H "anthropic-version: 2023-06-01"
233233```
234234
235235```json Response
from line 265
265265
266266The Compliance API exposes hard-delete endpoints for chats, files, project documents, and entire projects. A hard-deleted chat cannot be restored, and it stops appearing in list responses afterward.
267267
268* [Delete chat](https://platform.claude.com/docs/en/api/compliance/apps/chats/delete): also removes the chat's messages and any files attached to those messages.
268* [Delete chat](https://platform.claude.com/docs/en/api/compliance/apps/chats/delete): also deletes the chat's messages and any files attached to those messages.
269269* [Delete file](https://platform.claude.com/docs/en/api/compliance/apps/chats/files/delete): handles both chat files and project files.
270* [Delete project document](https://platform.claude.com/docs/en/api/compliance/apps/projects/documents/delete): removes a single project document by ID.
270* [Delete project document](https://platform.claude.com/docs/en/api/compliance/apps/projects/documents/delete): deletes a single project document by ID.
271271* [Delete project](https://platform.claude.com/docs/en/api/compliance/apps/projects/delete): see [Detach chats before deleting a project](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#detach-chats-before-deleting-a-project).
272272
273273For a chat in the unified Claude experience, [Delete chat](https://platform.claude.com/docs/en/api/compliance/apps/chats/delete) also deletes the sessions in the cloud that were started for the chat. It does not delete sessions that those sessions started.
from line 285
285285
286286curl --fail-with-body -sS -X DELETE \
287287 "https://api.anthropic.com/v1/compliance/apps/chats/claude_chat_01H5CWunD7RpVJ5bHa8RCkja" \
288 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
289 --header "anthropic-version: 2023-06-01"
288 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
289 -H "anthropic-version: 2023-06-01"
290290```
291291
292292```json Response
No line in this hunk matches that.