List runs for one line
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Query parameters
Response
What set a run off.
provider, event_name, and delivery_id are lifted out of the nested
payload.trigger object so a list row is readable without walking the
envelope. The extracted trigger values are not repeated here; they land in
the run’s run_params. payload still carries the whole envelope, minus the
raw webhook body on list responses.
Why a line run ended, and which step surfaced it.
Orchestrator classification (code, domain) is written into
result_payload on terminal paths. Step diagnostics are enriched in by
the API without replacing those fields.
Read out of result_payload rather than carried as its own request field.
api and workflow-handlers are separate Deployments with no rollout
ordering, so a new key on a request body is rejected by whichever old pods
are still serving — and on LineControlWaitRequest, which forbids extras,
that rejection would finalize a succeeded run as failed.
Unknown keys are tolerated for the same reason, in the other direction: a later orchestrator that adds a field here must not make every failure read as unclassified while the rollout is in flight.