ListWorkstreamsAPI mirrors erdo_list_workstreams.
Authorizations
An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).
Response
Success response
Two numbers rather than one, because they are different jobs: an unconfirmed egress is something to go and CHECK at the provider, and an expectation that settled against the decision is something to REVIEW before deciding the same way again. Summing them would produce a number an operator cannot act on.
follows (Wave E), so the list page and quiet board can render a follow toggle per cell without an extra fetch. Ids not present are not followed.
urgent attention items, for the quiet board (work-engine D10). Only workstreams with at least one are present; a missing entry means zero (a quiet cell). Embedded here so the board reads a single existing endpoint rather than fanning out a per-workstream attention query.
NO owning workstream (an org-level alert like a failing automation). These never appear in OpenUrgentByWorkstreamID and have no workstream cell, so the quiet board needs this to answer "is everything OK?" honestly — it must not read "all quiet" while standalone urgents sit red in the feed.
Embedded so list-page cards can render phase pips without N+1 fetches. Workstreams with no phases are omitted from the map (frontend should treat a missing entry as an empty slice).

