Skip to main content
GET
List status page events

Restrictions

Usage

  • Returns every matching event in one response (no pagination), sorted by start_at_seconds, newest first.
  • Without start_at_seconds and end_at_seconds, the time window is unbounded.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Query Parameters

page_id
integer<int64>
required

Status page ID.

start_at_seconds
integer<int64>

Lower bound of the event activity window: only events still open at, or closed at or after, this Unix timestamp (seconds) are returned.

end_at_seconds
integer<int64>

Upper bound of the event activity window: only events started at or before this Unix timestamp (seconds) are returned.

type
enum<string>
required

Event type filter. Required.

Available options:
incident,
maintenance
status
enum<string>
required

Event status filter. Required. Must be a status valid for the given type (investigating/identified/monitoring/resolved for incident; scheduled/ongoing/completed for maintenance).

Available options:
investigating,
identified,
monitoring,
resolved,
scheduled,
ongoing,
completed

Response

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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

List of status page events.