We are sunsetting On-Premises API. Refer to our On-Premises API Sunset document for details, and to learn how to migrate to our next-generation Cloud API.
This document provides more information about the following types of error and status messages:
For Embedded Signup troubleshooting, see Embedded Signup Flow Errors.
Error Code | Description |
---|---|
| Failed to download the media from the sender. |
| Message failed to send because there were one or more errors related to your payment method.
Check your payment setup in WhatsApp Manager and try again. |
| Message failed to send because it was pending for too long (i.e., > 1 day). This is expected if the WhatsApp Business API client is down for more than a day, then restarted. Resend the message. |
| Message failed to send during its Time To Live (TTL) duration. |
|
|
| Message failed to send because there was an error related to your certificate. Download a new certificate from the WhatsApp Manager and re-register. |
| Message failed to send because there was an error related to your certificate. Download a new certificate from the WhatsApp Manager and re-register. |
| Occurs when a message is sent but the business client's certificate is not properly signed using the client's identity keys. This likely indicates that the client re-registered with new identity keys but did not go through the full certificate creation flow. |
| 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. |
| 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. Check your quality status in the WhatsApp Manager. See the Quality-Based Rate Limits documentation for more information. |
| Failed to send a message because this user's phone number is part of an experiment. Skip sending messages to this user. |
| Message failed to send since the user with this phone number has potentially changed. |
| Message failed to send because of an unknown error. Try again later. |
| Document messages with captions are currently not supported. |
| |
| Message length exceeds 4096 characters. |
| Valid recipient types:
|
| Possible UUID conflict for media upload request or media with that UUID already exists. |
|
|
| File or resource not found |
| Recipient is not on the allow list |
| Missing a required parameter. If you’re trying to send a List Message, it’s possible that you missed the If you’re trying to send a Single Product Message or a Multi-Product Message, it’s possible that you missed the |
| Value entered for a parameter is of the wrong type or other problem. If you’re trying to send a List Message, check if each row’s ID is unique. If you’re trying to send a Single Product Message, it’s possible that you have sent the wrong If you’re trying to send a Multi-Product Message, check that your |
| Contains a parameter that is not required. |
| |
| |
|
|
| Client-side rate limit has been hit |
| If the system is under heavy load, this error is returned to allow the system to recover from the load. |
| This error occurs when a master-only request, such as set settings, get settings, import, export, code request, register, etc. is sent to a node that is not a primary master. This could happen when the WhatsApp Business API Client is not setup properly or internal errors. Retrying the request should resolve this error. If this does not resolve the error, contact support. |
| This error occurs when requests are sent to a Coreapp node that is not the shard owner or in the process to become the shard owner. You might see this error when we are doing shard failover in the multiconnect setup. Retrying the request should resolve this error most of the time. If not, contact Support. |
| This error occurs when you send a message to yourself. |
| This error occurs if you have not configured the REST API Webhooks format. |
| |
| You are required to change your password. |
| The request is not valid. |
| Message Undeliverable. See the "Why is my delivery rate not 100%?" FAQ. |
| You sent a message to a WhatsApp user who has potentially changed, and a |
| Your account has been locked to send any messages due to an integrity policy violation. See WhatsApp Business Platform Policy Enforcement for information. |
| Number of parameters provided does not match the expected number of parameters. |
| Template status is not active, or template does not exist for a language and locale. |
| The receiver failed to download the template. |
| No templates exist for a specific language and locale. |
| Parameter length too long |
| Translated text too long |
| Whitespace policy violated |
| Format character policy violated |
| Media format used is unsupported |
| Required component in the Template is missing |
| URL in button component is invalid |
| Phone Number in button component is invalid |
| Parameter format does not match format in the created Template |
| Buttons are unsupported by the receiver |
| This error happens when a template message language pack has not been downloaded yet. |
| Message request contains below minimum or above the maximum number of sections. See You need to have at least 1 |
| There is an invalid number of rows. For List Messages, there must be at least one |
| Format character policy has been violated. |
| The section object has no products or the total product count has exceeded the maximum allowed number. |
| The catalog ID you provided either does not exist or does not belong to your WhatsApp Business Account (WABA). |
| The catalog ID you provided is not connected to the phone number you are using to send a message. |
| Some products provided in your request were not found in the catalog. |
| No products were found in the catalog you provided. |
| Only available for businesses in India. This error is returned when a business sends a Single Product Message with missing and incomplete e-commerce compliance information. |
| Only available for businesses in India. This error is returned when a business sends a Multi-product message with missing and incomplete e-commerce compliance information. |
| Only available for businesses in India. This error is returned when a business sends a Multi-product message where there is a mix of invalid products and products with missing compliance information. |
| Returned when the |
| Only available for businesses in India. This error is returned when a business has not provided any compliance information. See the Business Compliance endpoint. |
| Template status is |
| Template status is |
| Template status is |
| Flow with specified ID does not exist or does not belong to your WhatsApp Business Account (WABA), or it is in invalid state. |
| Flow message Version is invalid. See currently supported message version in Flows Changelog |
| Returned when Flow in |
| Unable to send |
| Flow is in blocked state. This error may also be returned if flow uses an endpoint and required setup is incomplete, e.g. public key is not uploaded or became invalid. See Implementing Endpoint for Flows. |
| Flow is in throttled state and 10 messages using this flow were already sent in the last hour. |
| Flow version is invalid or expired. See currently supported versions in Flows Changelog |
For Commerce Manager error codes specific to Indian businesses see the Business Help Center.
These are HTTP Status Codes that could be used by the WhatsApp Business API Client.
HTTP Code | Description |
---|---|
| Success |
| Success (OK) |
| Successfully created (For POST requests) |
| Found |
| Client Errors |
| Request was invalid |
| Unauthorized |
| Forbidden |
| Not found |
| Method not allowed. |
| Precondition failed |
| Message is rate limited |
| Too many requests |
| Server Errors |
| Internal server error |
| Timeout |