Download a verified artifact associated with an accessible workflow run
GET
/v1/metronomes/{metronomeId}/runs/{runId}/artifacts/{digest}A digest is not authorization. The artifact must be associated with this run and its owner/organization scope. Bytes are length- and SHA-256-verified before delivery. Untrusted content is always an attachment.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| metronomeId | path | string | Yes | Metronome workflow ID |
| runId | path | string | Yes | — |
| digest | path | string | Yes | — |
Query parameters
None.
Body schema
This endpoint does not require a request body.
None.
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Original verified bytesapplication/octet-stream
None.
400Invalid digest
None.
401Authentication required
None.
403Permission denied
None.
404Run or associated artifact not accessible
None.
409Artifact integrity mismatch
None.
503Artifact store unavailable
None.
Download a verified artifact associated with an accessible workflow run
Loading...
Response 200
Loading...