> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/artifacts/{artifact_id}/download

> Download one persisted artifact payload

Download one persisted artifact payload

<Info>
  Audience: developers retrieving the saved artifact payload as a file.
</Info>

## Coverage and source scope

Returns the saved payload directly when it is stored locally. When the record is stored in R2, the route returns a `302` redirect to a short-lived signed object URL. Callers must allow redirects and should retain the artifact ID and manifest checksum alongside downloaded content.

## Canonical metadata

* `artifact ID`
* `manifest checksum`
* `200 payload or 302 redirect`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET -L -H "x-api-key: $SECAPI_API_KEY" -H "secapi-version: 2026-03-19" "https://api.secapi.ai/v1/artifacts/art_example_123/download" -o artifact.md
  ```
</RequestExample>

## 200 payload or 302 redirect

<ResponseExample>
  ```markdown theme={null}
  # Example artifact payload

  This response body is illustrative markdown saved for the artifact. When the payload is stored in R2, this endpoint instead returns a 302 redirect to a signed download URL.
  ```
</ResponseExample>

## Direct body versus redirect

For locally stored payloads, the route returns the body with its saved content type and a download filename. For R2-backed payloads, it redirects with `302` to a signed URL. The `-L` flag in the example follows that redirect. Fetch the manifest first when you need the filename, content type, byte length, checksum, or filing context.

## Errors

A missing, inaccessible, or unreadable artifact returns `404 artifact_download_failed`.

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/artifacts/{artifact_id}/download to download one persisted artifact payload. Preserve `artifact ID`, `manifest checksum`, `200 payload or 302 redirect` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## Failure posture

* allow redirects but do not persist the signed redirect URL as a durable identifier
* retain artifact ID and manifest checksum with downloaded content
* use the manifest's source context when the payload supports an evidence claim