WhatsApp error 131026: message undeliverable
Error 131026 means Meta could not deliver to that recipient. The usual cause is that the number is not registered on WhatsApp at all, though an outdated client or terms the user has not accepted produce the same code.
- Usually the number is not on WhatsApp
- Not a fault in your request
- Retrying the same number will not help
Nothing charged for 7 days. Cancel anytime.
Meta's code for a message that could not be delivered to the recipient.
Not on WhatsApp, an outdated client, or terms the recipient has not accepted.
Retries that help, because the condition is on the recipient side.
Why is a valid looking number undeliverable?
Because having a phone number is not the same as having WhatsApp on it.\n\nThe most common cause by far is that the recipient has never registered that number with WhatsApp, or has since removed it. Nothing about the number format reveals this, which is why a list imported from a CRM produces these errors in volume: it contains phone numbers, and only some of them are WhatsApp numbers.\n\nTwo less common causes produce the same code. The recipient may be on a WhatsApp client too old to receive the message type being sent, and they may not have accepted terms that a newer feature requires. Both are outside anything a sender can control.
What should happen when you get it?
Record it against the contact and stop sending to that number, rather than retrying.\n\nThe condition lives on the recipient side, so an immediate retry produces the same result and a scheduled retry usually does too. Treating it as transient is how an integration ends up burning throughput on numbers that will never receive anything.\n\nThe more useful response is to mark the contact as not reachable on WhatsApp and route them somewhere else, which is also what keeps a contact list from degrading quietly over time. If the number genuinely is on WhatsApp, the fix belongs to the recipient rather than to you.
Common mistakes
- Retrying on a schedule. The condition is on the recipient side and does not clear because time passed.
- Reading it as a formatting problem. The number reached Meta and was rejected at delivery, not at validation.
- Sending to a CRM list without filtering. A phone number is not necessarily a WhatsApp number.
EasyCoexistence keeps send failures on the connection timeline, so a pattern of undeliverable recipients is visible as a pattern rather than as scattered errors.
Frequently asked questions
Can I check whether a number is on WhatsApp first?
Not reliably, and Meta does not offer a lookup for it. In practice the first send is the check.
Does this affect my quality rating?
Undeliverable recipients are not the same as recipients who block or report you, but sending heavily to a list full of them is the kind of pattern that ends up showing elsewhere.
Is the number format the problem?
Usually not. Malformed numbers return a parameter error instead. This code means the number was understood and could not be reached.
Should I remove the contact?
Mark it as unreachable on WhatsApp rather than deleting it. The person may register that number later.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on