Skip to main content
Flashduty Open API provides 339 endpoints covering five major modules: On-call, Monitors, RUM, AI SRE, and Platform. All endpoints use unified authentication and request specifications. See Quick Start for details.
All endpoint URLs use https://api.flashcat.cloud as the base, authenticated via APP Key through query string.

Incidents

Channels

Alerts

Integrations

Schedules

Licenses

Calendars

Notification templates

Alert enrichment

Analytics

Status pages

Changes

IM integrations

Alert rules

Data sources

Diagnostics

Monitor utilities

Facets

Applications

Issues

Session replay

Sourcemaps

Data query

Error ingestion rules

Issue preset severity rules

Resources

Skills

MCP servers

A2A agents

Sessions

The POST /safari/session/get response includes a new pending_messages field, alongside events: the server-side projection of the human messages sitting in the session queue that the agent (actor) has not read yet, in execution order (head first), always an array (an empty array, never null, when nothing is queued). Each element has these fields:Only plain human messages are projected: rows produced by internal producers (automation, child-session notifications, parent initial messages — they carry source) and question answers (function_response) are excluded; if the queue cannot be read, the field degrades to an empty array instead of failing the request. The projection matches the user_message_enqueued frame payload and is what clients use to render “sent but not yet handled” pending bubbles.

Automations

Knowledge

Artifacts

Members

Teams

Roles & permissions

Audit logs

Account