WhatsApp error 131063: Marketing templates disabled for Cloud API
Last verified against Meta for Developers - Cloud API error codes
Your template is categorized as Marketing, but marketing templates are currently disabled for your Cloud API configuration.What error 131063 means
Code 131063 means the WhatsApp Business Account has the disable_marketing_messages_on_cloud_api setting turned on, and you tried to send a template categorized as MARKETING through the regular Cloud API /messages endpoint. The account owner opted to push marketing traffic through the Marketing Messages API for WhatsApp instead, so /messages now rejects that category.
Meta documents that the setting only takes effect on accounts that have fully onboarded to the Marketing Messages API. There is one sharp edge: accounts that started onboarding but never signed the MM API terms can also hit 131063 from the /marketing_messages endpoint, because that endpoint's default fallback to Cloud API is itself blocked by the opt-in. With product_policy set to STRICT no fallback is attempted at all.
Utility and authentication templates are unaffected, and so are free-form replies inside the service window. Only the marketing category is blocked.
What it looks like
{
"error": {
"message": "(#131063) Marketing templates disabled for Cloud API",
"type": "OAuthException",
"code": 131063,
"error_data": {
"messaging_product": "whatsapp",
"details": "Your template is categorized as Marketing, but marketing templates are currently disabled for your Cloud API configuration. To send this template, use the Marketing Messages API for WhatsApp or enable marketing templates on Cloud API by turning off disable_marketing_messages_on_cloud_api."
},
"fbtrace_id": "ABzNMWIqsLJ7hbj8xd5ytay"
}
}Why it happens
- A teammate or partner set
disable_marketing_messages_on_cloud_apitotruewhile your sender code still targets/messages. - A template you treat as utility was recategorized to MARKETING by Meta, so it now falls under the block.
- The MM API terms were never signed, so
/marketing_messagestried to fall back to Cloud API and the fallback was refused. - Two systems share one WABA and only one of them was migrated to the new endpoint.
How to fix WhatsApp error 131063
- 1Read the flag with
GET /<WABA_ID>?fields=disable_marketing_messages_on_cloud_api. - 2If the account is meant to use the MM API, send marketing templates to
POST /<PHONE_NUMBER_ID>/marketing_messagesinstead. - 3If that move was not intended, re-enable Cloud API marketing sends with
POST /<WABA_ID>and{"disable_marketing_messages_on_cloud_api": false}. - 4Confirm the MM API terms are signed before relying on the flag, so fallbacks are not rejected.
- 5Check each failing template's current category with the template management endpoint; recategorized templates explain surprise failures.
How to stop it recurring
Route by category in one place: look up each template's category from the cached template list and pick /marketing_messages or /messages accordingly. Treat the WABA flag as shared configuration, document who may change it, and re-read it on a schedule so a change by a partner does not silently break campaigns.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
- 131055: Method not allowedOnly marketing template messages are supported
- 134100: Only marketing messages supportedYou're only able to send marketing messages on this API.
- 134102: Template unavailable for usePlease check your eligibility status to ensure you are onboarded or contact…
- 132001: Template does not existThe template does not exist in the specified language or the template has not…
Error 131063 - quick answers
What does WhatsApp error 131063 mean?
Code 131063 means the WhatsApp Business Account has the disable_marketing_messages_on_cloud_api setting turned on, and you tried to send a template categorized as MARKETING through the regular Cloud API /messages endpoint. The account owner opted to push marketing traffic through the Marketing Messages API for WhatsApp instead, so /messages now rejects that category.
How do I fix WhatsApp error 131063?
1. Read the flag with GET /<WABA_ID>?fields=disable_marketing_messages_on_cloud_api . 2. If the account is meant to use the MM API, send marketing templates to POST /<PHONE_NUMBER_ID>/marketing_messages instead. 3. If that move was not intended, re-enable Cloud API marketing sends with POST /<WABA_ID> and {"disable_marketing_messages_on_cloud_api": false} . 4. Confirm the MM API terms are signed before relying on the flag, so fallbacks are not rejected. 5. Check each…
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.