Skip to main content
POST
Upsert status page template

Restrictions

Usage

  • Omit template.template_id to create a template; supply it to update one. An unknown template_id returns ResourceNotFound.
  • On update, empty fields keep their stored values. A predefined template’s type cannot be changed; a message template’s type can.
  • 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 creating or updating a status page template.

page_id
integer<int64>
required

Status page ID; obtain it from GET /status-page/list.

type
enum<string>
required

Template category. pre_defined for predefined event templates; message for notification message templates.

Available options:
pre_defined,
message
template
object
required

Template content. Shape depends on type: a predefined event template for pre_defined, a message template for message.

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

Result of upserting a status page template.