To enable the Compliance API, see the setup guide.
Set up the Compliance APITo enable the Compliance API, see the setup guide.
Set up the Compliance APIFile metadata for GET /v1/compliance/apps/chats/files/{claude_file_id}.
Returns metadata only. Use the sibling /content endpoint to download
the file bytes.
File ID
Chats this file is attached to. A file can be referenced by messages across multiple chats.
File creation timestamp
Display name of the file, if set
Lowercase hex MD5 of the file's preferred downloadable variant, as recorded at upload time. Null when no stored hash is available. The sibling /content endpoint also sets a Content-MD5 header (base64 per RFC 1864) computed over the exact served bytes; when the two disagree, the header is authoritative.
Chat message IDs this file is attached to. A file can be referenced by multiple messages.
MIME type of the file's preferred downloadable variant (e.g. 'application/pdf'). May be null for files with no downloadable content (e.g. code-interpreter outputs).
Size in bytes of the file's preferred downloadable variant, if known
Response for deleting a compliance file.
The ID of the file that was deleted
Constant string confirming deletion