Skip to main content
POST
/
status-page
/
change
/
create
Create status page event
curl --request POST \
  --url 'https://api.flashcat.cloud/status-page/change/create?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "page_id": 5750613685214,
  "type": "incident",
  "title": "Web Console Degraded Performance",
  "description": "We are investigating degraded performance affecting the web console.",
  "status": "investigating",
  "start_at_seconds": 1712000000,
  "notify_subscribers": true,
  "updates": [
    {
      "status": "investigating",
      "description": "We are currently investigating an issue affecting some users.",
      "component_changes": [
        {
          "component_id": "01KC3GAZ6ZJE40H55GM31RPWZE",
          "status": "degraded"
        }
      ]
    }
  ]
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "change_id": 6294539747131,
    "change_name": "API Test Incident"
  }
}

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.

Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsStatus Pages Events Manage (on-call)

Authorizations

app_key
string
query
required

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.

Body

application/json

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.

page_id
integer<int64>
required

Status page ID.

type
enum<string>
required

Event type.

Available options:
incident,
maintenance
title
string
required

Event title, up to 255 characters.

Maximum string length: 255
status
enum<string>
required

Initial event status. investigating/identified/monitoring/resolved apply to incidents; scheduled/ongoing/completed apply to maintenances.

Available options:
investigating,
identified,
monitoring,
resolved,
scheduled,
ongoing,
completed
updates
object[]
required

Timeline updates. Immediate events normally pass one update; retrospective events must pass all historical updates.

description
string

Event description (Markdown). Required by the validator.

start_at_seconds
integer<int64>

Event start time in unix seconds. Defaults to now when omitted.

responders
integer<int64>[]

Member IDs responsible for this event.

linked_changes
string[]

Linked change IDs (related incidents, deployments, etc.).

close_at_seconds
integer<int64>

Scheduled close time for retrospective events. Must be greater than start_at_seconds.

notify_subscribers
boolean

Notify subscribers about this event and all its updates.

auto_update_by_schedule
boolean

Maintenance only: automatically advance the status based on the scheduled window.

is_retrospective
boolean

Mark this event as a retrospective (historical) one.

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
required

Result of creating a status page event.