.jpg)
Error 130497 is the code that stops an international rollout in one market while every other market keeps working. Meta documents it as "Business account is restricted from messaging users in this country," with an HTTP status of 403 Forbidden and a recommended action of consulting the WhatsApp Business Messaging Policy for details on allowed countries for messaging in your business category (Meta for Developers, WhatsApp error codes reference, retrieved 2026-08-20).
The phrase that matters is "in your business category." This is not a blanket country block. Country availability is evaluated against what your business does, which means two companies sending to the same market can get different answers, and a market that opened for one of your product lines may not be open for another.
That framing is what most coverage of this error misses, and it changes how you plan a rollout. This guide covers the mechanics, the diagnosis, and what to do when a market is genuinely closed. For the wider failure surface, our WhatsApp Business API error codes reference indexes the rest.
What the 403 Tells You
HTTP 403 means Meta understood the request, authenticated you successfully, and refused it on policy grounds. That immediately rules out several things teams check first:
- Your credentials are fine, so this is not error 0 or error 190
- Your template resolved, so it is not error 132001
- Your recipient number is well-formed, or you would see error 131009 or error 131026
- You are within your limits, so it is not throttling
What remains is a policy decision about your account messaging that country. And because it is a decision rather than a fault, retrying is pointless — the same request will be refused indefinitely.
Two other 403-returning codes sit nearby, and separating them saves time. Error 368 restricts your entire WhatsApp Business Account for a policy violation and stops everything. Error 131031 locks an account. Error 130497 is narrower than both: everything keeps working except sends to one country.
Code | Scope | Cause |
|---|---|---|
130497 | One recipient country | Category-based country availability |
Whole account | Policy violation | |
Account or number | Integrity lock or 2FA lockout |
Importantly, 130497 is not an enforcement action. Nothing about your sending behaviour caused it, it does not affect your quality rating, and it is not a step on the ladder toward account restriction. It is a market availability boundary.
Category Is the Variable
Meta's recommended action points at the Business Messaging Policy specifically for allowed countries in your business category, and that qualifier is the whole mechanism.
Country availability is not a single global list that applies to everyone. It is evaluated against what your business does. Some categories are broadly available; others are restricted in particular markets for regulatory or policy reasons — financial services, gambling, pharmaceuticals, and similar categories are the ones that most often encounter market-specific limits.
Three practical consequences:
Your competitor's experience is not evidence. A business in a different category messaging the same country successfully tells you nothing about your own eligibility.
Your own history is not evidence either. If you operate multiple product lines under different categories, or your category was updated, availability can change without anything about your sending changing.
Check before you build. The Business Messaging Policy is the authority, and consulting it during market planning costs nothing. Discovering a closed market after localising templates and building a campaign costs a quarter.
Meta does not publish a single static country-by-category table that stays current, which is why this article does not reproduce one. Any list you find in a blog post — including a list of "restricted countries" presented as fact — is a snapshot of unknown age. Read the policy itself for your category and market.
Diagnosing It
Confirm it is country-specific. Group recent failures by recipient country code. If 130497 appears only for one or two country codes while others deliver normally, that confirms the diagnosis and tells you exactly which markets are affected.
Check that the numbers really are in that country. A malformed number missing a country code can route unexpectedly. Numbers should be E.164, digits only, with the correct country code — the same normalisation that prevents error 131026 delivery failures. Rule this out before concluding a market is closed.
Read the Business Messaging Policy for your category. This is Meta's own recommended action and the only authoritative answer.
Confirm your registered business category is accurate. If your account is categorised as something that does not reflect your actual business, that misclassification may be producing a restriction that would not otherwise apply. Correcting it is a Business Manager task.
Do not retry, and do not route around it. Retrying against a 403 cannot succeed. Sending to the same recipients through a different phone number on the same business portfolio is worse — Meta associates business assets, and attempting to evade a policy boundary converts a market limitation into a compliance problem. Our guide to WhatsApp API compliance covers where that line sits.
When a Market Is Genuinely Closed
If the policy confirms your category cannot message that country, the honest answer is that WhatsApp is not available to you there for now. Three responses are legitimate.
Route that market to another channel. SMS, RCS, or voice reach those customers without a policy problem. For businesses already running multi-channel this is a routing rule rather than a project — our comparison of WhatsApp versus SMS for notifications covers the trade-offs, and RCS versus SMS covers the richer alternative where it is supported.
Suppress that country from WhatsApp audiences at query time. Not at send time. Filtering when the audience is built means a campaign physically cannot include those recipients, rather than generating a wall of 403s every send. This is the same principle that makes opt-out handling work in error 131050.
Re-check periodically. Country availability changes as policy and regulation evolve. A market closed at launch may open later, so a quarterly review is worth scheduling rather than treating the first answer as permanent.
What is not legitimate: routing through another account or number to reach restricted recipients. That is evasion, and it risks the account-level enforcement in error 368 across your whole business portfolio rather than the narrow limitation you started with.
Frequently Asked Questions
What does WhatsApp error 130497 mean?
Your business account is restricted from messaging users in that specific country. Meta documents it with HTTP status 403 and a recommended action of consulting the WhatsApp Business Messaging Policy for allowed countries in your business category. It is a policy boundary rather than a technical fault, and it affects only sends to that country.
Which countries are restricted on WhatsApp?
There is no single fixed list, because availability is evaluated against your business category rather than applied uniformly. Two companies in different categories can get different answers for the same market. Meta's Business Messaging Policy is the authority for your category, and any country list published in a blog post is a snapshot of unknown age.
Can I retry a message that failed with 130497?
No. The 403 is a standing policy refusal, not a transient condition, so the same request will be refused indefinitely. Suppress that country from your WhatsApp audiences when they are built, rather than generating repeated failures on every send.
Does error 130497 mean my account is in trouble?
No. Unlike error 368, which restricts your whole account after a policy violation, 130497 is a market availability limit. Nothing about your sending behaviour caused it, it does not affect your quality rating, and it is not a step toward account restriction.
Can I use a different number to reach a restricted country?
No, and attempting it is considerably riskier than the restriction itself. Meta associates business assets across a portfolio, so routing around a policy boundary is treated as evasion and can escalate a narrow market limitation into account-level enforcement affecting every number you operate.
Check Availability Before You Localise
Error 130497 is cheap to hit and expensive to hit late. The failure itself costs nothing — some undelivered messages to one market. What costs real money is discovering the boundary after translating templates, briefing a local team, and scheduling a launch.
Because availability depends on your business category rather than on a universal list, the check belongs in market-entry planning alongside business verification and billing setup. Read the Business Messaging Policy for your category and target market first, confirm your registered category actually reflects your business, and plan a channel alternative for markets that are closed.
And when a market is closed, suppress it at audience-build time and re-check quarterly. Availability moves; a permanent workaround built around a temporary limitation is the wrong shape.
Planning a multi-market messaging rollout? Helo.ai is a Meta Partner and Google RCS Anchor Partner of the Year, running WhatsApp, RCS, SMS, and voice from one platform so a country restriction becomes a routing decision rather than a blocked launch. Talk to an expert.
Next: error 368 if the restriction turns out to be account-wide rather than country-specific, or WhatsApp API compliance for the wider policy picture.
