Skip to main content

List Alerts

GET 
/api/support/agent/alerts

The caller's own alerts, newest first. Alerts are how the support desk tells an agent that the AI agent needs them: an approval card waiting for a decision, a reminder when it is still waiting a day later, a problem the autopilot runner reported, or an AI-owned ticket that has gone quiet. Every alert is also sent as a push notification to the agent's installed app (approval alerts respect the agent's approval notification switch); nothing is emailed.

Required scope: support:read

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Each agent has their own copy of an alert, so read state is per agent. An agent only ever sees their own alerts. Alerts older than 30 days are deleted.

Filters (each also accepted without the filter[...] wrapper):

  • unread — 1 only unread, 0 only read
  • kind — approval, approval_reminder, runner, ai_stale, ai_error (value or comma-separated list)

Sorted newest first (alert id breaks ties). Paginated: page, per_page (default 10, max 100).

Alert fields

  • id (integer)
  • kind (string) — approval (an approval card is waiting on you), approval_reminder (still waiting 24 hours after the last alert), runner (the autopilot runner reported a problem), ai_stale (an AI-owned ticket has shown no sign of life for 4 hours), ai_error (the AI agent hit an error on a ticket)
  • title (string, max 160)
  • body (string, nullable)
  • url (string) — a path inside the agent console to open, e.g. /?ticket=3521 (the ticket with its approval card) or /
  • ticket_id (integer, nullable)
  • approval_id (integer, nullable) — the approval card the alert is about
  • created_at (ISO-8601)
  • read_at (ISO-8601, nullable) — null while unread

Request​

Responses​

OK

Response Headers
    Content-Type