WhatsApp Error 131026: Message Undeliverable

WhatsApp error 131026 means the message is undeliverable — not a WhatsApp number, unaccepted Terms, or an outdated app. Causes and how to fix it.

TL;DR: WhatsApp error 131026 means the message could not be delivered — usually because the recipient is not a valid WhatsApp user, has not accepted WhatsApp's latest Terms, or is on an outdated app version. You cannot force delivery; verify the number and reach the user another way.

What Error 131026 Means

Meta's details lists the reasons: "Unable to deliver message. Reasons can include: The recipient phone number is not a WhatsApp phone number. Recipient has not accepted our new Terms of Service and Privacy Policy. Recipient using an old WhatsApp version; must use the following WhatsApp version or greater: Android 2.21.15.15, SMBA 2.21.15.15, iOS 2.21.170.4, SMBI 2.21.170.4, KaiOS 2.2130.10, Web 2.2132.6." Older community wording ("Receiver is incapable of receiving this message") refers to the same undeliverable family. Sending an authentication template to an Indian (+91) number can also surface delivery failures, as auth templates currently cannot be sent to users in India.

Where You See It

Both ways: as an immediate API error, and as a failed status webhook in statuses[].errors[] after the send initially returned 200 + a wamid. A 200 is not proof of final delivery — trust the failed status webhook as the final verdict.

Common Causes

  • Recipient number is not registered on WhatsApp.
  • Recipient never accepted the latest Terms of Service.
  • Recipient app version is below the minimum.
  • Policy/engagement signals (especially for marketing templates); Meta may not disclose a more specific private reason.

How to Fix It

  1. Verify the destination number is valid and active on WhatsApp, formatted in E.164.
  2. On another channel, ask the user to message your business, update WhatsApp, and accept the latest Terms.
  3. If the API returned 200 but the webhook later failed with 131026, treat the webhook as authoritative.
  4. Don't hammer-retry; treat persistent 131026 as an unreachable contact.

How to Prevent It

  • Validate and normalize numbers before queuing sends.
  • Collect explicit opt-in so contacts are real, reachable users.
  • Process failed status webhooks, not just immediate responses.
  • Suppress repeatedly-undeliverable numbers; see Meta BSUID & Contact Book Transition for contact-validation patterns.

Related Errors

FAQ

What is WhatsApp error 131026? A delivery failure — bad number, unaccepted Terms, or outdated app.

Why did the API return 200 but the message fail? Acceptance and delivery are different stages; the final verdict can arrive later in the status webhook.

Can I force delivery on 131026? No. Verify the number and use another channel.

Does 131026 always mean an invalid number? No — that's one cause among several.

How Dualhook Helps

This is a send-side error. Dualhook never touches message content and cannot deliver a message WhatsApp won't accept. Because message-path webhooks go directly from Meta to your endpoint, your backend must log and act on the final failed status; Dualhook surfaces 131026 rates so you can quantify and suppress unreachable contacts via Messaging Health Status.

Browse more docsStart Free Trial