The numeric Meta code and safe request details identify why a send failed. The general message “Meta rejected the request” is only a summary; use the exact code for the real cause.
Find an error code
| Code | What happened | What to do |
|---|---|---|
| Invalid request parameter | Check the recipient, media, template name, language, and component values. Correct the payload before retrying. | |
| Application request rate limit reached | Stop repeated requests and retry later with increasing delays. | |
| Permission denied | Confirm the Meta app, business, system user, and token have the required WhatsApp permissions. | |
| Access token invalid or expired | Create or obtain a valid token, update the account in WABotSender, and reconnect. | |
| WhatsApp Business Account rate limit reached | Pause sending and retry later. Avoid repeatedly restarting the same campaign. | |
| Message throughput limit reached | Wait before retrying and review the account throughput tier in WhatsApp Manager. | |
| Required parameter is missing | Complete every required template component and CRM mapping. | |
| Parameter value is invalid | Check formats, international phone numbers, media references, coordinates, and button values. | |
| Sender and recipient are the same number | Choose a recipient phone number different from the Cloud API sender. | |
| Message could not be delivered | Verify the full international number, WhatsApp availability, and recipient eligibility. | |
| Recipient is not allowed for the test account | Add the number to Meta test recipients or send from a live approved account. | |
| The 24-hour customer-service window is closed | Use an approved Meta template to start a new conversation. | |
| Sending paused because of quality or spam signals | Pause the campaign and review template quality, targeting, consent, and account quality. | |
| Meta chose not to deliver this marketing message | Do not retry immediately. Meta may limit marketing templates per person; wait and retry later only when appropriate. | |
| The recipient stopped marketing messages | Do not send more marketing messages to this recipient. Respect the opt-out. | |
| Message type is not supported | Use a component and media type supported by the approved template and Cloud API. | |
| Too many messages were sent to this recipient too quickly | Wait before retrying and reduce repeated sends to the same person. | |
| Template variable count does not match | Match the campaign mapping to every approved template variable in the correct order. | |
| Template or language could not be found | Sync templates, then confirm the exact template name, account, approval status, and language code. | |
| Rendered template text is too long | Shorten mapped values and template content before trying again. | |
| Template content or format was rejected | Correct the template in Meta, submit it again, and wait for approval. | |
| Template parameter format does not match | Verify whether the template uses named or numbered variables and map values to the same format. | |
| Template is paused | Review template quality in WhatsApp Manager and wait for Meta to restore it or use another approved template. | |
| Template is disabled | Resolve the disabled template in Meta or select another approved template. | |
| Button parameters do not match the approved template | Static URL buttons need no campaign parameter. Supply values only for dynamic URL, copy-code, Flow, or other approved parameterised buttons. | |
| Sending phone number is not registered for Cloud API | Register the phone number in Meta and confirm the Phone Number ID belongs to the connected account. | |
| Phone registration attempt limit reached | Stop retrying and wait before another registration attempt. |
No error codes match this search.
Errors reported most often
131049 — Meta chose not to deliver
This is an ecosystem health decision, often related to how many marketing templates a person has recently received. A successful API acceptance does not guarantee final delivery. Do not immediately repeat the same marketing message.
132018 — Button parameter mismatch
Your campaign components must match the approved template. A static website URL such as https://example.com requires no runtime parameter. Dynamic URLs, offer codes, and Flows require only the values defined by the approved template.
“Meta rejected the request” without a clear cause
Open the campaign recipient or report details and look for code=, details=, and the trace value. Check the connected account, the exact template name and language, mapped variables, recipient eligibility, and the 24-hour service-window rule.
Troubleshooting sequence
- Copy the exact numeric code and safe details from WABotSender.
- Confirm the campaign used the intended account, Phone Number ID, approved template, and language.
- Check every CRM mapping and template component, including header media and buttons.
- Review recipient consent, full international phone number, and test-account eligibility.
- Follow the recommended action above. Avoid immediate repeated retries for quality, rate-limit, or ecosystem errors.
Official Meta documentation
Meta can add or revise provider behaviour. Use the official Cloud API error-code reference when a code is not listed here.