This document details the channel-specific status codes and the associated reasons for message delivery failure.
Columns
Please note that the 'Details' column is added in tables when there is additional information to be provided about the information in the 'Description' column.
Common Error Codes across Channels
| Error Code | Description |
|---|---|
| 7000 | Invalid JSON |
| 7001 | Authentication failed |
| 7002 | Service Key Missing |
| 7003 | Mandatory parameters missing |
| 7004 | Invalid parameters/Values |
| 7005 | Request expired |
| 7006 | Internal error occurred |
| 7007 | Service inactive |
| 7009 | Max number of destination address limited to 1000 |
| 7020 | You have reached the maximum transaction limit |
| 7104 | Invalid app id |
| 7200 | Unknown Status |
Apple Messages for Business
| Status Code | Description |
|---|---|
| 7000 | Invalid input details(JSON not correct) |
| 7006 | Internal server error |
| 7010 | Service provider exception |
| 7011 | Unknown Exception |
| 7301 | Message expired |
| 7307 | Endpoint not reachable |
| 7316 | Invalid application details |
| 7317 | Merchant API session failed |
| 7501 | Submitted |
| 7738 | Failed to upload media |
| 1001 | Queued |
| 7000 | Invalid JSON |
| 7001 | Authentication failed |
| 7002 | Service key missing |
| 7003 | Mandatory parameters missing |
| 7004 | Invalid parameters |
| 7007 | Service inactive |
| 7009 | Max number of destinations |
| 7722 | Parameter value is invalid |
Email
| Status Code | Description | Details |
|---|---|---|
| 7500 | Delivered | Returned when e-mail is delivered |
| 7501 | Submitted | Returned when e-mail sent to the gateway |
| 7520 | Bounce | The following bounce types are possible: - Undetermined: Indicates Amazon SES was unable to determine a specific bounce reason. - Permanent (general): Indicates Amazon SES received a general hard bounce and recommends that you remove the recipient's email address from your mailing list. - Permanent (no email): Indicates Amazon SES received a permanent hard bounce because the target email address does not exist. It is recommended that you remove that recipient from your mailing list. - Permanent (suppressed): Indicates Amazon SES has suppressed sending to this address because it has a recent history of bouncing as an invalid address. - Transient (general): Indicates Amazon SES received a general bounce. You may be able to successfully retry sending to that recipient in the future. - Transient (mail box full): Indicates Amazon SES received a mailbox full bounce. You may be able to successfully retry sending to that recipient in the future. - Transient (message too large): Indicates Amazon SES received a message too large bounce. You may be able to successfully retry sending to that recipient if you reduce the message size. - Transient (content rejected): Indicates Amazon SES received a content rejected bounce. You may be able to successfully retry sending to that recipient if you change the message content. - Transient (attachment rejected): Indicates Amazon SES received an attachment rejected bounce. You may be able to successfully retry sending to that recipient if you remove or change the attachment. |
| 7521 | Complaint | The following complaint types are possible: - Abuse: Indicates unsolicited email or some other kind of email abuse. - Auth-failure: Email authentication failure report. - Fraud: Indicates some kind of fraud or phishing activity. - Not-spam: Indicates that the entity providing the report does not consider the message to be spam. This may be used to correct a message that was incorrectly tagged or categorized as spam. - Other: Indicates any other feedback that does not fit into other registered types. - Virus: Reports that a virus is found in the originating message. |
| 7522 | Email address is not verified | This occurs when the account is in sandbox mode. Returned when destination email address is not verified. |
| 7523 | Invalid email address | Returned when destination email address is invalid. The email ID should be in the format: [email protected] where “abc” is the unique combination of string and numerics or one of the two, while “xyz” is the domain or server to be linked to. As part of the syntax, “@” and “.” are mandatory to ensure the validity of the email address. |
| 7524 | Email address max length reached | Returned when the maximum email length has been reached. According to the example above - “[email protected]”, the maximum length of “abc” should be less than or equal to 64 characters and the maximum length of “xyz.com” should be less than or equal to 255 characters. The total character length of the email address should not exceed 320 (inclusive of “@”). |
| 7535 | attachment length exceeded | Returned when overall email size including attachment exceeds the limit. For clients post version 5.63, the limit is 40MB. |
| 7536 | Exception while parsing the EMAIL Template, unable to fetch template | |
| 7240 | EmailId in bounce blocked list | Returned when the email has bounced |
| 7241 | EmailId in unsubscribe blocked list | * Returned when the destination email is found in Webex Connect unsubscribe list. |
| 7553 | SMTP Authentication Failed | |
| 7554 | SMTP Failures |
Google Business Messages
| Error Code | Description |
|---|---|
| 7900 | No error |
| 7904 | Request not authenticated due to missing, invalid, or expired OAuth token. |
| 7905 | Client does not have sufficient permission. This can happen because the OAuth token does not have the right scopes, the client doesn't have permission, or the API has not been enabled. |
| 7906 | A specified resource is not found. |
| 7909 | Either out of resource quota or reaching rate limiting. The client should look for google.rpc.QuotaFailure error detail for more information. |
| 7910 | Request cancelled by the client. |
| 7913 | API method not implemented by the server. |
| 7914 | Network error occurred before reaching the server. Typically a network outage or misconfiguration. |
| 7915 | Service unavailable. Typically the server is down. |
| 7916 | Request deadline exceeded. This will happen only if the caller sets a deadline that is shorter than the method's default deadline (i.e. requested deadline is not enough for the server to process the request) and the request did not finish within the deadline. |
| 7901 | Client specified an invalid argument. Check error message and error details for more information. |
| 7902 | Request can not be executed in the current system state, such as deleting a non-empty directory. |
| 7903 | Client specified an invalid range. |
| 7907 | Concurrency conflict, such as read-modify-write conflict. |
| 7908 | The resource that a client tried to create already exists. |
| 7911 | Unrecoverable data loss or data corruption. The client should report the error to the user. |
| 7917 | Unknown server error. Typically a server bug. |
| 7912 | Internal server error. Typically a server bug. |
| 7501 | Submitted |
| 7500 | Delivered |
| 7502 | Read |
| 7307 |
In-App Messaging and Live Chat
| Status Code | Description |
|---|---|
| 7500 | Delivered |
| 7501 | Submitted |
| 7502 | Read |
| 7000 | Invalid input details |
| 7006 | Internal server error |
| 7010 | Service provider exception |
| 7011 | Unknown Exception |
| 7301 | Message expired |
| 7304 | Invalid app credentials(Invalid OAuth) |
| 7305 | Invalid user credentials |
| 7307 | End point not reachable |
| 7308 | Invalid topic |
| 7309 | No topic subscribers found |
| 7310 | No segment found |
| 7311 | Thread or streamname required |
| 7312 | Invalid thread id |
| 7000 | Invalid JSON (Generic Template) |
| 7003 | param 'mediaid' or type based attachment is required (Generic Template) |
| 7004 | param 'title' in notification, is missed or empty (Generic Template) |
| 7034 | Max allowed elements reached - Upto 8 elements are allowed in attachments (Generic Template) |
| 7703 | Max allowed buttons in a section reached - Upto 3 buttons allowed in element (Generic Template) |
| 7704 | Duplicate identifiers not allowed (Generic Template) |
| 7708 | Max allowed image urls reached - Upto 5 allowed URLs in element (Generic Template) |
| 7004 | invalid value for param 'type' in rt attachment, only image, location, file, video and audio are allowed (Quick Replies) |
| 7003 | param 'mediaid' or type based attachment is required (Quick Replies) |
| 7704 | Duplicate identifiers not allowed (Quick Replies) |
| 7706 | Max allowed quick replies reached - max 5 quick replies will be allowed (Quick Replies) |
| 7026 | Request Json parameter size exceeded 4 KB (Quick Replies) |
Instagram
| Error Code | Description |
|---|---|
| 7000 | Invalid input details(JSON not correct) |
| 7307 | End point not reachable |
| 7302 | Rate limit exceeded |
| 7301 | Message expired |
| 7303 | Delivery notification of a message expired |
| 7006 | Internal server error |
| 7304 | Invalid app credentials(Invalid OAuth) |
| 7305 | Invalid user credentials |
| 7306 | Duplicate message |
| 7011 | Unknown Exception |
| 7501 | Submitted |
| 7500 | Delivered |
| 7502 | Read |
| 7010 | Service provider exception |
| 7526 | Either subscription messaging permission not enabled or invalid tag received from request |
| 7313 | Inbound message not received from user |
MMS
| Status Code | Description |
|---|---|
| 7144 | Delivery to the country code not supported |
| 7145 | Slide message max text size exceeded |
| 7146 | Max slides exceeded |
| 7147 | Quota exceeded at route level |
| 7148 | Invalid attachment type |
| 7212 | Invalid request. Make a valid request via GET/POST/XML with all the required variables |
| 7213 | User Authentication Failed |
| 7214 | This account has no API rights |
| 7215 | You can call API every X seconds |
| 7216 | This account has no rights to use this action |
| 7217 | XML Parse error: $error |
| 7218 | API not activated |
| 7219 | Invalid receiver number |
| 7220 | Invalid short code |
| 7221 | IP was not allowlisted. API call rejected |
| 7222 | Set throughput exceeded for this API action. API call rejected |
| 7223 | Phone number is in blocked list. API call rejected |
| 7224 | Account has reached the API request limit |
| 7225 | More than one object is not allowed in the same slide |
| 7226 | MMS audio/video/image are not allowed with object in the same slide |
| 7227 | Too many Slides |
| 7228 | Audio and Video not allowed in same slide |
| 7229 | Video and Image not allowed in same slide |
| 7230 | Text more than X characters |
| 7231 | Content not allowed |
| 7232 | Bad X slide duration |
| 7233 | This content does not exist |
| 7234 | The name is required |
| 7235 | No slides |
| 7236 | Slide X is empty |
| 7237 | Image in slide X is too big |
| 7238 | Audio in slide X is too big |
| 7239 | Video in slide X is too big |
| 7242 | Text in slide X is too long |
| 7243 | vCard in slide X is too big |
| 7244 | iCal in slide X is too big |
| 7245 | PDF in slide X is too big |
| 7246 | Passbook file in slide X is too big |
| 7247 | Image file in slide X is corrupted |
| 7248 | Could not copy Image in slide X |
| 7249 | Could not copy Audio in slide X |
| 7250 | Could not copy Video in slide X |
| 7251 | Could not copy vCard in slide X |
| 7252 | Could not copy iCal in slide X |
| 7253 | Could not copy PDF in slide X |
| 7254 | Could not copy Passbook file in slide X |
| 7255 | Internal error |
| 7256 | mmslink_expiration_date is invalid |
| 7257 | Carrier lookup failed. Please retry |
| 7258 | Carrier not provisioned |
| 7259 | The fallbacksmstext is required |
| 7260 | Invalid serviceid / serviceid is required |
| 7261 | Operator Not supported |
| 7262 | Unrecognized content type |
| 7263 | The ‘operator id’ is required |
| 7264 | Number is not subscribed in this campaign |
| 7265 | The campaignref is required |
| 7266 | Invalid campaignref |
| 7267 | Message failed at vendor |
| 7268 | Message rejected or not supported at vendor |
| 7269 | API access is blocked for this account. Please check the status of this account or its primary account if applicable |
| 7270 | Message delivery expired by operator |
| 7271 | Message delivery expired by application |
Messenger
| Status Code | Description |
|---|---|
| 7000 | Invalid input details(JSON not correct) |
| 7006 | Internal server error |
| 7010 | Service provider exception |
| 7011 | Unknown Exception |
| 7301 | Message expired |
| 7303 | Endpoint not reachable |
| 7313 | Inbound message not received from the user |
| 7500 | Delivered |
| 7501 | Submitted |
| 7502 | Read |
| 7526 | Either subscription messaging permission not enabled or invalid tag received from the request |
| 2018336 | The action is not submitted due to new privacy rules in Europe. See developer documentation for more information.98 |
| 2018047 | The action is not submitted due to new privacy rules in Europe. See developer documentation for more information. |
Push
| Status Code | Description | Details |
|---|---|---|
| 7500 | Delivered | The push was successfully delivered to the device. |
| 7501 | Submitted | The push was successfully submitted to the push service (APNS/FCM/HMS) for delivery |
| 7502 | Read | Generated when the user interacts with the push on the device. Note that this status does not occur if the user dismisses the push. |
| 7503 | Message expired before delivery attempt | Returned when the message is expired before attempting a delivery. The expiry value is configured in the request body. |
| 7504 | Authentication error | Returned when an authentication error occurs. |
| 7505 | Too large payload ( >4kb) | Returned when the payload is more than 4kb for Android. |
| 7506 | Invalid time to live value | Returned when an invalid value is passed for time to live parameter for Android |
| 7507 | Too many requests for the App | This error occurs when an Firebase receives too many requests for the same app, overloading the server. Firebase doesn't specify limits, but suggests using exponential back-off to mitigate this issue. |
| 7508 | GCM server error | Returned when an error occurs in Google Cloud Messaging server |
| 7509 | Too many concurrent requests for same customer | This error indicates messaging to a device exceeds the allowed rate. To address this, use exponential back-off. Note that FCM's limit for Android is 240 messages per minute or 5,000 per hour per device. |
| 7510 | Too big payload | Returned when the payload is more than 4kb for iOS. |
| 7511 | Invalid time to live value | Returned when an invalid value is passed for time to live parameter for iOS. |
| 7512 | Invalid push id | Returned when the push id is invalid. |
| 7513 | Unregistered Device | Returned when a device is not registered. |
| 7514 | Wrong apns certificate gateway | Returned when a wrong APNS certificate is provided. |
| 7515 | Bad apns certificate | Returned when an APNS certificate is invalid. |
| 7516 | Too many request for the same device | This error indicates the APNs server received too many requests for the same device token. Implement exponential back-off to mitigate this issue. |
| 7517 | APNS server error | Returned when an APNS server error occurs. |
| 7518 | Unknown | Returned when an unknown error occurs. |
| 7537 | Some tokens are successfully sent. Tokens identified by illegal_token are those failed to be sent | |
| 7538 | Some token parameters are incorrect | |
| 7539 | The number of tokens must be 1 when a synchronization message is sent | |
| 7540 | Incorrect message structure | |
| 7541 | The message expiration time is earlier than the current time | |
| 7542 | The collapse_key message field is invalid | |
| 7543 | The message contains sensitive information | |
| 7544 | OAuth authentication error | |
| 7545 | OAuth token expired | |
| 7546 | The current app does not have the permission to send push messages | |
| 7547 | All tokens are invalid | |
| 7548 | The message body size exceeds the default value | |
| 7549 | The number of tokens in the message body exceeds the default value | |
| 7550 | You are not authorized to send high-priority notification messages | |
| 7551 | System internal error | |
| 7560 | Request parameters were invalid. | Returns when any invalid value is given for any parameter in request body. |
| 7562 | The authenticated sender ID is different from the sender ID for the registration token. | Returned when push token of one app is used to send push notification for another app. |
| 7563 | Sending limit exceeded for the message target. | This error may result from exceeding either the overall message rate limit for an App asset or the device-specific limit. FCM has not documented these limits, however it recomends to employ an exponential back-off to resolve this error. |
| 7564 | The server is overloaded. | Returned when FCM server is overloaded. FCM has not documented any rate limits, however it recomends to employ an exponential back-off to resolve this error. |
| 7565 | An unknown internal error occurred. | Returned when the FCM server encounters an error while trying to process the request. |
| 7566 | APNs certificate or web push auth key was invalid or missing. | Returned by FCM when APNS certificate or web push auth key is either missing or invalid in your FCM project. To resolve this issue, please update your APNs certificate in your FCM project. |
| 7569 | Request not authenticated due to missing, invalid, or expired OAuth token. | The authentication token passed by 'Webex Connect' while submitting a push notification request to FCM was either invalid or expired. |
| 7570 | Client does not have sufficient permission. This can happen because the OAuth token does not have the right scopes, the client does not have permission, or the API has not been enabled. | Please be aware that any modification or deletion of scopes in the Google Cloud Service account can lead to this error. By default, Webex Connect adds the required scopes when generating an OAuth token. Additionally, users must verify that the HTTP v1 API is enabled within their Firebase project settings. |
| 7571 | Unregistered error returned from the FCM. | Returned by FCM when the token used is no longer valid and a new one must be used. |
| 7577 | Unknown server error. Typically a server bug. | Returned when an unknown server error occurs in the FCM server. |
| 7578 | API method not implemented by the server. | This occurs when a particular method is not working on the Google servers. |
RCS
| Status Code | Description |
|---|---|
| 7000 | Invalid input details - JSON |
| 7006 | Internal server error |
| 7010 | Service provider exception |
| 7011 | Unknown Exception |
| 7301 | Message expired |
| 7307 | Endpoint not reachable |
| 7500 | Delivered |
| 7501 | Submitted |
| 7502 | Read |
| 7740 | Invalid media details |
| 7318 | General Bad Request error for everything not caught in the specific error below |
| 7319 | Not Found |
| 7320 | Invalid JSON |
| 7321 | Invalid JSON Content (bad field, invalid phone number) |
| 7322 | Provider not configured for chatbot |
| 7323 | Unable to locate carrier for the recipient |
| 7324 | Max TPS reached |
| 7325 | Unauthorized access |
| 7326 | Internal System Error |
| 7327 | External System error |
| 7328 | Pass the error detail we have as error |
| 7329 | Carrier lookup process failure |
| 7330 | Includes: details from MaaP |
| 7331 | Rate limited at MaaP and retries expired |
| 7334 | MaaP returned a Failure IMDN |
SMS
| Status Code | Description | Details | Delivery Status |
|---|---|---|---|
| 7500 | Delivered | Returned when the message is transmitted to the destination network and confirmation of delivery is provided from the mobile handset. If the recipient did not receive the message, it may be due to spam, sender ID filters, or a corrupt or malformed message payload the handset was unable to process. | Delivered |
| 7501 | Submitted | Returned when the message has is in an interim status indicating submission to network provider, prior to it being actually delivered to the handset | Submitted |
| 7004 | Invalid parameters/Values | Returned when an invalid value or parameters are provided | Failed |
| 7006 | Internal server error | Returned when the message failed at the gateway and was not transmitted to the destination operator. This is may be an intermittent temporary error | Failed |
| 7101 | Invalid Sender ID | Returned when the sender is not authorized or configured at the destination operator or the wrong sender Id is being used for this request | Failed |
| 7102 | Invalid address | Returned when the address is invalid | Failed |
| 7109 | User in DnD | Returned when the user is registered on Do Not Disturb list | Un-Delivered |
| 7201 | Delivery failed at Operator | Returned when the message was routed to the operator but was rejected for various network-specific reasons (temp. failure or other network related issue) | Un-Delivered |
| 7202 | Delivery failed at platform | Returned when the delivery failed at platform | Un-Delivered |
| 7203 | Unknown Subscriber address | Returned when the number is an invalid mobile number on the destination network. This may indicate the subscriber is no longer valid, the number has ported away, or may have service blocks preventing message delivery | Un-Delivered |
| 7204 | Insufficient Credits in subscriber account | Returned when a message is sent to a prepaid mobile subscriber who no longer has a credit balance on their SIM card and can no longer receive messages | Un-Delivered |
| 7205 | Error in Binary message | Returned when there is an error in binary message. | Un-Delivered |
| 7206 | Can't deliver. Subscriber SIM Full | Returned when the subscribers SIM is full | Un-Delivered |
| 7207 | Subscriber out of coverage area or not reachable | Returned when the subscriber is out of coverage area | Un-Delivered |
| 7208 | Message expired | Returned when the message could not be delivered to the handset and exceeded its delivery time limit. This occurs when a subscriber has their handset turned off, or handset has no more memory to accept messages | Un-Delivered |
| 7209 | Unable to deliver multipart message | Returned when the message was sent as a multi-part message (either a long text message more than 160 chars which is split into multiple parts, or a message with specific character encoding) to the network destination and one or more of the parts was returned undeliverable. The specific error for the non-delivery is not disclosed and all parts of the message will be flagged with this error code | Un-Delivered |
| 7210 | Billing Configuration error | Returned when there is an error in billing configuration.This may be caused by an unexpected network destination, or due to a provisioning error. | Un-Delivered |
| 7211 | Billing error at operator | Returned when message could not be delivered as network operator has indicated there was a billing related error | Un-Delivered |
In addition to the existing SMS error codes, client tenants hosted in the United States and Canada regions have these additional error codes for SMS:
| Status Code | Description | Details | Delivery Status |
|---|---|---|---|
| 7111 | Spam content detected | Returned when the network operator has rejected this message as spam. Subsequent messages to the recipient may or may not be delivered depending on the underlying cause: -The sender ID has exceeded or violated carrier rules on message velocity (too many messages to the same recipient, too many messages from the same sender ID with sender ID restrictions). -The message content was marked as spam due to detected keywords. -The message was flagged for linking to websites suspected of spam or fraud. -The message content contained URL-shortening services that the network operator may have banned | Un-Delivered |
| 7280 | Message deleted | Returned when a network operator deletes the message for technical reasons related to network performance. | Un-Delivered |
| 7281 | Campaign error | Returned when the Sender ID (phone number) is not registered with an approved 10 DLC brand and campaign ID with the campaign registry and is blocked from transmitting messages to the operator. This could be caused by a missing configuration for the sender ID, the sender ID has changed or some other campaign-related error has occurred during submission. | Un-Delivered |
| 7282 | Invalid route | Returned when no valid route could be determined. The operator might not be supported or the number flagged as non-wireless (landline). | Un-Delivered |
| 7283 | Invalid operator or landline | Returned when the operator is not valid or the number is flagged as non-wireless (landline). | Un-Delivered |
| 7284 | Duplicate MT (caught by Duplication Guard) | Returned when message caught by duplicate guard | Un-Delivered |
| 7302 | Rate limit exceeded | Returned when the sender ID used to send traffic has exceeded its authorized TPS limit. 10 DLC registered numbers which are subject to rate limits will return such errors when exceeding the limits associated with their approved campaign IDs. The limits may be network operator, campaign or sender ID related. There could also be other throughput restrictions. Please note that campaign and brand limits apply across service providers and are shared by the brand and/or campaign – ensure that when using multiple service providers, you are not exceeding the limits across those providers. | Un-Delivered |
| 7513 | Unregistered device | Returned when the device is unregistered -The device inbox may be full at the device or network operator. -The device has been marked as busy by the network operator. -The device may have been flooded with messages and further submission to the device is not possible. | Un-Delivered |
| 7518 | Unknown | Returned when an unknown error occurs. The message may or may not have been delivered, but no additional information is available from the network operator. | Un-Delivered |
| 7607 | Invalid message type | Returned when the Message type is not accepted by the operator (like Binary messages, or unicode) | Un-Delivered |
| 7720 | Recipient blocked to receive messae | Returned when the recipient subscriber or operator is blocked to receive messages. | Un-Delivered |
Voice
| Code | Description |
|---|---|
| 7000 | Invalid JSON |
| 7003 | Dynamic Format - “Mandatory parameter missing: {{parameter}}” |
| 7004 | Dynamic Format - “Invalid parameter: {{parameter}}” |
| 7127 | Source IP not in the allowed list |
| 7016 | Unknown exception |
| 7020 | You have reached maximum transaction limit |
| 7101 | Invalid sender ID |
| 7102 | Invalid destination address |
| 7104 | Invalid app ID |
| 8009 | The profile doesn’t exist for this tenant |
| 7107 | Message length exceeded |
| 7108 | Invalid template ID |
| 7126 | Invalid content type |
| 7009 | Maximum number of destinations reached |
| 7022 | JSON size exceeded |
| 7005 | Request expired |
| 7519 | Call answered |
Voice - Logbook Error Codes
| Error Code | Description | Details |
|---|---|---|
| 1001 | Address Incomplete(Request-URI incomplete) | Call was rejected by User as the phone was busy |
| 1003 | User doest not exist | Call was rejected by User as the phone was busy |
| 1005 | User switched off | Call was not answered by User as the phone was switched off |
| 1007 | OBD-Timeout | Call was not answered by User as the phone was switched off |
| 2001 | No Service Configured for shortcode | Call was not answered by User as the shortcode service was not configured |
| 2002 | No answer from end user | Call was not answered by the user |
| 2003 | Subscriber Busy / Line is Busy | Call was not asnwered by User as the phone was busy |
| 2005 | End user Call dropped by Platform | Call dropped by the platform |
| 2006 | End user Call Rejected by Platform | Others, Call dropped due to internal error |
| 3000 | End user call dropped with unknown Error | Users' call was dropped due to unknown reason |
| 3002 | No response from Network / SIP Server Timeout | Timedout due to no reponse from the network |
| 3003 | ||
| 1010 | Number not in service/ Invalid Number | Customers number is not valid or not in service |
| 1002 | Call has been rejected by the receiver | Call was rejected by User as the user was busy |
| 2008 | Call Dropped by Network/End user | Call disconnected |
| 1011 | Call media capabilities Not Acceptable | Others, Call dropped due to internal error |
| 1009 | Malformed Request | Others, Call dropped due to internal error |
| 1012 | Number not supported / Invalid End User Number | Customers number is not valid or not in service |
| 1013 | Server received a request that does not match any dialog or transaction | Others, Call dropped due to internal error |
| 1008 | The server did not understand an event package specified | Others, Call dropped due to internal error |
| Other 1000, 2000, 3000 series | Call dropped due to internal error | Call dropped due to internal error |
WhatsApp
Error descriptions for each state are sent in additional info in the webhook
| Status Code | Description | Details |
|---|---|---|
| 7500 | Delivered | Returned when the message is delivered to the destination WhatsApp number. |
| 7501 | Submitted | Message submitted to WhatsApp for delivery. |
| 7502 | Read | Message read by the recipient. |
| 7010 | Service provider exception | Please refer to additional info object, part of the failed DR payload for more details. The error codes scenarios are captured in the following Meta documentations: Cloud API error codes and On-Premises API error code . 131026 and 1026 Marketing template message user limit has reached, refer template . page for more details. Cloud API will return error code 131026 and On-Premises API will return error code 1026. |
| 7011 | Unknown Exception | |
| 7701 | Media download error | Failed to download the media from the sender. |
| 7703 | Business eligibility - Payment issue | |
| 7704 | Message is not valid | Message failed to send because it was pending for too long. |
| 7705 | Message expired | Message failed to send during its Time To Live (TTL) duration. |
| 7706 | Rate limit hit | Message failed to send because there were too many messages sent from this phone number in a short period of time. Resend the failed messages. |
| 7707 | Unsigned certificate | Incorrect certificate. Message failed to send due to a phone number registration error. |
| 7710 | 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. |
| 7711 | 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. Check your quality status in the WhatsApp Manager. |
| 7712 | User's number is part of an experiment | Failed to send a message because this user's phone number is part of an experiment. Skip sending messages to this user. |
| 7713 | Generic error | Message failed to send due to an unknown error. Try again. If the error persists reach out to your support contact to raise a ticket with WhatsApp. |
| 7714 | Message too long | Length of the message exceeds 4096 characters. |
| 7715 | Invalid recipient type | The recipient type is not valid. |
| 7717 | Resource already exists | Possible UUID conflict for media upload request or media with that UUID already exists. |
| 7721 | Required parameter is missing | |
| 7722 | Parameter value is not valid. The namespace does not correspond to the WABA id. | Value entered for a parameter is of the wrong type or other problem. |
| 7723 | Parameter is not required | Contains a parameter that is not required. |
| 7726 | User is not valid | |
| 7727 | Internal error | Media upload failed due to bad image (image not uploaded correctly) or endpoint containing media was not found |
| 7729 | System overloaded | On-Premises system is under heavy load, wait for some time before trying again to allow the system to recover from the load. |
| 7730 | Not Primary Master | Retrying the request should resolve this error. If this does not resolve the error, reach out to your support contact. |
| 7731 | Not Primary Coreapp | Retrying the request should resolve this error. If this does not resolve the error, reach out to your support contact. |
| 7733 | Bad User | Sender and recipient phone number is the same. Send a message to a phone number different from the sender. |
| 7736 | Generic error | |
| 7802 | A user_identity_changedsystem notification requires acknowledgement | You sent a message to a WhatsApp user who has potentially changed, please re-authenticate the customer and reach out to your support contact to initiate acknowledgement with WhatsApp. |
| 7803 | Sender account has been locked | Your account has been locked to send any messages due to an integrity policy violation. See WhatsApp Business Platform Policy Enforcement for information. |
| 7804 | 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 and make sure the request includes all of the variable parameter values that have been defined in the template. |
| 7805 | Template Missing | Template status is not active, or template does not exist for a language and locale. |
| 7808 | Template Param Length Too Long | Parameter length too long |
| 7809 | Template Hydrated Text Too Long | Translated text too long |
| 7811 | Template Format Character Policy Violated | Template content violates a WhatsApp policy. See Rejection Reasons to determine possible reasons for violation. |
| 7812 | Template Required Component Missing | Required component in the Template is missing |
| 7813 | Template Invalid Hydrated URL | URL in button component of a Template is invalid |
| 7814 | Template Media Format Unsupported | Media format used in a Template is unsupported. |
| 7815 | Template Invalid Phone Number | Phone Number in Template button component is invalid |
| 7816 | Template Parameter Format Mismatch | Variable parameter values are formatted incorrectly. The variable parameter values included in the request are not using the format specified in the template. See Message Template Guidelines. |
| 7819 | Invalid number of sections | List Message request contains below minimum or above the maximum number of sections. You need to have at least 1 section object and you can have up to 10. |
| 7820 | Invalid number of rows | There is an invalid number of rows. For List Messages, there must be at least one rows object per section. |
| 7820 | Invalid number of rows | There is an invalid number of rows. For List Messages, there must be at least one rows object per section. |
| 7821 | Character Policy Violated | Format character policy has been violated. |
| 7830 | Invalid Header Structure | Returned when the header object structure is invalid. |
| 7832 | AuthException. We were unable to authenticate the app user. | Typically this means the Connect app access token has expired, been invalidated, or the user has changed a setting to prevent people from accessing their data. Reach out to you support contact for re-establishing the app. |
| 7833 | API Unknown. Invalid request or possible server error. | Reach out to your support contact and request to check the WhatsApp Business Platform Status page and check API status information before trying again. |
| 7834 | API Service. Temporary due to downtime or due to being overloaded. | Reach out to your support contact and request to check the WhatsApp Business Platform Status page and check API status information before trying again. |
| 7835 | API Method. Capability or permissions issue. | Reach out to your support contact to resolve the issue. |
| 7836 | API Too Many Calls | Try again later or reduce the frequency or amount of messages being sent |
| 7837 | API Permission Denied. Permission is either not granted or has been removed. | Reach out to your support contact to resolve the issue. |
| 7838 | Parameter is invalid. The request included one or more unsupported or misspelled parameters. | The request included one or more unsupported or misspelled parameters. |
| 7839 | Access token has expired | Reach out to you support contact for re-establishing the WhatsApp app |
| 7840 | Permission is either not granted or has been removed. | Reach out to your support contact for resolve the issue. |
| 7842 | 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. |
| 7845 | Rate limit hit. Cloud API message throughput has been reached. | The app has reached the API's throughput limit. See Throughput. Try again later or reduce the frequency with which the app sends messages. |
| 7846 | Service Overloaded | Reach out to your support contact and request to check the WhatsApp Business Platform Status page and check API status information before trying again. |
| 7849 | 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. |
| 7854 | Server Temporarily Unavailable | Reach out to your support contact and request to check the WhatsApp Business Platform Status page and check API status information before trying again. |
| 7860 | Account has been locked | The WhatsApp Business Account associated with the app has been restricted or disabled for violating a WhatsApp platform policy. See the Policy Enforcement document to learn about policy violations and how to resolve them. |
| 7862 | Hash mismatch | Returned when there is a mismatch in the customer’s hash key due to potential identity change. |
Contact Policy-integrated Error Codes
The error codes listed below are common across all Contact Policy-integrated channels. They are applicable only when Contact Policy block has been used when sending outbound messages or calls.
| Status Code | Message | Description |
|---|---|---|
| 9000 | Contact policy not enabled | Contact policy is not enabled. |
| 9001 | Contact policy inputs required | When the client is enabled with Contact Policy and the request doesn’t have all the required parameters to serve. For example, when a request sent does not have the Contact Policy Group parameter, this error message is returned. |
| 9002 | Recipient has not consented to message | The recipient has not provided consent to the received message. |
| 9003 | Requested consumer was not found in group | The requested consumer was not found in the group. |
| 9004 | Unable to reach Contact Policy Service, please try again later | Contact Policy Service is not reachable. |
| 9005 | Invalid or unknown group ID or channel | The Group ID or Channel referred to, is invalid or unknown. |
| 9006 | Frequency cap: Recipient has exceeded frequency cap | You have exceeded the configured contact frequency cap/limit. |
| 9007 | Frequency cap: The group was not found | The referred group was not found. |
| 9010 | Consent check failed, customer consent expired | The consent check has failed as the customer consent has expired. |