Add a timeline update to a status page event.
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 appending an update to a status page event timeline.
Status page ID.
Target event ID.
New event status. Must match the event type. When the status transitions to resolved or completed, all referenced components must become operational.
investigating, identified, monitoring, resolved, scheduled, ongoing, completed Update timestamp in unix seconds. Defaults to now when omitted.
Update description (Markdown). Required.
Component status transitions applied by this update. Component IDs must be unique.
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.