Create a template
Create a new notification template.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Templates Manage (on-call) |
Usage
template_namemust be unique within the account; duplicates returnInvalidParameter.- The server validates every non-empty channel template by rendering it against a mock incident — a syntactic error in any channel fails the whole request with
InvalidParameter. - Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
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
Create a new notification template.
Template name, unique per account. 1–39 characters.
1 - 39"Prod incident default"
Team scope. 0 for account-wide.
Free-form description. Up to 500 characters.
500Email body template source (Go html/template syntax).
SMS template source (Go text/template syntax).
Voice call script template source.
DingTalk robot message template source.
WeCom robot message template source.
Feishu robot message template source.
Feishu app message template source.
DingTalk app message template source.
WeCom app message template source.
Slack app message template source.
Microsoft Teams app message template source.
Telegram bot message template source.
Slack robot message template source.
Zoom bot message template source.
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.