Publish an incident post-mortem

POST

/organizations/{org_id}/incidents/{incident_id}/postmortem/publish

curl --request POST \
  --url https://api.perstat.io/organizations/example/incidents/example/postmortem/publish \
  --header 'Authorization: Bearer <token>'

• Production

Marks the incident’s post-mortem as published, making it eligible to appear on public status pages when its visibility is set to public. Returns the updated post-mortem, or 404 when none exists yet. Requires the incident command plan capability, otherwise 402. Accepts API keys with the incidents:write scope, subject to current role and resource grants.

Authorizations

• bearer

Parameters

Path Parameters

org_id

required

string

incident_id

required

string

Responses

200

Request succeeded. The response body contains the result.

Media typeapplication/json

Post-mortem (Nachbereitung) eines Incidents.

object

contributing_factors

required

string

impact

required

string

lessons

required

string

published_at_unix

integer | null format: int64

root_cause

required

string

status

required

string

summary

required

string

title

required

string

visibility

required

string

what_went_well

required

string

what_went_wrong

required

string

Example^generated

{
  "contributing_factors": "example",
  "impact": "example",
  "lessons": "example",
  "published_at_unix": 1,
  "root_cause": "example",
  "status": "example",
  "summary": "example",
  "title": "example",
  "visibility": "example",
  "what_went_well": "example",
  "what_went_wrong": "example"
}

401

Authentication is missing or invalid.

402

The request exceeds an entitlement or limit of the current plan.

403

The authenticated caller does not have permission to perform this operation.

404

No accessible resource matches the supplied identifier.