Skip to main content
POST
Create or update post-mortem template

Restrictions

Usage

  • 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 creating or updating a post-mortem template.

name
string
required

Template name.

content
string
required

BlockNote JSON template content.

template_id
string

Template ID. Omit to create a new template; provide it to update an existing template.

team_id
integer<int64>

Managing team ID. Required when creating a custom template.

description
string

Template description.

content_markdown
string

Markdown version of the template content.

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

Post-mortem report template.