WhatsApp API error 131064: Messaging limit reached for template classification violations
Error 131064 is an enforcement limit. Meta found that some of your templates were classified in a category that didn't match their content, typically promotional messages sent as utility, and has capped how much the account can send for a while.
Quick answer
Meta has limited your account's messaging because templates were misclassified. Review every template's category, move promotional content to marketing, and wait for the enforcement period to end.What WhatsApp error 131064 means
Meta documents 131064 as a throttling error: the message failed because the account reached its messaging limit due to template classification violations. Meta says the limit applies to both template messages and direct sends, and that it is lifted automatically after the enforcement period.
Why error 131064 happens
Limits like this are triggered by sending patterns rather than single messages. The patterns that usually cause it:
- Utility templates that carry offers, coupons or cross-sell lines, which makes them marketing.
- Authentication templates used for anything other than one-time codes.
- Template content edited after approval in a way that changed what it really is.
- Many near-identical templates created to work around an earlier recategorisation.
How to fix error 131064
Recovery takes time, so the aim is to stop making it worse and fix the cause meanwhile.
- List every approved template with its category and read each one as Meta would: does it sell anything?
- Move templates with any promotional content to the marketing category, even if most of the text is transactional.
- Split mixed messages: keep the order update in a utility template and put the offer in a separate marketing template for opted-in customers.
- Retire duplicate templates and keep one clearly categorised version of each message.
- Wait for the enforcement period to pass before sending at the previous volume.
Should you retry after 131064?
Retrying during the enforcement period fails the same way. Fix the template categories first, then resume once Meta lifts the limit; Meta lifts it automatically when the period ends.
How error 131064 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131064, the "(#131064)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 131064, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up.
Frequently asked questions
Does error 131064 block service replies too?+
Why would a utility template count as marketing?+
Send at volume without tripping limits
InfiQ queues and paces sends for you, and shows where rate-limit errors came from.