WhatsApp API error 131063: Marketing templates disabled on Cloud API
Error 131063 means the template is categorised as marketing, and marketing templates have been switched off for your Cloud API configuration, so this route won't send them.
Quick answer
Marketing templates are disabled on your Cloud API set-up. Send marketing through the Marketing Messages API, or re-enable marketing templates on Cloud API.What WhatsApp error 131063 means
Meta documents 131063 as: your template is categorised as marketing, but marketing templates are currently disabled for your Cloud API configuration. This happens when the business has turned on the setting that disables marketing messages on Cloud API. Meta's options are to use the Marketing Messages API, or to turn that setting off again.
Why error 131063 happens
Account errors come from the set-up behind the number, not from the message. Check these:
- The account was set up to send marketing only through the Marketing Messages API, and the setting blocks it on Cloud API.
- A template you thought was utility was recategorised as marketing, so it now falls under the setting.
- Someone changed the account's marketing setting without telling the team that runs campaigns.
How to fix error 131063
Work through these in order; the first one that turns up a problem is usually the fix.
- Check the template's current category; it may have been recategorised to marketing.
- Decide which route should carry marketing messages for the account.
- Send the template through the Marketing Messages API, or re-enable marketing templates on Cloud API.
- If the template was meant to be utility, check whether Meta recategorised it to marketing, and remove any promotional content if it really is transactional.
Should you retry after 131063?
Resending on the same route fails. Switch the route, or change the setting, then send.
How error 131063 shows up in InfiQ
If Meta rejects the send straight away, InfiQ's API answers with an HTTP error that carries Meta's own error object: error.code 131063, a message beginning "(#131063)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.