Skip to main content
Flashduty Open API provides 392 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 with an APP Key (the app_key query parameter or the Fd-App-Key request header; see the quickstart).

Incidents

Channels

Alerts

Public integrations

/integration/* manages public (account-level) integrations, including supported IM and webhook types. Use /channel/integration/* for channel-owned dedicated integrations. List and info return complete integration keys and mask saved configuration secrets as ******.

Dedicated integrations

/channel/integration/* manages channel-owned dedicated integrations. Queries require Channels Read, Channels Manage, or Integrations Read; writes require Channels Manage. You also need visibility of the target channel for queries and management access for writes. The shared /integration/type/list catalog accepts these three read permissions; a scoped App Key must allow integration.api:read:typeList to query it.The App Key’s api_scopes must allow the operation. Private channels are visible to the account owner, an Admin, the channel creator, or members of the owning or managing teams; writes follow channel management access. Queries return the complete integration key and mask saved configuration secrets as ******.

Integration utilities

Schedules

Licenses

Calendars

Notification templates

Alert enrichment

Analytics

Status pages

Changes

IM integrations

Alert rules

Alert rule import and export are available in the console only. See Alert Rule Quickstart.

Data sources

Diagnostics

Monitor utilities

Dashboards

Rule folders

Facets

Applications

Issues

Session replay

Sourcemaps

Data query

Dashboards

Error ingestion rules

Issue preset severity rules

Resources

Skills

MCP servers

A2A agents

Sessions

The POST /safari/session/get response includes a 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 included. Messages from automation, child-session notifications, and parent initial messages (they carry source), messages holding question answers (function_response), and messages holding batched page-action receipts (function_responses) are excluded. The content matches the user_message_enqueued frame payload.

Automations

Knowledge

Artifacts

/safari/artifact/gallery/pin and /safari/artifact/gallery/unpin both take artifact_id (required), return an empty response on success, and never modify the artifact itself. A pin is a per-caller preference, not an edit to the artifact. The artifact stays visible to the whole account, and only the caller’s gallery order changes. The list moves the caller’s pinned artifacts to the front and returns pinned_at (Unix milliseconds) on those rows only. Any account member may pin any artifact they can see; pinning requires the artifact to exist (a missing one returns 404), while unpinning runs no existence check. Both endpoints are idempotent: re-pinning refreshes the pin time, and unpinning an artifact that was never pinned succeeds.

Members

Teams

Roles & permissions

Audit logs

Account