Runs
List the notifications a run owes
List the notifications a run owes. Requires permission runs:read.
GET
List the notifications a run owes
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
Returns one page of the notifications the run owes for one attempt: theevent (its kind, title, summary and, for a step’s notification, its node), the channel (bell, slack or email), whether it targets a person or a Slack channel (targetKind), its delivery state, timing, attempts, lastError (credential-shaped strings masked), the obligation that superseded it and when and why it was repaired. Never the recipient, the person or Slack channel it targets, the delivered notification or who repaired it.
Attempts and paging
attempt defaults to the run’s current attempt. An attempt the run never made answers 400 “Invalid attempt”; GET /api/v2/runs/getProvenance lists the run’s attempts. limit is 1 to 100 (default 50). Follow meta.nextCursor as cursor while meta.hasMore is true. A cursor the server cannot read answers 400.
Visibility
You needruns:read at the run’s home (its own org unit, else its workflow’s owning org unit) and at every company it carries, the same rule as GET /api/v2/runs/get. Any other run, and a run with neither home, answers 404 “Run not found” like a missing one. A Personal key reads as its owner, cut down to the key’s scopes; an External App reads by its own role grants.Authorizations
Query Parameters
Response
One page of notification obligations

