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"
Developers building a run history view.
https://api.edgaze.ai/v1/runsOverview#
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.
The list response omits outputs and reason to stay compact. 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.
Authorization#
run:readParameters#
Headers
AuthorizationstringheaderrequiredBearer token with run:read scope.
Example: Bearer edgaze_sk_live_…
Query parameters
statusstringqueryFilter by status: pending, running, completed, failed, or cancelled.
Example: completed
workflowstringqueryOnly return runs of this workflow id.
Example: 550e8400-e29b-41d4-a716-446655440000
offsetintegerqueryPagination offset. Defaults to 0.
Example: 0
limitintegerqueryPage 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#
A suspended run is reported as running in this list. GET /runs/{id} reports the precise state.
Only runs belonging to the API key's account are returned, including runs started from the web UI.
Rows omit outputs and reason to keep the query flat. Fetch GET /runs/{id} for those fields.
Was this useful?
Your response helps us improve the documentation.