Skip to main content
POST
Update post-mortem status

Restrictions

Usage

  • Requires the On-call Pro license.
  • The caller must be an account owner or admin, or a member of the report’s team; otherwise the call returns AccessDenied.
  • Status can move both ways. Only a drafting report accepts POST /incident/post-mortem/content/reset.
  • Publishing deletes uploaded media files that the report body no longer references.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for changing a post-mortem report status.

post_mortem_id
string
required

Post-mortem ID; obtain it from POST /incident/post-mortem/list.

status
enum<string>
required

Target report status.

  • drafting: being edited; the body can still be replaced with a content reset.
  • published: published; media files no longer referenced by the body are deleted.
Available options:
drafting,
published

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.