Runs

List Runs

Page through your account's run history, filtered by status or workflow.

curl --fail-with-body --silent --show-error 'https://api.edgaze.ai/v1/runs' \
  -H "Authorization: Bearer $EDGAZE_API_KEY"

Audience

Developers building a run history view.

GEThttps://api.edgaze.ai/v1/runs

Overview#

Returns the runs owned by the API key's account, newest first. Every run counts: those started by any key on the account and those started from the web UI both appear here.

Rows are projected from the indexed run record rather than folded from the event log, which keeps the endpoint cheap enough to poll on a dashboard. The trade-off is that outputs and reason are omitted. Read Get Run when you need a single run in full.

Runs are scoped to the API key owner, so this endpoint never returns another account's runs.

Page with offset and limit while pagination.hasMore is true. Narrow with status or workflow. Read GET /runs/{id} for outputs and failure reasons.

Authorization#

run:read

Parameters#

Headers

Authorizationstringheaderrequired

Bearer token with run:read scope.

Example: Bearer edgaze_sk_live_…

Query parameters

statusstringquery

Filter by status: pending, running, completed, failed, or cancelled.

Example: completed

workflowstringquery

Only return runs of this workflow id.

Example: 550e8400-e29b-41d4-a716-446655440000

offsetintegerquery

Pagination offset. Defaults to 0.

Example: 0

limitintegerquery

Page size from 1 to 50. Defaults to 24.

Example: 24

Response#

Example payloads are in the request/response panel above.

Each row carries id, status, workflowId, workflowVersionId, startedAt, completedAt, displayedChargeUsd, and billingStatus. The pagination object reports the offset and limit that were applied plus hasMore.

Edge cases#

Suspended runs read as running

Suspension is only visible in the event log, so a suspended run is reported as running here. GET /runs/{id} reports the precise state.

Owner-scoped

Only runs belonging to the API key's account are returned, including runs started from the web UI.

No outputs

Rows omit outputs and reason to keep the query flat. Fetch GET /runs/{id} for those fields.