BSG mirrors Meta's WhatsApp Cloud API errors — when a message can't be sent or delivered, we pass Meta's error code and description straight through, without renaming or reinterpreting them. The codes you see are Meta's codes, and the complete, authoritative list lives in Meta's WhatsApp Cloud API error codes documentation.
This guide covers the sending errors you're most likely to run into. (For problems while connecting your account, see Common Embedded Signup errors.)
How errors reach you
An error code and description come back in your send response and in delivery callbacks, and you can look them up later with Get Single Message Info (the error_code field). Meta formats the message as the code plus a short title — for example (#130429) Rate limit hit — with extra detail in error_data.
A quick way to triage: rejected means something on the request side needs your attention (parameters, a limit, or billing); undeliverable means the request was fine but the message couldn't reach the recipient.
Most common sending errors
132001 — Template not found or not approved
Meta: "The template does not exist in the specified language or the template has not been approved."
Why you might see it: a wrong template name or language.code, or the template isn't approved yet (or hasn't finished syncing into BSG from Meta).
What to do: confirm the exact name and language with Search WhatsApp templates, and make sure the template is Approved in WhatsApp Manager.
132000 — Parameter count doesn't match the template
Meta: "The number of variable parameter values included in the request did not match the number of variable parameters defined in the template."
Why you might see it: you sent more or fewer parameters than the approved template defines, or in the wrong order.
What to do: send exactly the parameters the template expects, in order. Check the template's structure with Get WhatsApp template.
131049 — Message not delivered (per-user limit)
Meta: "This message was not delivered to maintain healthy ecosystem engagement."
Why you might see it: Meta limits how many marketing messages a person receives across all businesses, so a slice of any large marketing send is expected to land here. (Related: Meta also doesn't deliver marketing templates to US (+1) numbers — see per-user limits.)
What to do: this is expected at scale, not a bug — don't retry immediately (wait at least 24h). Use a non-US number for marketing tests.
131026 — Message undeliverable
Meta: "Unable to deliver message." Reasons include: the recipient isn't a WhatsApp user, hasn't accepted WhatsApp's latest Terms, or is on a very old WhatsApp version.
Why you might see it: normal background noise on any large send.
What to do: confirm the recipient uses WhatsApp and that the number is correct; there's nothing to change in the request itself.
131042 — Payment method / billing not set up
Meta: "There was an error related to your payment method." Common causes: no payment method attached, credit line over limit or inactive, or timezone/currency not set.
Why you might see it: billing isn't fully configured on Meta — most common right after connecting.
What to do: with BSG you pay Meta directly, so set up billing in WhatsApp Manager → Account tools → Payment settings. See Meta's About Billing help article.
99 — Platform balance or plan limit reached (BSG-specific)
This one is from BSG, not Meta — it's the exception to "we mirror Meta." It means you've reached your BSG plan's message limit (the default is up to 1,000) or your platform balance is exhausted.
What to do: top up your balance, or contact your account manager to raise your plan limit.
When a send error is really a setup problem
Some sending errors trace back to how the account was connected rather than the request itself — most commonly 131042 (billing not set up) and phone-number registration errors. If sends started failing right after onboarding, check your connection first: see Common Embedded Signup errors.
Where to find every other error
Because BSG mirrors Meta, any code not listed here is defined in Meta's WhatsApp Cloud API error codes documentation.
Related guides
- BSG WhatsApp API Overview — sending, statuses, and error handling in context.
- Common Embedded Signup errors — problems while connecting your account.
- Getting started with 1-way WhatsApp on BSG — connecting your account, limits, and payme
Comments
0 comments
Article is closed for comments.