Saved runs, newest first. Empty in skeleton mode.

GET

/api/v1/reports/runs

curl --request GET \
  --url https://example.com/api/v1/reports/runs \
  --header 'Authorization: Bearer <token>'

Authorizations

• bearer

Parameters

Query Parameters

limit

integer format: int64

Responses

200

Saved runs, newest first; empty in skeleton mode

Media typeapplication/json

Array<object>

A run row for the saved-reports list (without the heavy result_* payloads).

object

created_by

string | null

created_ms

required

integer format: int64

definition_id

string | null format: uuid

error

string | null

finished_ms

integer | null format: int64

id

required

string format: uuid

name

required

string

pct

required

integer format: int32

range_from_ms

integer | null format: int64

range_to_ms

integer | null format: int64

section_count

required

integer format: int32

started_ms

integer | null format: int64

state

required

Lifecycle of one report run.

string

Allowed values: queued running succeeded failed unknown

trigger

required

What started a run.

string

Allowed values: manual scheduled unknown

Example

[
  {
    "state": "queued",
    "trigger": "manual"
  }
]

401

No valid bearer token

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}

403

Role lacks View

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}