Skip to main content
Download one persisted artifact payload
Audience: developers retrieving the saved artifact payload as a file.

​
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

​
200 payload or 302 redirect

​
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

​
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