← API referenceFile intelligence · API access unavailable
API REFERENCE / FILE INTELLIGENCE
GET /v1/artifacts/{artifact_id}/content
Read one derived output with its actual content type.
Request fields
| Location | Field | Type | Required | Description |
|---|---|---|---|---|
| Header | Authorization | string | Yes | Credential scoped to the authorized resource. |
| Path | artifact_id | string | Yes | Stable derived-artifact ID. |
| Header | Range | string (byte range) | No | Optional byte range for large derived outputs. |
Request example
Example request
GET /v1/artifacts/art_123/content
Authorization: Bearer <scoped token>HTTP status codes
| Status | Meaning |
|---|---|
200 OK | Success response shown below. |
401 Unauthorized | Missing, expired, or invalid credential. |
403 Forbidden | Credential is valid but lacks the required scope or role. |
404 Not Found | Artifact is absent or its source file is not visible. |
416 Range Not Satisfiable | Requested bytes fall outside this artifact. |
429 Too Many Requests | Rate limit reached; honor Retry-After when provided. |
503 Service Unavailable | Service temporarily unavailable; retry safely. |
Response fields
| Field | Type | Example |
|---|---|---|
body | binary stream | File bytes |
Response example
Example response
200 OK
Content-Type: text/plain; charset=utf-8
ETag: "art_123"
<derived output bytes>How it works
Authorization is checked against the source file on every read. A known artifact ID never bypasses a revoked folder grant. Large artifacts may support byte ranges; this route never returns underlying provider credentials or device paths.