Create a new incident or maintenance event on a status page.
Documentation Index
Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt
Use this file to discover all available pages before exploring further.
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Status Pages Events Manage (on-call) |
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Parameters for creating a status page incident or maintenance event. The first update must contain component_changes to define affected components; retrospective events require at least 2 updates.
Status page ID.
Event type.
incident, maintenance Event title, up to 255 characters.
255Initial event status. investigating/identified/monitoring/resolved apply to incidents; scheduled/ongoing/completed apply to maintenances.
investigating, identified, monitoring, resolved, scheduled, ongoing, completed Timeline updates. Immediate events normally pass one update; retrospective events must pass all historical updates.
Event description (Markdown). Required by the validator.
Event start time in unix seconds. Defaults to now when omitted.
Member IDs responsible for this event.
Linked change IDs (related incidents, deployments, etc.).
Scheduled close time for retrospective events. Must be greater than start_at_seconds.
Notify subscribers about this event and all its updates.
Maintenance only: automatically advance the status based on the scheduled window.
Mark this event as a retrospective (historical) one.
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.