Close an attention card: withdraw, archive or snooze
/api/companies/{companyId}/attention/{sourceKind}/{sourceId}/closeClose an attention card: withdraw, archive or snooze.
Requires a member with organization write access. mode=withdraw closes the request for everyone because it is out of date; it is never an approval. It runs the source's own withdraw (interactions, including on a closed task) or cancel (decisions, approvals except hire requests), which writes its own activity entry and tells the agent. mode=archive and mode=snooze hide the card for the caller only, until its content changes or until until; the source stays open. Cards without a request to withdraw (budget, review, blocker, recovery, failed run, agent error, join request) return 422 for withdraw with the control to use instead. 404 when the caller cannot see the card; 409 with code attention_already_closed and the resolver when someone else answered first. Writes one attention.closed activity entry.
Authorization
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.
Path parameters
Request body
application/json · required
one of: "withdraw", "archive", "snooze"at most 4000 characters1–200 charactersResponses
details names each field that failed.Errors return {"error": "..."}, often with a code and details. See errors and limits.