Engineering
WhatsApp error 131065: max price not available in that country
What Meta's max price feature for marketing messages does, why error 131065 appears in some countries, and how to send once you remove the unsupported setting.
By Broadchat teamPublished 5 min read
In short
WhatsApp error 131065 means you set a max price (a bid cap) on a marketing message to a country where Meta does not yet support that setting. Max price is an optional control that lets a business cap what it is willing to pay per marketing message; it reached open beta on 1 Oct 2026 and is not supported everywhere. The fix is to remove the max price parameter for that country, or skip setting one until Meta's documentation lists the recipient's market as supported.
Key takeaways
- 131065 fires when a marketing message request includes a max price for a country Meta has not enabled the feature in.
- Max price is a bid cap, not a discount: it limits what you are willing to pay per marketing message, and WhatsApp may not deliver a message if the real cost would exceed it.
- The feature reached open beta on 1 Oct 2026, after a limited beta earlier in the year, and Meta says it becomes required in eligible geographies only once it reaches general availability.
- The fix is to remove the max price field from the request for that market, not to retry the same call.
- Max price sits inside Meta's pricing and delivery controls for marketing sends, separate from per-user marketing limits (error 131049).
WhatsApp error 131065 means a marketing message request set a max price for a country where Meta does not support that control yet. The send fails before delivery because the parameter itself is not valid for that market, not because of anything wrong with the template, the recipient or your account.
What max price is
Max price is an optional bid-style setting for marketing messages: a business states the most it is willing to pay per delivered marketing message, and WhatsApp can hold back delivery rather than send at a cost above that cap. Meta rolled it out gradually: a limited beta from 15 May 2026, then open beta from 1 Oct 2026. Meta's documentation says that once the feature reaches general availability, expected in Q2 2027, it becomes required only "in eligible geographies", implying it will not apply everywhere even then.
Because the rollout is market by market, a max price value that works for one country can be rejected outright for another, even inside the same campaign or API call.
What triggers 131065
The error appears when your request to send a marketing template includes a max price, and the recipient's country is not among the markets Meta currently supports the setting for. Common ways this happens in practice:
- A campaign tool or integration sets a default max price for every send, without checking the setting per country.
- A business copies a working request from one market (where max price is supported) to another market's number without removing the field.
- Meta changes which countries support the feature between beta phases, and a previously working value stops being accepted.
What to do
- Remove the max price parameter from the request for the country that returned 131065, and resend. The template and recipient are not the problem.
- Check Meta's current list of supported countries before setting a max price for a new market; the list changes as the beta expands toward general availability.
- If you need cost control everywhere, manage it through your own campaign budgeting and segment sizing instead of relying on max price in markets it does not yet cover.
- If you integrate directly with the Cloud API or the Marketing Messages API, make the max price field conditional on the recipient's country rather than a fixed default across all sends.
Where this fits in the Marketing Messages API
Max price is one of several delivery controls Meta has added alongside the Marketing Messages API for WhatsApp (generally available since 19 November 2025), which optimises delivery toward people likely to engage and adds its own benchmarks and recommendations. Max price can be used from either the Cloud API or the Marketing Messages API, but its country coverage is the same underlying beta, so a country missing from the list returns 131065 regardless of which API sent the request. It is unrelated to per-user marketing limits (error 131049), which govern how often one person receives marketing messages rather than what you are willing to pay per message.
Finding it in Broadchat
Broadchat's campaign sending does not set a max price by default, so most partners will not meet 131065 unless they call Meta's API directly with it set for an unsupported market. If you send templates through the channel API and plan to experiment with max price, check the recipient country against Meta's current supported list first, since the setting is still rolling out and coverage can change between its beta phases. For the full list of Cloud API codes, see the WhatsApp API error codes cheat-sheet, and for current per-message costs see WhatsApp API pricing. Background on the platform is in what the WhatsApp Business API is.
Sources
- WhatsApp Business Platform changelog — Meta for Developers, checked 12 October 2026
- Pricing on the WhatsApp Business Platform — Meta for Developers, checked 12 October 2026
- Cloud API error codes — Meta for Developers, checked 12 October 2026
Broadchat team · Product and partner success team
The people who build and support Broadchat, the white-label WhatsApp Business API platform. We write from what we see while onboarding partners and their clients on the official WhatsApp Cloud API, and we check every article against Meta's current documentation.
Last updated:
Frequently asked questions
What does WhatsApp error 131065 mean?
It means your marketing message request included a max price (a bid cap on what you will pay per message) for a country where Meta does not yet support that setting. Remove the max price for that country and resend.
Is max price the same as Meta's per-message rate?
No. Meta's rate card sets what a delivered message actually costs. Max price is an optional cap a business can set on top of that, so WhatsApp can hold back a send rather than deliver it above the cap the business chose.
Which countries support max price?
The list changes as the feature moves through its beta phases toward general availability, expected in Q2 2027, when Meta says it becomes required only in eligible geographies. Check Meta's current documentation for the countries covered before setting a max price for a new market.
Will retrying the same request fix error 131065?
No. The request fails because the parameter itself is not valid for that country, so retrying without changes returns the same error. Remove the max price field for that market, then resend.