Skip to main content
GET
ListAttentionItemsAPI mirrors erdo_list_attention_items.

Authorizations

Authorization
string
header
required

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

Query Parameters

statuses
string[]
engine_actions_only
boolean
item_id
string
organization_slug
string
subject_kind
string
subject_id
string
limit
integer<int32>
Required range: -2147483648 <= x <= 2147483647
offset
integer<int32>
Required range: -2147483648 <= x <= 2147483647

Response

Success response

items
AttentionItem is one thing the engine wants a human to see or answer, · object[]
report
AttentionItemReport is everything a person needs to judge one escalation · object

without opening a database: what Erdo read, what it proposes, what happens if nobody answers, and what the item is connected to.

It exists because the feed card is a headline. In September 2026 one organization raised 45 escalations and the platform expired 141 of the 181 raised that month unanswered — a correct diagnosis expires exactly as quietly as a wrong one when the reasoning behind it cannot be read.

Every field is a projection of something already stored. Nothing here is derived prose, and nothing is invented when a fact is missing: an item with no decision behind it carries no decision, which is the ordinary case.

total
integer<int64>