WhatsApp error 131055: Method not allowed
Last verified against Meta for Developers - Cloud API error codes
Only marketing template messages are supportedWhat error 131055 means
Code 131055 comes from the Marketing Messages API for WhatsApp, the POST /<PHONE_NUMBER_ID>/marketing_messages endpoint. That endpoint accepts only marketing template messages. Send it anything else (a free-form text, an interactive message, or a template categorized as AUTHENTICATION or UTILITY) and it can answer with HTTP 400 and (#131055) Method not allowed.
The message reads like an HTTP verb problem, which sends people checking whether they used POST. They did; the "method" here is the kind of message, not the HTTP method. Meta's send guide states the scope directly: freeform, authentication, service, and utility messages are not supported on /marketing_messages and will produce an error.
Your token, phone number, and recipient are fine. Route the message to the regular Cloud API /messages endpoint instead, or use a template that is actually categorized as MARKETING.
What it looks like
{
"error": {
"message": "(#131055) Method not allowed",
"type": "OAuthException",
"code": 131055,
"error_data": {
"messaging_product": "whatsapp",
"details": "Only marketing template messages are supported"
},
"fbtrace_id": "AXk2pQ7rLm9TzWb"
}
}Why it happens
- A sender that routes all outbound traffic through
/marketing_messagesafter an MM API migration. - An OTP or order update template (AUTHENTICATION or UTILITY) sent to the marketing endpoint.
- A customer service reply sent as type
textto the marketing endpoint. - A template you expected to be MARKETING that is actually in another category.
How to fix WhatsApp error 131055
- 1Check the
typein your payload; it must betemplate. - 2Look up the template's category in your template list and confirm it is MARKETING.
- 3Send non-marketing traffic to
POST /<PHONE_NUMBER_ID>/messagesinstead. - 4Retry the marketing template on
/marketing_messagesonce the routing is fixed.
How to stop it recurring
Route by category in one dispatcher: marketing templates to /marketing_messages, everything else to /messages. Keep the category in your template cache, refreshed from template status webhooks, so a recategorization changes routing automatically instead of producing a wave of 400s.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
- 134100: Only marketing messages supportedYou're only able to send marketing messages on this API.
- 131063: Marketing templates disabled for Cloud APIYour template is categorized as Marketing, but marketing templates are…
- 134101: Your template is still syncingWhen you send a message from a template, the template syncing process can take…
- 134102: Template unavailable for usePlease check your eligibility status to ensure you are onboarded or contact…
Error 131055 - quick answers
What does WhatsApp error 131055 mean?
Code 131055 comes from the Marketing Messages API for WhatsApp, the POST /<PHONE_NUMBER_ID>/marketing_messages endpoint. That endpoint accepts only marketing template messages. Send it anything else (a free-form text, an interactive message, or a template categorized as AUTHENTICATION or UTILITY) and it can answer with HTTP 400 and (#131055) Method not allowed .
How do I fix WhatsApp error 131055?
1. Check the type in your payload; it must be template . 2. Look up the template's category in your template list and confirm it is MARKETING. 3. Send non-marketing traffic to POST /<PHONE_NUMBER_ID>/messages instead. 4. Retry the marketing template on /marketing_messages once the routing is fixed.
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.