Skip to main content
POST
RespondAttentionItemAPI mirrors erdo_respond_attention_item: answer a choice

Authorizations

Authorization
string
header
required

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

Path Parameters

itemID
string
required

Body

application/json
action
string
answer
object
defects
AttentionDefectInput is one "this variant is broken" flag on a choice answer. · object[]
organization_slug
string

Response

Success response

decision_slug
string

it has one: an escalation carrying a held engine action records its decision at creation, so the item page can link straight to the report — the human answering "disable this automation" can read what was decided, on whose authority and with what outcome. Empty for digests, choices and plain escalations with no decision behind them, which is most items.

It is also on Report, and it stays here because the answer/acknowledge/ dismiss endpoints return this same shape and carry no report: a caller that just answered an item should still be told what it decided.

item
AttentionItem is one thing the engine wants a human to see or answer, · object

surfaced in the Activity feed. See migrations/008_create_attention_item.

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.