Reset post-mortem content
Replace the body of a drafting post-mortem report with Markdown.
Restrictions
Usage
- The report must be drafting and its current revision must equal
expected_revision; otherwise the API returns409 Conflict. - Reuse an
idempotency_keyonly for the same report, revision, and Markdown content; different reuse returns409 Conflict. - A successful reset disconnects the previous collaboration (Yjs) room. Reconnect to the new generation room
post-mortem-{accountId}-{postMortemId}-g{N}(generation 0 has no-gsuffix). The reset cannot be rolled back. - Markdown content is limited to 4 MiB.
- 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
Parameters for fully replacing a drafting post-mortem report body.
Post-mortem ID to reset.
Replacement Markdown content. Limited to 4 MiB.
Current content revision expected by the caller. Pass 0 for the first write to a document that has never been saved.
x >= 0Non-blank key for safely retrying this exact reset request.
1 - 128Response
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.