Questions your agents are waiting on you for, or your settled history
Two sorts, never mixed on the same page. The default — state=open (or omitted), no order — is the queue sorted the way the Floor shows it: priority descending, then kind rank (blocker, guardrail, choice, info), then oldest first; a plain limit, nextCursor always null (AF-52: this order is fixed, never paginated). Any other state (answered, expired, withdrawn, settled, all), or order=recent on open, switches to the HISTORY sort instead: most recently settled first (answered date if answered, else created date), paginated by the opaque cursor — pass back a page's nextCursor as the next call's cursor until it comes back null. settled means any of the three non-open states at once (answered, expired or withdrawn) — use it for a history view that must never show a still-open notice; all keeps open notices mixed in, for a combined per-person journal.
A company admin may read a colleague's queue/history with recipientUserId, or the whole company's, line by line, with scope=company (the two are mutually exclusive) — anyone else passing either gets 403, never a silently empty list. Notices past their expiresAt flip to expired on read, so this list never shows a stale question.
Request
- Base URL: https://api.atako.ai
- URL: https://api.atako.ai/notices
- Auth: HTTP bearer
Query parameters
Only this agent's notices.
Only notices raised from this chat session — what a session thread asks for so it shows its own questions and not the agent's others.
Only notices raised from this kind of work.
Company admins only — read a colleague's queue/history instead of your own. Mutually exclusive with scope=company.
Company admins only — company reads every notice of the company (history sort applies) instead of one recipient. Mutually exclusive with recipientUserId.
Force the history sort (most recently settled first) even when state=open.
Opaque pagination cursor from a previous page's nextCursor — only meaningful on the history sort.
Response
Changes
No recorded changes to this operation across all 2 revisions of this API.