Troubleshooting Guide Error 131026 — Message Undeliverable Understand why WhatsApp messages fail to deliver with error code 131026, what causes it, and how to resolve it. |
What you'll learn
|
What is Error 131026? Message Undeliverable — the message was sent but could not be delivered to the recipient |
Known Causes All officially documented and commonly observed reasons for this error |
1. Recipient phone number is not on WhatsApp The phone number you are messaging has not registered a WhatsApp account, or the number no longer exists. This is the most common cause of error 131026. |
2. Recipient has blocked your business number If the recipient has blocked your WhatsApp Business number, messages cannot be delivered. Meta returns error 131026 without disclosing the block to protect user privacy. |
3. Recipient has not accepted Meta's Terms of Service or Privacy Policy If the recipient has not accepted WhatsApp's latest Terms of Service and Privacy Policy, some messages — particularly template messages — may fail to deliver. |
4. Recipient is using an outdated version of WhatsApp WhatsApp requires a minimum app version to receive Cloud API messages. If the recipient has not updated their app, messages with buttons, links, or media may fail. The minimum required versions are: |
5. Authentication template sent to an India (+91) number Authentication templates cannot be sent to WhatsApp users with a +91 (India) country code. This is a hard restriction from Meta — it is not a bug and cannot be bypassed. Use SMS, email, or another OTP channel for Indian numbers. |
6. Marketing message frequency limit reached Meta enforces Marketing Template Frequency Capping to protect users from receiving too many marketing messages from multiple businesses. If a user has already received several marketing messages from different businesses in a short period, further marketing messages may be blocked — even from businesses they have opted into. The exact limits are dynamic and not disclosed by Meta. |
7. Recipient is located in a restricted or sanctioned country Messages cannot be delivered to users in countries that are sanctioned or restricted under applicable laws and regulations. Meta does not disclose which specific countries are restricted in API responses. |
8. Business-to-Business (API to API) messaging The WhatsApp Business API is designed for businesses to message consumers — not for one API account to message another API account. Attempting to send a template message from one WhatsApp Business API account to another will consistently return error 131026. |
How to Diagnose the Cause Use this step-by-step method to narrow down the root cause |
|
|
|
|
How to Resolve It Actions to take based on the identified cause |
How to Prevent It Best practices to reduce error 131026 occurrences |
| |
| |
| |
| |
| |
|
Related Error Codes Other delivery errors you may see alongside 131026 |
Frequently Asked Questions Common questions about error 131026 |
Q: Will I be charged for messages that return error 131026? No. Messages that fail with error 131026 are not delivered and no conversation is opened, so you will not be billed for them. |
Q: Can I find out exactly why the message was not delivered? Not directly. Meta intentionally uses error 131026 as a broad code to protect recipient privacy. You can narrow it down using the diagnostic steps in this article, but the exact reason is not always disclosed. |
Q: Should I retry sending the message immediately after getting this error? No. Retrying immediately will not help and may make things worse if the cause is frequency capping. If you need to retry, use increasing time intervals between attempts. If the number is not on WhatsApp or has blocked you, retrying will never succeed. |
Q: My messages were delivering fine before but are now returning 131026 — what changed? A sudden increase in 131026 errors on marketing templates is most likely caused by Meta's marketing frequency capping. This enforcement has been expanding since 2024. Try sending utility messages to the same contacts and check if those deliver. If they do, the issue is specifically with marketing template delivery limits. |
Q: What is the difference between error 131026 and error 131049? Both indicate undeliverable messages, but error 131049 is specifically tied to Meta's marketing message frequency cap ("Healthy Ecosystem Engagement"). Error 131026 is broader and can be caused by multiple reasons including invalid numbers, blocked contacts, outdated app versions, and more. In some cases, frequency capping may still surface as 131026. |
Q: Can I send to India (+91) numbers at all? Yes — you can send Marketing and Utility templates to India (+91) numbers without issues. The only restriction is that Authentication templates cannot be sent to +91 numbers. This is a hard Meta rule and cannot be changed. |
Quick Summary Error 131026 means the message was not delivered. The most common causes are an invalid number, a blocked contact, or a marketing frequency cap. Use the diagnostic steps above to identify the cause, clean your contact list regularly, and always collect proper opt-ins before messaging. If the issue persists, contact our support team. |