List Run Artifacts

GET /runs/{run_id}/artifacts

The binaries a run produced, newest first.

Ids and facts, no links: a link is asked for per artifact through GET /runs/{run_id}/artifacts/{attachment_id}, so reading the list signs nothing and works on a deployment with no bucket. A user’s upload to the same run is not listed. Requires the viewer role in the run’s workspace.

Role floor

Requires viewer or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
run_id	path	string (uuid)	required	—
limit	query	integer	optional	Default 50. min 1 max 200
cursor	query	string | null	optional	—
offset	query	integer | null	optional	min 0

Responses

Status	Description	Body
200	Successful Response	Page_RunArtifactItem_
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/runs/{run_id}/artifacts \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — Page_RunArtifactItem_

Field	Type		Notes
items	RunArtifactItem[]	required	—
next_cursor	string | null	optional	—
total	integer | null	optional	—