WARNING: This operation PERMANENTLY deletes the chat, all of its messages, changedmanage-claude/compliance-content-data
Nearest release: v2.1.317, published 2 hours before 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−6removed
From line
146
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 146, old and new numbered
/
from line 146
146146 "mime_type": "text/csv",
147147 "size_bytes": 2048,
148148 "md5": "89968669461d95416549937168269d6b"
149 },
150 {
151 "id": "claude_file_01Qm7RzKdTgWnYbVx3HcLpE5",
152 "filename": "requirements_tracker.xlsx",
153 "mime_type": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
154 "size_bytes": 18432,
155 "md5": "5ccf4e7dd3bdfa729883d6764631ac60"
149156 }
150157 ],
151158 "artifacts": [
from line 171
164171}
165172```
166173
167`files`, `generated_files`, and `artifacts` can each be `null` on a given message. `files` are the files and text attachments (for example, PDFs, images, spreadsheets, documents, and pasted text) the user attached to the message, as claude.ai stored them. `generated_files` are binary files the assistant created during the conversation through tool use (for example, PDFs, spreadsheets, or slide decks). `artifacts` are versioned documents (for example, code or markdown) the assistant generated or updated in its response; an artifact can be revised across multiple assistant turns in the same chat, and each revision appears as a new `version_id` under the same artifact `id`. Pass each entry’s `id` (or `version_id` for artifacts) to the matching content endpoint in [Retrieve files and artifacts](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-files-and-artifacts) to download it.
174`files`, `generated_files`, and `artifacts` can each be `null` on a given message. `files` are the files and text attachments (for example, PDFs, images, spreadsheets, documents, and pasted text) the user attached to the message, as claude.ai stored them. `generated_files` are binary files the assistant created during the conversation through tool use (for example, PDFs, spreadsheets, or slide decks). `artifacts` are versioned documents (for example, code or markdown) the assistant generated or updated in its response; an artifact can be revised across multiple assistant turns in the same chat, and each revision appears as a new `version_id` under the same artifact `id`. Pass each entry’s `id` (or `version_id` for artifacts) to the matching content endpoint in [Retrieve files and artifacts](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-files-and-artifacts) to download it. An `id` in `generated_files` starts with either `claude_gen_file_` or `claude_file_`. Choose the endpoint by the prefix, not by the array the entry came from.
168175
169176## Retrieve files and artifacts
170177
171Files and artifacts are downloaded by ID. Except for Claude Docs documents (see the end of this section), they aren’t listed independently. The IDs come from the chat messages endpoint in [Retrieve chats and messages](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-chats-and-messages) (the `files`, `generated_files`, and `artifacts` arrays on each message) or, for project-level uploads, from the [project attachments endpoint](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-projects-and-attachments).
178Files and artifacts are downloaded by ID. They aren’t listed independently, except for the artifacts returned by [List code artifacts](https://platform.claude.com/docs/en/api/compliance/apps/code/artifacts/list), such as Claude Docs documents (see the end of this section). All other IDs come from the chat messages endpoint in [Retrieve chats and messages](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-chats-and-messages) (the `files`, `generated_files`, and `artifacts` arrays on each message) or, for project-level uploads, from the [project attachments endpoint](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-projects-and-attachments).
172179
173Pick the endpoint that matches your ID type and the data you need. The same file content endpoint serves both chat files and project files.
180Pick the endpoint that matches your ID’s prefix and the data you need. The same file content endpoint serves chat files, project files, and the `generated_files` entries whose IDs start with `claude_file_`. The file endpoints and the generated-file endpoints each reject the other’s IDs with a 400 error; see [Invalid file ID](https://platform.claude.com/docs/en/manage-claude/compliance-errors#invalid-file-id).
174181
175182| You have | You want | Use this endpoint |
176183| ------------------------------ | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
from line 194
187194
188195The response carries these headers:
189196
190* `Content-Disposition: attachment; filename*=utf-8''<percent-encoded filename>` carries the original upload file name in RFC 5987 extended form. The extended form is used for every file name, not only non-ASCII ones.
197* `Content-Disposition: attachment; filename*=utf-8''<percent-encoded filename>` carries the file name in RFC 5987 extended form. The extended form is used for every file name, not only non-ASCII ones.
191198* `Content-Type` carries the MIME type recorded for the stored content, which for a document stored as extracted text can still name the original document format.
192199* `Content-MD5` carries the MD5 digest of the served bytes, base64-encoded as specified in RFC 1864.
193200* `Transfer-Encoding: chunked` is always set.
from line 207
200207 --output "dashboard_mockup_v1.pdf"
201208```
202209
203In curl, the `--remote-header-name` (`-J`) option, which normally saves a download under the `Content-Disposition` file name, does not read the `filename*` form, so name the saved file yourself with `--output`. In a script, take the name from the file’s `filename` field in the chat messages or [Get file metadata](https://platform.claude.com/docs/en/api/compliance/apps/chats/files/retrieve) response, or decode `filename*`. Either way, it is the name the user gave the upload, so treat it as untrusted before using it as an output path:
210In curl, the `--remote-header-name` (`-J`) option, which normally saves a download under the `Content-Disposition` file name, does not read the `filename*` form, so name the saved file yourself with `--output`. In a script, take the name from the file’s `filename` field in the chat messages or [Get file metadata](https://platform.claude.com/docs/en/api/compliance/apps/chats/files/retrieve) response, or decode `filename*`. Either way, treat it as untrusted before using it as an output path:
204211
205212* Keep only the base name.
206213* Allow only characters that are safe on your filesystem.
No line in this hunk matches that.