Skip to main content
GET
ListDecisionsAPI mirrors erdo_list_decisions.

Authorizations

Authorization
string
header
required

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

Query Parameters

organization_slug
string
workstream_slug
string
source
string
decision_class
string
subject_kind
string
subject_ref
string
status
string
applicability
string
outcome
string
approval_id
string

The approval whose answer produced the decisions to return. It is the one identifier on this surface that is an id rather than a slug, because an approval has none — listing, reading and deciding one all take its id, so the id is the handle a caller already holds. It matches whether the ask was approved or refused, and can name several decisions: an answered batch is split into one decision per coherent intent.

since
string
limit
integer<int32>
Required range: -2147483648 <= x <= 2147483647
offset
integer<int32>
Required range: -2147483648 <= x <= 2147483647
lapsed_offset
integer<int32>

With applicability=standing, current and lapsed commitments are two lists paged independently, so neither crowds the other out of a page.

Required range: -2147483648 <= x <= 2147483647

Response

Success response

decisions
DecisionSummary is the compact projection of one decision that both a · object[]
lapsed_decisions
DecisionSummary is the compact projection of one decision that both a · object[]

cursor with the same limit: decisions holds only current commitments (offset), lapsed_decisions only expired unsuperseded ones (lapsed_offset). Neither list's rows count against the other's page. Any other applicability returns every match in decisions, each carrying `lapsed`, and lapsed_decisions empty.

lapsed_offset
integer<int32>
Required range: -2147483648 <= x <= 2147483647
limit
integer<int32>

the page itself on the org that has decided the most, and no caller has needed one — a short page is the end of that list.

Required range: -2147483648 <= x <= 2147483647
offset
integer<int32>
Required range: -2147483648 <= x <= 2147483647