Skip to main content
POST
Reset post-mortem content

Restrictions

Usage

  • The report must be drafting and its current revision must equal expected_revision; otherwise the API returns 409 Conflict.
  • Reuse an idempotency_key only for the same report, revision, and Markdown content; different reuse returns 409 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 -g suffix). 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
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 fully replacing a drafting post-mortem report body.

post_mortem_id
string
required

Post-mortem ID to reset.

markdown
string
required

Replacement Markdown content. Limited to 4 MiB.

expected_revision
integer<int64> | null
required

Current content revision expected by the caller. Pass 0 for the first write to a document that has never been saved.

Required range: x >= 0
idempotency_key
string
required

Non-blank key for safely retrying this exact reset request.

Required string length: 1 - 128

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 a successful full post-mortem content reset.