Error Messages
List of common API errors you might encounter.
Error Code | Descrption | What to do |
---|---|---|
403 | This URL *** is blocked | If you need access to a blocked / blacklisted endpoint, contact our support team. |
401 | Invalid API Key | If this happens, please double check you are using the correct API KEY for a number. If the problems persists, please generate a new API KEY. |
400 | WhatsApp Business API has been disabled | Response returned if WhatsApp Business API has been disabled. There are many reasons why the API might be disabled - cancellation, payment issues etc. If the number is disabled in error, contact our support team. |
400 | Endpoint calls limits has been exceeded | |
500 | Internal server error | The request failed. Please review your request payload. If the issue persists longer than 10 minutes, Contact our support team. |
502 | WhatsApp for Business API not available | Error returned if integration with WhatsApp Business does not exist in system or integration is not in running state (WhatsApp Business stack is not running). Contact our support team. |
555 | Internal server error | Our default servers may restart several times a day. When this happens, you may receive the error code 555. If this happens >3 times in 24 hours, contact support. |
1014 | Connection timed out. Please check if wacore is running | You are trying to send a message but the number if offline. A number can become offline for various reasons such as a server restart, or due to non compliance with the WhatsApp terms of service. If the number does not re-connect within 10 mins contact our support team. |
1016 | System overloaded | This error usually indicates that your webhook is not responding with status 200. This leads to a build up of webhooks in the DB and the system gets overloaded when the callback queue reaches 100K. Please check that your webhook is set and responding with status 200 for all incoming requests. |
2001 | Template name does not exist in the translation | You are trying to send a template that does not exist in Meta Business Manager or is not Approved for use. Please check your WhatsApp Manager > Account Tools> Message Templates and make sure the template is available and approved for use. |
Error Code | Description | What to do |
---|---|---|
402 | Message failed to send because there were one or more errors related to your payment method | Contact our support team and we will extend our Credit Line to your WABA. |
429 | Rate limit hit |
|
470 | Re-engagement message | Message failed to send because more than 24 hours have passed since the customer last replied to this number. Use a message template to respond. |
471 | Spam rate limit hit | Message failed to send because there are restrictions on how many messages can be sent from this phone number. This may be because too many previous messages were blocked or flagged as spam. |
1011 | Chat application is not initialized | This error occurs when you are trying to send a message on a number that is no longer registered for the WhatsApp API. A number can become unregistered for various reasons such as non compliance with the WhatsApp terms of service. If your number is unregistered, try to re-register the number or contact our support team. |
1016 | System overloaded | This error usually indicates that your webhook is not responding with status 200. This leads to a build up of webhooks in the DB and the system gets overloaded when the callback queue reaches 100K. Please check that your webhook is set and responding with status 200 for all incoming requests. |
Error Code | Description | What to do |
---|---|---|
1005 | Unknown error: biz_link_info_invalid_payload | This error occurs when you are trying to register a number for the WhatsApp API but the WhatsApp App account or WhatsApp Business app is not fully deleted. Please fully delete the existing WhatsApp Account from your device and then retry the registration for WhatsApp API.
|
| | |
| | |
Last modified 4mo ago