## Get artifact metadata ### Path Parameters ### Header Parameters ### Returns ### Example #### Response
The whole hunk
81 lines, first recorded
/
lines
The first capture of this source. The page was already there, and this is what it said.
---
title: Get artifact metadata
url: https://platform.claude.com/docs/en/api/compliance/apps/artifacts/retrieve
---
## Get artifact metadata
**get** `/v1/compliance/apps/artifacts/{artifact_version_id}`
Returns metadata for an artifact version, without the content body.
Use the sibling `/content` endpoint to fetch the artifact text. The
`md5` and `size_bytes` fields here are computed over the UTF-8
encoding of that text, so a DLP consumer can dedupe or match hashes
without downloading every artifact.
### Path Parameters
- `artifact_version_id: string`
The artifact version ID (tagged ID, e.g., claude_artifact_version_abc123)
### Header Parameters
- `"x-api-key": optional string`
### Returns
- `id: string`
Artifact ID e.g. 'claude_artifact_abc123'
- `artifact_type: string or null`
MIME-like artifact type e.g. 'application/vnd.ant.code'
- `claude_chat_id: string`
The chat this artifact belongs to
- `created_at: string`
Artifact version creation timestamp
- `md5: string`
Lowercase hex MD5 of the artifact content (UTF-8 encoded). Matches the `content` field returned by the sibling `/content` endpoint.
- `size_bytes: number`
Size in bytes of the artifact content (UTF-8 encoded)
- `title: string or null`
Artifact title
- `version_id: string`
Artifact version ID e.g. 'claude_artifact_version_abc123'
### Example
```http
curl https://api.anthropic.com/v1/compliance/apps/artifacts/$ARTIFACT_VERSION_ID \
-H "Authorization: Bearer $ANTHROPIC_COMPLIANCE_API_KEY"
```
#### Response
```json
{
"id": "id",
"artifact_type": "artifact_type",
"claude_chat_id": "claude_chat_id",
"created_at": "2019-12-27T18:11:19.117Z",
"md5": "md5",
"size_bytes": 0,
"title": "title",
"version_id": "version_id"
}
```