Skip to main content
POST
Delete a template

Restrictions

Usage

  • If an escalation rule still uses the template, the call returns HTTP 400 ReferenceExist with data.refs (kind = escalate_rule, the rule name, a console href).
  • The template’s status becomes deleted: it disappears from /template/list and its name can be reused, but /template/info still returns it.
  • An unknown or already-deleted template_id returns InvalidParameter.
  • Only an account admin, the template creator, or a member of the template’s owning team may call this; others get AccessDenied.
  • 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

Request body carrying a template ID.

template_id
string
required

Target template ID. Pass 6321aad26c12104586a88916 to address the built-in preset.

Pattern: ^[0-9a-fA-F]{24}$
Example:

"6605a1b2c3d4e5f6a7b8c9d0"

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

An empty object. Returned as the data payload by operations whose success signal is simply the absence of an error.