Skip to main content

Templates

Alert Templates define the user‑facing content delivered for alerts. They manage channel‑specific messaging (email, SMS, push, web), content type, locale, and publishing state, allowing institutions to customize how alerts are presented across channels and languages.

End-user benefits

  • Alerts use standardized templates to deliver easy‑to‑understand and uniform messages.
  • Messaging is tailored for each delivery channel to improve readability and usability.
  • Supports language and regional formats to ensure alerts are clear and appropriate for customers.

Integration capabilities

  • List templates with filters: alert type name, channel, id, locale, state (DRAFT, PUBLISHED, ARCHIVED).
  • Create, update, and delete templates; set content type, channel, locale, and vendor context where applicable.
  • Templates define the content of alerts by channel. Supports variable substitution using a variableMap for dynamic content like account numbers, balances, and transaction amounts.

Supported channels

ChannelDescription
EMAILEmail — subject and body
SMSSMS body
PUSHPush notification body
WEBWeb notification body

Template content types

Content typeDescription
EMAIL_SUBJECTEmail subject line
EMAIL_BODYEmail body
SMS_BODYSMS content
PUSH_BODYPush content
WEB_BODYWeb notification content

Scopes

ScopeDescription
alertMgmt:readRead alert types and associated templates
alertMgmt:writeWrite alert types and associated templates

Required headers

HeaderDescription
AuthorizationBearer OAuth 2.0 access token
transactionIdUnique request identifier

Error codes

System (PRMSYS_*)

CodeMessageHTTP Status Code
PRMSYS_10001Cross talk / concurrency error occurred400
PRMSYS_10002Malformed input data400
PRMSYS_10003Unknown application error occurred400
PRMSYS_10004Error occurred while validating JWT token400
PRMSYS_10005Resource of name already exists204
PRMSYS_10006Requested resource of identifier doesn't exist400
PRMSYS_10007Resource of identifier already exists400
PRMSYS_10008Requested resource of name doesn't exist400
PRMSYS_10015Required attribute missing400
PRMSYS_10016Non Printable ASCII character detected400

Validation (PRMVAL_*)

CodeMessageHTTP Status Code
PRMVAL_10001Path parameter doesn't match request body value400
PRMVAL_10002Invalid value for field400
PRMVAL_10003Invalid institution400
PRMVAL_10005Invalid channel type400
PRMVAL_10006Invalid alert type400
PRMVAL_10007Field is required400
PRMVAL_10008Field is invalid400

Endpoints