WhatsApp API error 131066: Message was not delivered to this user
Error 131066 is a new code Meta has announced for February 2027. It will say that a marketing message wasn't delivered to a user because of the template's quality or, for max price templates, the price you set.
Quick answer
From February 2027, 131066 means a marketing message was held back because of template quality or your max price. Improve the template's engagement or raise the price; changes improve chances but don't guarantee delivery.What WhatsApp error 131066 means
Meta documents 131066, "Message was not delivered to this user", with HTTP 400, as available from February 2027. It says the marketing message wasn't delivered based on template quality or, for max price templates, price, and that raising template quality (reads, clicks and other responses) or raising your price can improve future sends without guaranteeing delivery. Meta also says that from then on 131049 keeps its narrower meaning: not delivered to support a healthy messaging experience.
Why error 131066 happens
This code belongs to Meta's Marketing Messages API, so the cause sits in how marketing sends are routed or set up. Typically:
- A marketing template with low engagement: few reads, clicks or replies.
- A max price set below what it takes to win delivery for that user.
- Sending the same weak template to people who have ignored it before.
How to fix error 131066
There is no request change that gets this message delivered; the work is in your data and your audience.
- Separate 131066 from 131049 in your reporting so you know which lever to pull.
- Improve the template: a clearer offer, better timing, and audiences who want it.
- For max price templates, review the price against the value of the message.
- Don't resend the same message to the same person straight away.
Should you retry after 131066?
Retrying the same message doesn't change the outcome. Improve the template or the price for future sends instead.
How error 131066 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131066, the "(#131066)" 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 131066, 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.