List events (incidents and maintenances) for 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 | None — any valid app_key can call this operation |
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.
Status page ID.
Filter events started at or after this unix timestamp (seconds).
Filter events started at or before this unix timestamp (seconds).
Event type filter. Required.
incident, maintenance Event status filter. Required. Must be a status valid for the given type (e.g. investigating/identified/monitoring/resolved for incidents; scheduled/ongoing/completed for maintenances).
investigating, identified, monitoring, resolved, scheduled, ongoing, completed 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.