Skip to main content
GET
ListWorkstreamsAPI mirrors erdo_list_workstreams.

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Query Parameters

status
string[]
limit
integer<int32>
Required range: -2147483648 <= x <= 2147483647

Response

Success response

decision_exceptions
DecisionExceptionCounts is the pair of decision states the quiet board colors. · object

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.

followed_workstream_ids
string[]

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.

open_urgent_by_workstream_id
OpenUrgentByWorkstreamID maps workstream_id (string) → its count of open, · object

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.

open_urgent_standalone
integer<int64>

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.

phases_by_workstream_id
PhasesByWorkstreamID maps workstream_id (string) → its ordered phases. · object

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).

workstreams
Workstream represents a piece of business work in motion. · object[]