WhatsApp API Error Codes: What They Mean and How to Fix Them

A practical list of WhatsApp Cloud API error codes with meanings and fixes: 131026 undeliverable, 131047 outside the 24-hour window, 131049 per-user marketing limit, 131050 user stopped marketing, 130429 rate limit, 132xxx template errors, 133xxx registration errors and token errors.

Illustration: a WhatsApp Cloud API error response with code 131049 in a code window

WhatsApp Cloud API errors come back in two places: straight away in the API response (for problems with the request, token or account) and later in a status webhook marked failed (for messages Meta accepted but couldn’t deliver). Handle both, and build your logic on the numeric code and error_data.details, which Meta says to rely on rather than titles or HTTP status.

Below are the codes Indian businesses run into most, grouped by cause, with what each means and what to do, from Meta’s error code reference (updated June 2026).

Key takeaways

  • 131047: more than 24 hours since the customer last wrote. Send an approved template instead.
  • 131049: not delivered to protect “healthy ecosystem engagement” (per-person marketing limit). Wait at least 24 hours.
  • 131050: the person stopped your marketing messages. Don’t retry.
  • 131026: undeliverable, usually not on WhatsApp or an old app version. Check the number another way.
  • 130429 and 131056: you’re sending too fast. Slow down and retry with backoff.

Where WhatsApp API errors appear

WhereWhenShape
API responseThe request itself fails: bad token, wrong parameter, rate limit, account restricted{ error: { message, type, code, error_data: { details }, fbtrace_id } }
Status webhookMeta accepted the message but delivery failedstatuses[].status: "failed" with errors[] (code, title, message, error_data.details)
Other webhooksAccount or app problems, or an unsupported incoming messagevalue.errors or messages[].errors

Delivery errors (the ones marketers see)

CodeMeaningWhat to do
131026Message undeliverable: not a WhatsApp number, the person hasn’t accepted WhatsApp’s latest terms, or their app is too oldConfirm the number through another channel; don’t keep resending
131047More than 24 hours since the customer last repliedSend an approved template
131049Not delivered “to maintain healthy ecosystem engagement”: the per-user marketing limitWait at least 24 hours before trying again; send fewer, better offers
131050The person stopped marketing messages from youDon’t retry; mark them opted out (Meta’s user_preferences webhook tells you)
130472Held back by a Meta marketing message experimentNothing to fix; a small share of messages is held back in experiments
131048Spam rate limit: too many of your messages were blocked or flaggedCheck quality in WhatsApp Manager and pause the campaign
130497Your account can’t message users in that countryCheck the Business Messaging Policy for the destination

If 131049 and 131050 are common in your campaign reports, you’re sending too much marketing to the same people. More in WhatsApp broadcast limits and WhatsApp quality rating.

Rate limit errors

CodeMeaningWhat to do
130429Throughput reached for your number (80 messages per second by default)Queue and retry with exponential backoff
131056Pair rate limit: too many messages to the same person too quicklyWait before messaging that person again; others aren’t affected
131057Account in maintenance mode, for example during a throughput upgradeRetry after a short wait

Template errors (132xxx)

CodeMeaningWhat to do
132000Number of parameters doesn’t match the templateSend exactly the variables the template has
132001Template doesn’t exist in that language, or isn’t approvedCheck the name, language code and status
132005Text too long after filling in variablesShorten the variable values
132007Template content breaks policyEdit the content and resubmit
132012Parameter in the wrong formatMatch the type: text, currency, date, media
132015Template paused for low qualityEdit it to improve quality, or wait for the pause to end
132016Template paused too many times and permanently disabledCreate a new template
132068 / 132069WhatsApp Flow blocked, or throttledFix the Flow, or wait

Token, permission and account errors

CodeMeaningWhat to do
190Access token expiredUse a permanent system-user token
0 / 3 / 10 / 200–299Authentication or permission problemCheck the token in Meta’s access token debugger and the app’s permissions
100Invalid or misspelled parameterCheck the request against the endpoint reference
131008 / 131009Required parameter missing, or value invalidFix the request body
131021Sender and recipient are the same numberSend to a different number
131031Account locked, for example for a policy breach or a wrong two-step PINSee the policy enforcement notice and health status
131042Payment problem: no payment method, credit line issue, account suspendedFix billing in Meta Business Suite or with your provider
368Account restricted or disabled for a policy violationSee WhatsApp account restricted or banned
131000 / 131016Unknown error, or service temporarily unavailableRetry; check Meta’s status page

Phone number and media errors

CodeMeaningWhat to do
131045 / 133010Number not registered on the platformRegister it
133005Wrong two-step verification PINReset the PIN in WhatsApp Manager
133006Number must be verified before registeringRequest and enter a verification code
133016Too many register or deregister attempts (10 per 72 hours)Wait until the block lifts
131052Couldn’t download media the customer sentAsk them to send it again or another way
131053Couldn’t upload your mediaCheck the file type and size

Registration and PINs are covered in WhatsApp Cloud API phone numbers.

Handling errors well

  1. Log the code, details and `fbtrace_id` for every failure; Meta support asks for the trace ID.
  2. Retry only what can succeed: 130429, 131056, 131000 and 131016 with backoff; never 131050 or 132016.
  3. Respect people: treat 131050 as an opt-out and 131049 as “too much marketing”.
  4. Watch failure rates per template; a jump often means a pause or a quality problem.
  5. Alert on account-level codes (368, 131031, 131042): they stop all sending.

Error reports in Automate AI

Automate AI records the delivery status of every message. Campaign reports show sent, delivered, read and failed counts, and you can resend to failed numbers once the cause is fixed, or retarget people by what happened to the last message. Templates show Meta’s approval status, and opted-out contacts can be kept out of campaigns. See WhatsApp marketing.

Campaign details in Automate AI showing messages sent, delivered, read, failed and clicked
A campaign’s delivered, read and failed counts (sample data).

Frequently asked questions

What does WhatsApp error 131049 mean?

The message wasn’t delivered “to maintain healthy ecosystem engagement”: the person reached WhatsApp’s per-user limit for marketing messages. Meta advises waiting at least 24 hours before trying again.

What does WhatsApp error 131026 mean?

The message couldn’t be delivered, usually because the number isn’t on WhatsApp, the person hasn’t accepted WhatsApp’s latest terms, or their WhatsApp is very old.

How do I fix WhatsApp error 131047?

It means more than 24 hours have passed since the customer last messaged you. Send an approved template; free-form messages only work inside the 24-hour window.

What is WhatsApp error 130429?

You’ve hit your number’s throughput limit (80 messages per second by default). Queue messages and retry with backoff.

What does WhatsApp error 131050 mean?

The person has stopped marketing messages from your business. Don’t retry; mark them as opted out of marketing.

Sources

  1. Meta: Error codes (WhatsApp Business Platform)
  2. Meta: Status webhooks reference
  3. Meta: Per-user marketing template limits
  4. Meta: Throughput

WhatsApp rules and prices change. We check these guides against Meta’s documentation, but always confirm current terms with Meta before you rely on them. Questions? Message us on WhatsApp at +91 836 977 8812.