malipopaysmsservice_WabaCreateTemplateRequest
Lowercase letters, digits and underscores only.
Possible values: <= 512 characters
payment_receivedLike en or en_US. The language is part of the identity, so pick it deliberately.
enPossible values: [MARKETING, UTILITY, AUTHENTICATION]
components object[]required
Meta's own component array, with a BODY at minimum, optionally HEADER, FOOTER, BUTTONS or CAROUSEL. Validated against Meta's rules before submission, so a malformed template comes back immediately with a sentence you can act on rather than hours later as an unexplained rejection. The rules that actually cause rejections: a body cannot end with a variable, every variable needs an example, and placeholders are positional and sequential from 1.
Possible values: >= 1
Possible values: [HEADER, BODY, FOOTER, BUTTONS, CAROUSEL]
Optional. Defaults to your own connected account, falling back to the shared platform account if you have none.
Lets Meta re-file the template into another category rather than reject it outright.
{
"name": "payment_received",
"language": "en",
"category": "MARKETING",
"components": [
{
"type": "HEADER"
}
],
"wabaAccountId": "string",
"allowCategoryChange": true
}