Update post-mortem basics
Replace the incident facts stored in a post-mortem report.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Incidents Manage (on-call) |
Usage
- Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
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
Basic incident facts to write back to a post-mortem report.
Post-mortem ID.
Highest severity among linked incidents.
Unix timestamp in seconds for the earliest linked incident start time.
x >= 1Unix timestamp in seconds for the latest linked incident close time. 0 when still open.
x >= 0Total incident duration in seconds.
x >= 0Responder member IDs to store on the report.
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.