WhatsApp API errors 131055 and 134100: only marketing messages allowed
Errors 131055 and 134100 mean you used Meta's Marketing Messages API for something other than a marketing template. That API only carries marketing templates; everything else goes through the Cloud API.
Quick answer
The Marketing Messages API accepts marketing templates only. Send utility and authentication templates, and free-form messages, through the Cloud API instead.What WhatsApp error 131055 means
Meta documents 131055, "Method not allowed", with HTTP 400: only marketing template messages are supported, and you may have sent a non-template message or an authentication or utility template. It documents 134100, "Only marketing messages supported", also HTTP 400, for sending a utility or authentication template where only templates categorised as marketing are allowed.
Why error 131055 happens
This code belongs to Meta's Marketing Messages API, so the cause sits in how marketing sends are routed or set up. Typically:
- All sends were switched to the Marketing Messages API, including order updates and one-time codes.
- A template was recategorised from marketing to utility, so it no longer qualifies.
- A free-form message or reply was sent through the marketing route.
How to fix error 131055
Work through these in order; the first one that turns up a problem is usually the fix.
- Route by category: marketing templates to the Marketing Messages API, everything else to the Cloud API.
- Check the template's current category before each send; categories can change after review.
- Send replies inside the customer service window through the Cloud API.
- Retry the failed messages on the right route.
Should you retry after 131055?
Resending on the same route fails. Send the message through the Cloud API, or use a marketing template if marketing is what you meant.
How error 131055 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 131055, a message beginning "(#131055)" 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. Keep transactional messages, such as order updates and one-time codes, on InfiQ's standard send path so they never depend on the marketing route.
Frequently asked questions
What's the difference between 131055 and 134100?+
Can I send OTPs through the Marketing Messages API?+
Why did a template that worked yesterday start failing with 134100?+
Send marketing on WhatsApp the right way
Campaigns, opt-in records and template quality in one place, so marketing messages reach the people who want them.