| Code | Description / Developer message | Possible Solution |
|---|---|---|
| 400 | Your WhatsApp for Business API has been disabled | Contact support. |
| 400 | You have exceeded the endpoint rate limit. | Implement request throttling or exponential backoff to cool down API requests and avoid exceeding rate limits. Contact support. |
| 400 | Could not send message due to lack of payment. Messaging can resume once overdue invoices towards 360Dialog are settled. Please reach out to our integration partner. | Contact integration partner or support to resolve account billing issues. |
| 401 | Invalid API key | Check that the API is the correct and valid for the number you are trying to use. Generate another API key if required. Check the key value is being passed in the D360-API-KEY header. |
| 403 | The endpoint is blocked | Contact support to see if the specific endpoint can be enabled. |
| 500 | Internal server error | There are various reasons for this error. Contact support. |
| 502 | WhatsApp for Business API not available | Contact support. |
| Meta Error Code | Description | Possible Solutions | HTTP Status Code |
|---|---|---|---|
| 368 - Temporarily blocked for policies violations | The WhatsApp Business Account associated with the app has been restricted or disabled for violating a platform policy. | See the Policy Enforcement document to learn about policy violations and how to resolve them. Contact support. | 403 - Forbidden |
| 130497 - Business account is restricted from messaging users in this country. | The WhatsApp Business Account is restricted from messaging to users in certain countries. | Businesses can only send messages to countries they have been specifically approved for. This error is received when a message is sent to an unauthorized country. Cross-country messaging can be unlocked for an account by completing a scaling path to reach the 2,000 messaging limit tier. It may take up to 30 days for cross-country messaging to be unlocked after completing a scaling path. It may not be possible to send a cross-country message to recipients in Brazil and Indonesia even after a scaling path is completed. There is no known solution at this time. If the business's activities are prohibited in other countries, messaging recipients of said countries may result in this error as well. See WhatsApp Business Messaging Policy for details on allowed countries for messaging in your business category. | 403 - Forbidden |
| 131031 - Account has been locked | The WhatsApp Business Account has been restricted or disabled for violating a platform policy, or Meta were unable to verify data included in the request (e.g, the two-step pin included in the request is incorrect). |
Use the healthcheck endpoint, which may provide additional insight into the reason for the account lock. | 403 - Forbidden |
Unable to deliver message.
The following scenarios can cause a message to appear as sent but not delivered. For many of these reasons, Meta does not disclose the underlying cause of the error, due to privacy and policy reasons.
Recipient using an old WhatsApp version; must use the following WhatsApp version or greater:
Using a non-WhatsApp communication method, ask the WhatsApp user to:
Common problems:
131047 -
Re-engagement message
| More than 24 hours have passed since the recipient last replied to the sender number. |Send the recipient a business-initiated message using a message template instead. Threshold for expected behavior is ≤1%
In case the error occurs more frequently, please get in touch with customer support.
If you do receive this error code and suspect it is due to the limit, wait at least 24 hours before resending the template message. Doing so will only result in another error response since the limit may be in effect for differing periods of time. See Per-User Marketing Template Message Limits for additional information.
The error 131049 indicates that Meta intentionally chose not to deliver the message in order to maintain a healthy ecosystem engagement. In essence, the message was not sent to preserve the integrity of the ecosystem.
To prevent this error from occurring again, it's recommended not to attempt resending the message immediately after receiving this error. Instead, you should try sending the message at progressively longer intervals until it is successfully delivered, as the duration of the imposed limit can vary. Wait at least 24 hours before resending the template message.
This feature is deployed for all businesses, (even businesses with OBA) and there is no whitelisting list available. This limit is not active in these countries: European Economic Area, United Kingdom, Japan, South Korea
As mentioned in the Meta developer documentation:
"WhatsApp has found that per-user marketing template limits maximize marketing message engagement and improve the user experience, measured through improvements in user read rates and sentiment. This limit helps WhatsApp users find business messaging more valuable and feel less like they receive too many business messages.
Our per user marketing limit adapts automatically over time based on a person’s recent engagement levels. While this may mean delivering fewer messages to some users during periods of lower marketing read rates or overall inbox activity, rest assured your ability to reach people when they are most engaged will not change."
| | 131051 - Unsupported message type | Unsupported message type. | See [Messages](https://developers.facebook.com/docs/whatsapp/cloud-api/reference/messages) for supported message types before trying again with a supported message type. | | 131052 - Media download error | Unable to download the media sent by the user. |We were unable to download media included in the WhatsApp user's message. For more information, refer to the error.error\_data.details value in any messages webhooks triggered when this message was received.
Ask the WhatsApp user to send you the media file using a non-WhatsApp method.
| | 131053 - Media upload error | Unable to upload the media used in the message. |We were unable to upload the media for one or more reasons, such as an unsupported media type.
For more information, refer to the error.error\_data.details value in any messages webhooks triggered when this message fails to send.
We recommend that you inspect any media files that are causing errors and confirm that they are in fact supported. For example, in UNIX you can use file inspection via the command line to determine its MIME type:
file -I rejected-file.mov
You can then confirm if its MIME type is supported. See Supported Media Types.
| | 131057 - Account in maintenance mode | Buiness Account is in maintenance mode | The WhatsApp Business Account is in maintenance mode. One reason for this could be that the account is undergoing a throughput upgrade. | | 132000 - Template Param Count Mismatch | The number of variable parameter values included in the request did not match the number of variable parameters defined in the template. | See [Message Template Guidelines](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/) and make sure the request includes all of the variable parameter values that have been defined in the template. | | 132001 - Template does not exist | The template does not exist in the specified language or the template has not been approved. | Make sure your template has been approved and the template name and language locale are correct. Please ensure you follow [message template guidelines](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/). | | 132005 - Template Hydrated Text Too Long | Translated text is too long. | Check the WhatsApp Manager to verify that your template has been translated. See [Quality Rating and Template Status](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/#quality-rating-and-template-status). | | 132007 - Template Format Character Policy Violated | Template content violates a WhatsApp policy. | See [Rejection Reasons](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/#rejection-reasons) to determine possible reasons for violation. | | 132012 - Template Parameter Format Mismatch | Variable parameter values formatted incorrectly. | The variable parameter values included in the request are not using the format specified in the template. See [Message Template Guidelines](https://developers.facebook.com/docs/whatsapp/message-templates/guidelines/). | | 135000 - Generic user error | Message failed to send because of an unknown error with your request parameters. | The error you encountered was related to template restrictions, which are in place due to Meta security concerns. Unfortunately, Meta will disclose further details about these restrictions. Contact 360Dialog support | ## Meta Number Registration Errors | Code | Description | Possible Solution | HTTP Status Code | | ---------------------------------------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | | 1005 - Timeout | Registration timeout | Wait until the timeout phase has lapsed and try again. | 403 - Forbidden | | 1005 - Unknown error: biz\_link\_info\_invalid\_payload | The WhatsApp personal app or WhatsApp Business app account was not deleted. | Reinstall WhatsApp or WhatsApp Business and then [fully delete](https://faq.whatsapp.com/android/account-and-profile/how-to-delete-your-account/?lang=en) it. This will allow the number to be registered for the WhatsApp Business API. | 403 - Forbidden | | 1005 - This number has not been approved for an enterprise | The WhatsApp App or WhatsApp Business App account was not deleted. | Reinstall WhatsApp or WhatsApp Business and then [fully delete](https://faq.whatsapp.com/android/account-and-profile/how-to-delete-your-account/?lang=en) it. This will allow the number to be registered for the WhatsApp Business API. | 403 - Forbidden | | 1005 - There was an error verifying this phone number | This means that the registration has been locked. | Contact 360Dialog support. | 403 - Forbidden | ## Meta Embedded Signup (ES) Errors | Error Message | Description | Possible Solution | Screenshot | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | 360Dialog cannot onboard customers at this time | There is an issue with the partner's Tech Provider solution. The solution may not be live, or could be pending approval from 360Dialog. |The partner can use Integrated Onboarding instead of Embedded Signup.
Contact 360Dialog support.
The ban must be lifted by Meta before registration.
Contact 360Dialog support.
Unverified portfolios have a 2 WABA limit. Verified portfolios' WABA limit is 20.
Business verification must be completed.
Double-check if the user has admin access to the Meta business portfolio.
Create new user account with admin permissions, or give the existing user account admin permissions.
Contact 360Dialog if the issue persists.
If the phone number is on the WhatsApp personal app, delete the WhatsApp personal app account.
If the phone number is on the WhatsApp Business app, register it through Coexistence Onboarding.
Coexistence Onboarding (onboarding a WhatsApp Business app phone number to WhatsApp Cloud API) cannot continue due to one of the following:
Make sure to follow the Coexistence Onboarding guide and attempt onboarding again.
If the phone number is connected to another WABA with another BSP, disconnect the WhatsApp Business app from WhatsApp Cloud API:
If the steps above didn't work, or the phone number isn't on the WhatsApp Business app, contact 360Dialog support.
Contact the previous BSP's support team to remove their credit line from the WABA.
After the credit line is removed, disconnect the WhatsApp Business app from WhatsApp Cloud API:
1. Open the app,
2. Navigate to Settings > Account > Business Platform,
3. Press Disconnect Account.
Attempt onboarding again afterwards.
If the previous BSP cannot remove their credit line, a full WhatsApp Business app account deletion is required. Contact 360Dialog support for assistance.