Skip to main content
POST
DecideApprovalAPI mirrors erdo_decide_approval.

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required

Body

application/json
decided_by_external_ref
string

who decided, recorded beside the Erdo account the API key belongs to.

REST ONLY, and deliberately absent from DecideApprovalInput above: the MCP tool is answered by a model, which has no user of its own to name and would fill the field with something invented. An application does have one — a whole desk shares one organization key, so without this every approval any of them makes is attributed to the key's owner.

ATTRIBUTION, NEVER AUTHENTICATION. Erdo stores it verbatim and never verifies, parses or resolves it; anything holding the key can send any value. It may name a person on a card and must never gate anything.

decision
string
parameter_constraints
object
reason
string

DecideApprovalInput.Reason for what a rejection's reason does.

scope
string

Response

Success response

message
string
success
boolean