Runs

List Run Events

Read the durable event log for a run: started, node progress, and completion markers.

curl --fail-with-body --silent --show-error 'https://api.edgaze.ai/v1/runs/7c9e6679-7425-40de-944b-e07fc1f90ae7/events' \
  -H "Authorization: Bearer $EDGAZE_API_KEY"

Audience

Developers building with the Edgaze API.

GEThttps://api.edgaze.ai/v1/runs/{run_id}/events

Overview#

Returns a page from the durable, ordered event log for a run. Each event has a monotonic sequence number and ISO timestamp.

Terminal event names match the final run status: run.completed, run.failed, or run.cancelled. Event payloads are sanitized and never expose internal billing or account fields.

Use alongside GET /runs/{id} when you need step-level visibility: for example, showing progress in a dashboard or debugging which node failed.

Fetch after POST /runs while polling status. Pass afterSequence from nextAfterSequence to read the next page. The default page is 100 events and the maximum is 500.

Authorization#

run:read

Parameters#

Headers

Authorizationstringheaderrequired

Bearer token with run:read scope.

Example: Bearer edgaze_sk_live_…

Path parameters

run_idstringpathrequired

UUID returned from POST /runs.

Example: 7c9e6679-7425-40de-944b-e07fc1f90ae7

Query parameters

afterSequenceintegerquery

Return events after this sequence. Defaults to 0.

Example: 0

limitintegerquery

Page size from 1 to 500. Defaults to 100.

Example: 100

Response#

Example payloads are in the request/response panel above.

Edge cases#

Reconstructing streamed output

node.output.delta events carry data.text. Concatenate them in sequence order, grouped by nodeId, to rebuild what a node produced as it ran.

data is an allowlist

Events expose only text, status, and reason. Cost records, payer identity, and raw provider errors are never included; failure text is generalized the same way as Run.reason.

Treat event types as an open set

New event types may be added. Ignore types you do not recognize rather than failing.

Bounded pages

Pages default to 100 events and are capped at 500 events.

Prefer the stream for live UIs

GET /runs/{id}/stream delivers the same events over SSE without a polling loop.

Was this useful?

Your response helps us improve the documentation.