Your task is to use the context that was given and to output it in markdown format and clean it up
Remove the following:
- image links
- this page helpful parts
- grid layout where mentioned
- mentioned imports like import { WasThisPageHelpful } from '@components/WasThisPageHelpful' and other react references/info
- any react components or html tags and keep only the text
Other instructions:
-don't change wording, word order, words itself or add any punctuation
-do not change any of the content meaning and facts, just clean up the formatting and convert to markdown
-if you see selectwrapper with options, just combine with the table below it and render it as markdown info
-if you get table in md format, don't change anything in it
-if you see any text in the format [text](link), leave it in the same place, dont change it or move it
-remove imports from the top of the file like import { WasThisPageHelpful } from '@components/WasThisPageHelpful' and other react references/info if they exist
-do not put duplicated content and do not put notes about duplicated content
-do not change the text enclosed in '---' at the beginning of the file, it is used for metadata
-do not explain what you did, just output the result
-return full file, don't skip or remove anything that is not mentioned in the instructions
:/# Response status and error codes
When using our API, you may encounter certain **status** and **error** codes that you need to understand or troubleshoot. This page contains a list of all codes with thorough descriptions and action steps you need to take if you are looking to resolve a problem
Note
To quickly locate a specific response status or error code on this page, use your browser's native search functionality by pressing **Ctrl+F** (Windows) or **Command+F** (Mac) and typing the code name or keyword you want to find
By referencing this guide, you can quickly identify and address problems to ensure smooth integration and seamless communication with our platform
Need more help?
If you cannot find a solution for your issue on this page and need further assistance, please contact our [Support](mailto:support@infobip.com)
## HTTP status codes
Every HTTP transaction has a status code sent back by the server to define how the server has handled the transaction. The most common statuses you may encounter are
- **200 OK**
- **404 Not Found**
- **401 Unauthorized**
Check out [the list of the HTTP status codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) to learn more
## API status codes
Besides the standard HTTP status code, the status object may be returned as part of the API response message, delivery report, or message log
**Status object example:**
```json
{
"groupId":3,
"groupName":"DELIVERED",
"id":5,
"name":"DELIVERED_TO_HANDSET",
"description":"Message delivered to handset"
}
```
## General status codes
Status codes are grouped into status code groups with their own unique ID
### Pending [#pending-general-status-codes]
**Group ID: 1**
The message has been processed and sent to the next instance, for example, a mobile operator. Note that this does not mean the message has been delivered to the handset. For the full delivery status, use delivery reports instead
| ID | Status | Description |
|:---:|------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 3 | `PENDING_WAITING_DELIVERY` | Message has been successfully sent from the platform to the operator's end, but we are awaiting a delivery report from their end.
In case the delivery itself is impacted, the causes can be the availability of the destination, network issues, congestion, or additional setup requirements. |
| 7 | `PENDING_ENROUTE` | Message has been successfully accepted and processed by the platform and forwarded to the next instance, which specifically involves the mobile operator. |
| 26 | `PENDING_ACCEPTED` | Message is pending after being accepted by the system and waiting for further processing or delivery confirmation from the operator. |
### Undeliverable [#undeliverable-general-status-codes]
**Group ID: 2**
The message has not been delivered
| ID | Status | Description |
|:---:|---------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 4 | `UNDELIVERABLE_REJECTED_OPERATOR` | Message was rejected by the operator and deemed undeliverable, possibly due to a network glitch or restrictions imposed by the operator.
Resolution steps include contacting [Support](mailto:support@infobip.com) for further clarification or resolution. |
| 9 | `UNDELIVERABLE_NOT_DELIVERED` | Message was not delivered to the intended recipient and considered undeliverable, typically due to factors such as an invalid or unreachable destination number.
Resolution steps involve verifying the accuracy of the recipient's number. If the issue persists, contact [Support](mailto:support@infobip.com) for assistance. |
| 31 | `UNDELIVERABLE_NOT_SENT` | The message has not been sent |
| 96 | `NO_ANSWER` | The call was successfully delivered to the end user device; however, it was not answered by the end user |
| 97 | `BUSY` | The call has been successfully delivered to the end user's device, but the end user's device indicates that they are currently busy and unable to answer the incoming call |
| 98 | `CANCELLED` | The call was canceled at the origination end before it could be successfully routed to the end user |
### Delivered [#delivered-general-status-codes]
**Group ID: 3**
The message has been delivered
| ID | Status | Description |
|:---:|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
| 2 | `DELIVERED_TO_OPERATOR` | Message has been successfully delivered to the operator's system and awaits further processing or delivery to the recipient's handset. |
| 5 | `DELIVERED_TO_HANDSET` | Message has been successfully delivered to the recipient's handset |
### Expired [#expired-general-status-codes]
**Group ID: 4**
The message has been sent and has either expired due to pending past its validity period (the platform defaults to 48 hours), or the delivery report from the operator has returned `EXPIRED` as a final status
| ID | Status | Description |
|:---:|--------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 15 | `EXPIRED_EXPIRED` | Message was received and sent to the operator. However, it has been pending until the validity period has expired or the operator returns the `EXPIRED` status.
Resolution steps include contacting [Support](mailto:support@infobip.com) for further clarification or resolution. |
| 29 | `EXPIRED_DLR_UNKNOWN` | Message has expired, and the delivery status is unknown, indicating that the delivery report or confirmation was not received or could not be determined.
Resolution steps involve contacting [Support](mailto:support@infobip.com) to resolve the unknown delivery status. |
| 87 | `SIGNALS_BLOCKED` | Message has been rejected due to an anti-fraud mechanism. The message is charged to the customer. |
### Rejected [#rejected-general-status-codes]
**Group ID: 5**
The message has been received but has either been rejected by Infobip or the operator has returned `REJECTED` as final status
| ID | Status | Description |
|:----:|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 6 | `REJECTED_NETWORK` | Message has been received, but the network is either out of our coverage or is not set up on your account.
Your account manager can inform you about the coverage status or set up the network in question. Otherwise, reach out to [Support](mailto:support@infobip.com). |
| 8 | `REJECTED_PREFIX_MISSING` | Message has been received but rejected as the number is not recognized due to an incorrect number prefix or length. This information is different for each network and is regularly updated. |
| 10 | `REJECTED_DND` | Message has been received and rejected because the user is subscribed to DND (Do Not Disturb) services, disabling any service traffic to their number. |
| 11 | `REJECTED_SOURCE` | Your account is set to accept only registered sender IDs, and the sender ID defined in the request has not been registered on your account. |
| 12 | `REJECTED_NOT_ENOUGH_CREDITS` | Your account is out of credits for further submission.
Top up your account. For assistance in topping up or applying for an online account top-up service, contact your account manager or [Support](mailto:support@infobip.com).|
| 13 | `REJECTED_SENDER` | The sender ID has been blocklisted on your account through the web interface.
Remove the blocklist on your account or contact [Support](mailto:support@infobip.com) for further assistance. |
| 14 | `REJECTED_DESTINATION_BLOCKLISTED` | The destination address has been blocklisted either at the operator's request or on your account through the web interface.
Remove the blocklist on your account through the web interface or contact [Support](mailto:support@infobip.com) for more information. |
| 17 | `REJECTED_PREPAID_PACKAGE_EXPIRED` | Account credits are past their validity period.
Top up your subaccount with credits to extend the validity period. |
| 18 | `REJECTED_DESTINATION_NOT_REGISTERED` | Your account has been set up for submission only to a single number for testing purposes.
Contact your account manager or reach out to Support to remove the limitation. |
| 19 | `REJECTED_ROUTE_NOT_AVAILABLE` | Message has been received on the system. However, your account has not been set up to send messages, that is, no routes on your account are available for further submission.
Your account manager can set up your account based on your preference. Otherwise, reach out to [Support](mailto:support@infobip.com) for more information. |
| 20 | `REJECTED_FLOODING_FILTER` | Message has been rejected due to an anti-flooding mechanism. By default, a single number can only receive 20 varied and 6 identical messages per hour.
If a requirement exists, the limitation can be extended per account on request to your account manager or [Support](mailto:support@infobip.com). |
| 21 | `REJECTED_SYSTEM_ERROR` | The request has been rejected due to an expected system error.
Retry the submission or contact [Support](mailto:support@infobip.com) for more details. |
| 23 | `REJECTED_DUPLICATE_MESSAGE_ID` | The request has been rejected due to a duplicate message ID specified in the submit request; the message IDs should be a unique value.
For more information, see the [SMS](https://www.infobip.com/docs/api/channels/sms) section on the Infobip API Developer Hub. |
| 24 | `REJECTED_INVALID_UDH` | Message has been received and our system detected the message was formatted incorrectly because of either an invalid ESM class parameter or an inaccurate amount of characters when using esmclass:64 (UDH).
For more information, see [User Data Header](https://en.wikipedia.org/wiki/User_Data_Header) and [Concatenated SMS](https://en.wikipedia.org/wiki/Concatenated_SMS) or contact [Support](mailto:support@infobip.com) for clarification. |
| 25 | `REJECTED_MESSAGE_TOO_LONG` | Message has been received, but the total message length is more than 25 parts, or the message text exceeds 4000 bytes as per our system limitation. |
| 51 | `MISSING_TO` | The request has been received, but the `to` parameter has not been set, or it is empty, that is, there must be a valid recipient to send the message to. |
| 52 | `REJECTED_DESTINATION` | The request has been received, but the destination is invalid—the number prefix is incorrect as it does not match a valid number prefix by any mobile operator. Number length is also taken into consideration when verifying number validity. |
| 87 | `SIGNALS_BLOCKED` | Message has been rejected due to an anti-fraud mechanism. If the message is deemed fraudulent, it will not be charged. |
| 99 | `REJECTED` | The call was rejected/declined by the end user at the receiving end. |
| 100 | `UNDELIVERABLE_REJECTED_PLATFORM` | The request was rejected due to being invalid, malformed, or because the service is temporarily unavailable. Review the request parameters and structure, and try again when the service is accessible. |
## Voice status codes
### Rejected [#rejected-voice-status-codes]
**Group ID: 5 - Voice status codes**
The message has been received but has either been rejected by Infobip or the operator has reverted to `REJECTED` as the final status
| ID | Status | Description |
|:----:|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 53 | `REJECTED_INVALID_AUDIO_FILE_URL` | The URL of the audio file is invalid and could not be read properly. |
| 54 | `REJECTED_UNSUPPORTED_LANGUAGE` | The language submitted within the request is not supported and the request could not be processed correctly. |
| 55 | `REJECTED_MESSAGE_IS_EMPTY` | Native to Voice services, this status is returned when no text is sent in your Voice message request. |
| 56 | `REJECTED_INVALID_NOTIFY_URL` | Native to Voice services, this status is returned when the `notifyUrl` parameter is not formatted properly.
For more information, see [Voice messages over API](https://www.infobip.com/docs/voice-and-video/voice-messages#voice-messages-over-api). |
| 57 | `REJECTED_INVALID_NOTIFY_CONTENT_TYPE` | Native to Voice services, this status is returned when the `notifyContentType` parameter is not formatted properly.
For more information, see [Voice messages over API](https://www.infobip.com/docs/voice-and-video/voice-messages#voice-messages-over-api). |
| 58 | `REJECTED_INVALID_DTMF_SIGN` | Defined value for repeating the message is invalid and must be a positive number. |
| 59 | `REJECTED_INVALID_DTMF_TIMEOUT` | Defined value for the waiting period is invalid and must be a positive number. |
| 60 | `REJECTED_INVALID_RING_TIMEOUT` | Defined value for the duration of the call is invalid and must be a positive number. |
| 61 | `REJECTED_INVALID_CALL_TIMEOUT` | Defined value for the total period of the call is invalid and must be a positive number. |
| 62 | `REJECTED_INVALID_MACHINE_DETECTION` | The action which attempts to detect answering machines at the beginning of the call is invalid. |
| 63 | `REJECTED_INVALID_ACTIONS` | Actions submitted in HTTP API request are invalid. |
| 64 | `REJECTED_INVALID_ACTION_GROUPS` | Action groups submitted in HTTP API request are invalid. |
| 83 | `REJECTED_MACHINE_DETECTION_DISABLED` | Machine detection is not enabled.
Contact your dedicated account manager or reach out to Support. |
| 87 | `REJECTED_INVALID_DELIVERY_TIME_WINDOW` | Invalid `deliveryTimeWindow`. The time gap between **from** and **to** cannot be less than 1 hour. |
| 91 | `REJECTED_INVALID_SSML` | Submitted message text contains invalid SSML. |
## MMS status codes
### Rejected [#rejected-mms-status-codes]
**Group ID: 5 - MMS status codes**
The message has been received but has either been rejected by Infobip or the operator has reverted to rejected as the final status
| ID | Status | Description |
|:----:|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
| 56 | `REJECTED_INVALID_NOTIFY_URL` | Status is returned when the `notifyUrl` parameter is not formatted properly. |
| 77 | `REJECTED_MESSAGE_TEXT_TOO_LONG` | Message has been received, but the textual part of the message length exceeds 1600 characters, which is the system limitation. |
## Email status codes
### Rejected [#rejected-email-status-codes]
**Group ID: 5 - Email status codes**
The email has been received but has either been rejected by Infobip or the operator has reverted to rejected as the final status
| ID | Status | Description |
|:----:|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 75 | `REJECTED_FREE_TRIAL_EXCEEDED` | This status code is returned by the API when a user's free trial has been exceeded.
It means the user has exceeded the allowed number of messages or usage limits and must upgrade to continue using the service. |
| 88 | `REJECTED_DATA_TRANSFORMATION_FAILED`| This status code is returned by the API when there is an error in the data transformation process while creating the data needed to proceed with sending a mail.
Errors can include placeholder size exceeding limits or data failing to parse (for example, custom headers). |
| 89 | `REJECTED_INTERNAL_ERROR` | This status code is returned by the API when there is an internal error with the system processing a message.
This occurs when a message exceeds retry limits or when internal data fails to parse. |
| 90 | `REJECTED_VALIDATION_FAILED` | This status code is returned by the API when a validation check fails during message processing.
Errors can be caused by issues such as an invalid sender, an invalid landing page, invalid preserved recipients, a missing template, and so on. |
### SMTP enhanced status codes [#smtp-enhanced-status-codes-email-status-codes]
**SMTP responses** include enhanced status codes that indicate whether a request was successful, temporarily rejected, or permanently rejected
For a complete list of codes and their meanings, see the [SMTP enhanced status codes](https://www.infobip.com/docs/email/email-over-smtp/smtp-enhanced-status-codes) page
## Push notifications status codes
### Undeliverable [#undeliverable-push-notifications-status-codes]
**Group ID: 2 - Push notifications status codes**
The message has not been delivered
| ID | Status | Description |
|:----:|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 66 | `UNDELIVERABLE_NO_DESTINATION` | The status occurs when a `TO` object in a Push API call defines a filter that does not resolve any `pushRegistrationIds` as destinations for Push delivery. The `to` field is used to query the message recipient segment.
For example, you can target a **tag** that does not exist in any instance of the requested `ApplicationCode`. In this case, no destinations are found.
Alternatively, you can target all application instances (devices) that use Android OS. Here `CloudType: GCM` resolves all destinations and sends the message to all linked devices.
To verify your valid registrations, use the filtering options in the Infobip [web interface](https://portal.infobip.com/login).
For more information about user data, refer to the following links: [iOS](https://github.com/infobip/mobile-messaging-sdk-ios/wiki/) and [Android](https://github.com/infobip/mobile-messaging-sdk-android/wiki/). |
### Rejected [#rejected-push-notifications-status-codes]
**Group ID: 5 - Push notifications status codes**
The message has been received but has either been rejected by Infobip, or the operator has reverted to rejected as final status
| ID | Status | Description |
|:----:|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 65 | `REJECTED_NO_APPLICATION` | The status occurs when an invalid or non-existent `ApplicationCode` is used in the `from` field of a Push API call.
Each application profile has a unique `ApplicationCode`, which is used in the SDK as a key identifier for the application installed on an end user's device and enables communication with the platform.
For each paired device and installed application, a `pushRegistrationId` is issued and uniquely linked to the `ApplicationCode`. You can [get all available applications](https://www.infobip.com/docs/api/channels/mobile-app-messaging/get-push-applications) or check the configuration. |
## Moments status codes
### Pending [#pending-moments-status-codes]
Below are the possible status codes for batch flow processing
| ID | Status | Description |
|:----:|--------------------|------------------------------------------------------------|
| 200 | `PENDING_ACCEPTED` | A person has been accepted and is going to be processed by Flow. |
## Error codes
Error object can be returned as part of the send message response or delivery report response
Error object example:
```json
{
"groupId":0,
"groupName":"OK",
"id":0,
"name":"NO_ERROR",
"description":"No Error",
"permanent":false
}
```
## General error codes
Error codes are grouped into error code groups with their own unique ID
### OK [#ok-general-error-codes]
**Group ID: 0**
The request has been completed successfully
| ID | Permanent | Error | Description |
|:---:|:---------:|--------------|----------------------------------------------------------------------------------------------------------------|
| 0 | false | `NO_ERROR` | There is no error description provided. Mostly, it is returned for successful delivery or when the operator did not return any error code. |
### Handset errors [#handseterrors-general-error-codes]
**Group ID: 1**
The request has not been completed due to handset-related issues
| ID | Permanent | Error | Description |
|:----:|:---------:|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | true | `EC_UNKNOWN_SUBSCRIBER` | Typically, this indicates that the subscriber or recipient of the message is unknown or not recognized by the network.
Verify the subscriber details by dialing the number. If correct, contact [Support](mailto:support@infobip.com). |
| 2 | false | `EC_UNKNOWN_BASE_STATION` | Suggests an error involving an unidentified or unrecognized base station, often in the context of network or communication systems.
This could be due to a missing or inaccessible base station. |
| 5 | false | `EC_UNIDENTIFIED_SUBSCRIBER` | This can occur for reasons such as an invalid or unregistered number, incomplete or incorrect subscriber information, or technical issues.
Verify and correct subscriber information. If correct, contact [Support](mailto:support@infobip.com). |
| 6 | false | `EC_ABSENT_SUBSCRIBER_SM` | Indicates the destination numbers were unreachable, powered off, or in an area with limited coverage.
Ensure the subscriber's device is turned on and has a stable network connection. |
| 7 | false | `EC_UNKNOWN_EQUIPMENT` | The mobile device has not been recognized by EIR (Equipment Identity Register) during device verification on the MAP protocol level at the operator’s infrastructure. |
| 8 | false | `EC_ROAMING_NOT_ALLOWED` | The subscriber is roaming in another country or operator’s infrastructure. Delivery is not guaranteed due to a lack of roaming agreements between operators. |
| 9 | true | `EC_ILLEGAL_SUBSCRIBER` | Indicates the mobile station failed authentication, often due to the subscriber's number being blocklisted.
Investigate and address the issue with the network operator, or contact [Support](mailto:support@infobip.com). |
| 11 | true | `EC_TELESERVICE_NOT_PROVISIONED` | The mobile subscription does not support the requested service (for example, SMS).
Contact the service provider or network operator to activate the required teleservice. |
| 12 | true | `EC_ILLEGAL_EQUIPMENT` | Indicates the IMEI check on the handset failed due to the IMEI being blocklisted or unauthorized.
Use authorized equipment to resolve this issue. |
| 13 | false | `EC_CALL_BARRED` | The operator suspended the subscriber’s service, usually for unpaid invoices.
Check the subscriber's account status and ensure sufficient balance or contact the network operator to resolve. |
| 21 | false | `EC_FACILITY_NOT_SUPPORTED` | The requested service is not supported by the handset or network.
Verify the supported facilities and ensure compatibility. Restart the device and apply the latest software/firmware updates. |
| 27 | false | `EC_ABSENT_SUBSCRIBER` | Indicates the destination numbers were unreachable, powered off, or in an area with limited coverage.
Ensure the subscriber's device is turned on and has a stable network connection. |
| 31 | false | `EC_SUBSCRIBER_BUSY_FOR_MT_SMS` | Indicates that the subscriber is busy for MT SMS. |
| 32 | false | `EC_SM_DELIVERY_FAILURE` | Indicates a failure in delivering an SMS to the recipient, possibly due to unavailability, memory capacity issues, or temporary communication issues.
Verify details or contact [Support](mailto:support@infobip.com). |
| 33 | false | `EC_MESSAGE_WAITING_LIST_FULL` | The message waiting list is full |
| 34 | false | `EC_SYSTEM_FAILURE` | Indicates a system failure |
| 35 | false | `EC_DATA_MISSING` | Indicates that some data is missing |
| 36 | false | `EC_UNEXPECTED_DATA_VALUE` | Indicates that an unexpected data value has been entered |
| 255 | false | `EC_UNKNOWN_ERROR` | Indicates an unknown error |
| 256 | false | `EC_SM_DF_MEMORYCAPACITYEXCEEDED`| Indicates that the message inbox on the recipient's mobile phone is full, preventing new messages.
Delete messages to clear space. |
| 257 | false | `EC_SM_DF_EQUIPMENTPROTOCOLERROR`| There has been a mobile subscriber equipment error |
| 258 | false | `EC_SM_DF_EQUIPMENTNOTSM_EQUIPPED`| There has been a mobile subscriber equipment error |
| 259 | false | `EC_SM_DF_UNKNOWNSERVICECENTRE` | There has been a mobile subscriber equipment error |
| 260 | false | `EC_SM_DF_SC_CONGESTION` | There has been a mobile subscriber equipment error |
| 261 | false | `EC_SM_DF_INVALIDSME_ADDRESS` | There has been a mobile subscriber equipment error |
| 262 | false | `EC_SM_DF_SUBSCRIBERNOTSC_SUBSCRIBER` | There has been a mobile subscriber equipment error |
| 500 | false | `EC_PROVIDER_GENERAL_ERROR` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 502 | false | `EC_NO_RESPONSE` | The message was processed and forwarded to the operator, but no response was returned.
The error may also apply to SS7 network level issues. |
| 503 | false | `EC_SERVICE_COMPLETION_FAILURE` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 504 | false | `EC_UNEXPECTED_RESPONSE_FROM_PEER` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 507 | false | `EC_MISTYPED_PARAMETER` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 508 | false | `EC_NOT_SUPPORTED_SERVICE` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 509 | false | `EC_DUPLICATED_INVOKE_ID` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 565 | true | `EC_CANNOT_RECEIVE_SC` | End users connected to this MVNO cannot receive short code messages. The mobile operator rejected the message as the end user is connected to their network through an MVNO.
This restriction applies to short code messages. |
| 573 | true | `EC_SC_BLOCKED_BY_END_USER` | The end user has asked their mobile operator to block messages sent from your short code. Additional messages must not be sent unless the end user opts in again. |
| 581 | false | `EC_USER_OUT_OF_CREDIT` | The end user is out of prepaid credit and cannot receive the message.
Retry sending every 24 hours for up to seven days. |
| 628 | true | `EC_TEMPORARY_HANDSET_FAILURE` | There is a temporary handset failure |
| 629 | true | `EC_DEST_ADDRESS_UNABLE_TO_RECEIVE_SMS` | The destination address is unable to receive SMS |
| 1024 | false | `EC_OR_APPCONTEXTNOTSUPPORTED` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1025 | false | `EC_OR_INVALIDDESTINATIONREFERENCE` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1026 | false | `EC_OR_INVALIDORIGINATINGREFERENCE` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1027 | false | `EC_OR_ENCAPSULATEDAC_NOTSUPPORTED` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1028 | false | `EC_OR_TRANSPORTPROTECTIONNOTADEQUATE` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1029 | false | `EC_OR_NOREASONGIVEN` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1030 | false | `EC_OR_POTENTIALVERSIONINCOMPATIBILITY` | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1031 | false | `EC_OR_REMOTENODENOTREACHABLE` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1152 | false | `EC_NNR_NOTRANSLATIONFORANADDRESSOFSUCHNATURE` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1153 | false | `EC_NNR_NOTRANSLATIONFORTHISSPECIFICADDRESS` | No translation for this specific address |
| 1154 | false | `EC_NNR_SUBSYSTEMCONGESTION` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1155 | false | `EC_NNR_SUBSYSTEMFAILURE` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1156 | false | `EC_NNR_UNEQUIPPEDUSER` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1157 | false | `EC_NNR_MTPFAILURE` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1158 | false | `EC_NNR_NETWORKCONGESTION` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1159 | false | `EC_NNR_UNQUALIFIED` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1160 | false | `EC_NNR_ERRORINMESSAGETRANSPORTXUDT` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1161 | false | `EC_NNR_ERRORINLOCALPROCESSINGXUDT` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1162 | false | `EC_NNR_DESTINATIONCANNOTPERFORMREASSEMBLYXUDT` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1163 | false | `EC_NNR_SCCPFAILURE` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1164 | false | `EC_NNR_HOPCOUNTERVIOLATION` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1165 | false | `EC_NNR_SEGMENTATIONNOTSUPPORTED` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1166 | false | `EC_NNR_SEGMENTATIONFAILURE` | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1281 | false | `EC_UA_USERSPECIFICREASON` | Message was aborted by a network peer due to a network protocol error. |
| 1282 | false | `EC_UA_USERRESOURCELIMITATION` | Message was aborted by a network peer due to a network protocol error. |
| 1283 | false | `EC_UA_RESOURCEUNAVAILABLE` | Message was aborted by a network peer due to a network protocol error. |
| 1284 | false | `EC_UA_APPLICATIONPROCEDURECANCELLATION` | Message was aborted by a network peer due to a network protocol error. |
| 1536 | false | `EC_PA_PROVIDERMALFUNCTION` | Message was aborted due to other network protocol errors. |
| 1537 | false | `EC_PA_SUPPORTINGDIALOGORTRANSACTIONREALEASED` | Message was aborted due to other network protocol errors. |
| 1538 | false | `EC_PA_RESSOURCELIMITATION` | Message was aborted due to other network protocol errors. |
| 1539 | false | `EC_PA_MAINTENANCEACTIVITY` | Message was aborted due to other network protocol errors. |
| 1540 | false | `EC_PA_VERSIONINCOMPATIBILITY` | Message was aborted due to other network protocol errors. |
| 1541 | false | `EC_PA_ABNORMALMAPDIALOG` | Message was aborted due to other network protocol errors. |
| 1792 | false | `EC_NC_ABNORMALEVENTDETECTEDBYPEER` | Message was aborted due to other network protocol errors. |
| 1793 | false | `EC_NC_RESPONSEREJECTEDBYPEER` | Message was aborted due to other network protocol errors. |
| 1794 | false | `EC_NC_ABNORMALEVENTRECEIVEDFROMPEER` | Message was aborted due to other network protocol errors. |
| 1795 | false | `EC_NC_MESSAGECANNOTBEDELIVEREDTOPEER` | Message was aborted due to other network protocol errors. |
| 1796 | false | `EC_NC_PROVIDEROUTOFINVOKE` | Message was aborted due to other network protocol errors. |
### User errors [#user-errors-general-error-codes]
**Group ID: 2**
User error occurred
| ID | Permanent | Error | Description |
|:-----:|:---------:|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 323 | true | `EC_INVALID_REQUEST_TYPE` | The request type was invalid. |
| 351 | false | `EC_INVALID_DESTINATION_ADDRESS` | Invalid destination address.
Possible reasons for receiving this error for the following mobile operators might be:
**Any operator**:
• The mobile number is not on the mobile operator's network.
• The mobile number has been deactivated.
**T-Mobile and MetroPCS**:
• The phone number belongs to a prepaid user who does not have enough credit to receive a message.
**T-Mobile**:
• The end user is not provisioned to receive a message from all short codes (or from specific short codes)
• The end user is on an MVNO connected through T-Mobile.
• T-Mobile does not deliver messages from short codes to end users on MVNOs.
**AT&T (US)**:
• The phone number belongs to a prepaid user who does not have enough credit to receive a message.
• The phone number is not provisioned for any messages.
• The phone number could be blocked due to a spam complaint. |
| 352 | true | `EC_INVALID_REQUEST_DESTINATION` | Invalid request - destination address country code is not recognized. |
| 355 | true | `EC_MSG_TEXT_TOO_LONG` | Message text is too long. |
| 368 | true | `EC_INVALID_SOURCE_ADDRESS` | Invalid source address value.
The mobile operator rejected the message with an invalid MT source address error. Contact your account manager or reach out to [Support](mailto:support@infobip.com) to determine if the MT source address should be supported by the end user's mobile operator. |
| 433 | true | `EC_ACCOUNT_ACCESS_DENIED` | Account access has been denied. |
| 541 | false | `EC_LIMIT_REACHED` | Carrier sending limit has been reached.
The message was blocked by AT&T because the TPS (transactions per second) limit on your messaging campaign has been exceeded. |
| 542 | false | `EC_QUOTA_REACHED` | Carrier daily quota reached.
The message was blocked by T-Mobile because the daily volume limit for your brand has been exceeded. You cannot resend the message until the next day. |
| 572 | true | `EC_CAMPAIGNID_NOT_PROVISIONED` | Program ID or campaign ID is not provisioned for this mobile operator or is not active. |
| 577 | true | `EC_ACC_NOT_PROVISIONED_TO_SMS_DEMO_SC` | The account is not provisioned to use the SMS demo short code. |
| 578 | true | `EC_EXCEEDED_THE_TIME_LIMIT_OF_SMS_DEMO` | Exceeded the time limit for using SMS demo. |
| 579 | true | `EC_DEST_ADDRESS_NOT_IN_SMS_DEMO` | The destination address is not in the safelist for SMS demo. |
| 580 | true | `EC_EXCEEDED_THE_MAX_NUMBER` | Exceeded the maximum number of demo requests. |
| 594 | true | `EC_INVALID_GLOBAL_CAMPAIGN_ID` | Invalid global campaign ID. |
| 597 | true | `EC_ACC_HAS_NO_ADRESS_FOR_DESR` | Account is not provisioned with an address that can reach the destination. |
| 598 | true | `EC_INTERACTION_NOT_SUPPORTED` | Interaction is not supported for the message destination. |
| 601 | true | `EC_ACC_NOT_2_WAY` | Account is not provisioned for global two-way SMS. |
| 603 | true | `EC_CONTENT_BLOCKED` | Content blocked by user opt-out (MO: STOP).
This code can be returned in a delivery receipt for an MT originating from a North American, SMS-enabled toll-free number or an SMS-enabled landline number. Messaging can resume to the end user if the end user opts back into your program. |
| 604 | true | `EC_BLOCKED_BY_CAMPAIGN_BLACKLIST` | Content blocked by campaign blocklist. |
| 607 | true | `EC_REJECTED_SPAM_BY_OPERATOR` | This message was identified as spam and cannot be delivered. |
| 608 | false | `EC_SIGNALS_BLOCKED` | The message has been rejected due to an anti-fraud mechanism.
It means that the risk score of the destination hit the defined threshold and the system blocked the message. In case of a false positive, you can use Signals API to add it to the trusted list. |
| 609 | true | `EC_SIGNALS_HARD_LIMIT_REACHED` | The daily system-defined limit for sent messages (UTC-based) has been reached. |
| 2049 | true | `EC_IMSI_BLACKLISTED` | IMSI is blocklisted. |
| 2052 | true | `EC_BLACKLISTED_DESTINATIONADDRESS` | The destination number has been blocklisted either at the operator`s request or on your account through the web interface.
Go to the [web interface](https://portal.infobip.com/login) to remove the blocklist on your account or contact [Support](mailto:support@infobip.com) for more information. |
| 2053 | true | `EC_BLACKLISTED_SENDERADDRESS` | The sender number has been blocklisted either at the operator's request or on your account the web interface.
Go to the web interface to remove the blocklist on your account or contact [Support](mailto:support@infobip.com) for more information. |
| 3041 | true | `EC_DEACTIVATED_LIST` | The phone number you provided is listed as deactivated, which means it is no longer active and cannot receive messages.
If you included the `mobileOperatorId` in your request, you can perform an operator lookup to check if the number was ported to a new operator. If you did not include the `mobileOperatorId`, we have already performed the lookup and confirmed that the number is permanently deactivated. It is crucial to refrain from sending any further messages to this number.
For more details, see the guidelines on handling deactivated phone numbers. |
| 4096 | true | `EC_INVALID_PDU_FORMAT` | Invalid PDU format. |
| 4099 | true | `EC_MONTHLY_LIMIT_REACHED` | Your account monthly credit limit has been reached.
For further financial assistance, contact your account manager or contact Support. |
| 4100 | true | `EC_MESSAGE_CANCELED` | The request was received, but has not been sent to the next instance within its validity period and has expired with the appropriate error code, or the same error code was reverted from the operator. |
| 4101 | true | `EC_VALIDITY_EXPIRED` | The message was sent to the next instance and has not been delivered within the message validity period, thus it has expired with the appropriate error code, or the error code was reverted from the operator. |
| 4102 | true | `EC_NOTSUBMITTEDTOSMPPCHANNEL` | Inbound SM cannot be transferred through SMPP due to the lack of SMPP connectivity. |
| 4103 | true | `EC_DESTINATION_FLOODING` | As per the flooding filter rule, you can send 6 messages with the same content to the same destination in one hour while or you can send up to 20 messages with different content to the same destination in a period of one hour.
If there is a valid reason for the traffic to bypass the filter, your account manager can assist you with adjusting these limitations, or reach out to [Support](mailto:support@infobip.com). |
| 4104 | true | `EC_DESTINATION_TXT_FLOODING` | Related to the `REJECTED_FLOODING_FILTER` status.
The message is rejected due to the number of identical messages sent to a single number. |
| 4202 | true | `EC_10DLC_LIMIT_REACHED` | Message was not delivered due to 10DLC operator limit. |
## Voice error codes (DEPRECATED)
Old voice error codes are deprecated from **October 9th, 2024**
See the [Voice and WebRTC error codes](#voice-and-webrtc-error-codes) table for the most up-to-date error code descriptions
### OK [#ok-voice-error-codes]
**Group ID: 0 - Voice error codes**
The request has been completed successfully
| ID | Permanent | Error | Description |
|:-----:|---------|--------------------------|------------------------------------------------------------------------------------------------------------------------|
| 5000 | true | `VOICE_ANSWERED` | The voice call was successfully answered by the recipient.
No further action is required. |
| 5001 | true | `VOICE_ANSWERED_MACHINE` | The voice call was answered by a machine or voicemail system.
You may consider adjusting your communication strategy for machine-answered calls. |
### Handset errors [#handset-errors-voice-error-codes]
**Group ID: 1 - Voice error codes**
The request has not been completed due to handset-related issues
| ID | Permanent | Error | Description |
|:-----:|---------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
| 5480 | false | `EC_VOICE_ERROR_TEMPORARILY_NOT_AVAILABLE` | Temporary unavailability of the voice service or recipient currently unavailable.
Retry the operation later or contact [Support](mailto:support@infobip.com) for assistance. |
| 5603 | false | `EC_DECLINE` | The call was declined by the recipient or the end user rejected the call or is currently unavailable for the call.
Consider alternative methods of communication or try reaching out again later. |
### Operator errors [#operator-errors-voice-error-codes]
**Group ID: 3 - Voice error codes**
The request has not been completed due to operator issues
| ID | Permanent | Error | Description |
|:-----:|---------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 5002 | true | `EC_VOICE_USER_BUSY` | The recipient's phone line is busy.
You can try calling again at a later time or explore other communication channels. |
| 5003 | true | `EC_VOICE_NO_ANSWER` | The recipient did not answer the call.
You may try calling again later or choose an alternative communication method. |
| 5004 | true | `EC_VOICE_ERROR_DOWNLOADING_FILE` | An error occurred while downloading the audio file for playback.
Verify the file's accessibility and format. If the issue persists, contact [Support](mailto:support@infobip.com) for further assistance. |
| 5005 | true | `EC_VOICE_ERROR_UNSUPPORTED_AUDIO_FORMAT` | The audio format is not supported.
Check the audio format requirements, use supported types, and ensure compatibility with the voice service. |
| 5400 | false | `EC_VOICE_ERROR_BAD_REQUEST` | The voice call request was malformed or contained invalid parameters.
Review the request or ensure it is properly formatted and check the API documentation for the correct request structure. |
| 5403 | false | `EC_VOICE_ERROR_FORBIDDEN` | The voice call request was rejected by the operator.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 5404 | false | `EC_VOICE_ERROR_DESTINATION_NOT_FOUND` | The destination for the voice call was not found or is invalid.
Double-check the recipient's phone number or destination details. |
| 5407 | false | `EC_VOICE_ERROR_PROXY_AUTHENTICATION_REQUIRED` | Proxy authentication is required to establish the voice call.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 5408 | false | `EC_VOICE_ERROR_REQUEST_TIMEOUT` | The voice call request timed out before a response was received or the end user could not be found in time during the call.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 5410 | false | `EC_VOICE_ERROR_GONE` | The requested voice call resource is no longer available.
Ensure the recipient's phone number is valid and accessible or contact [Support](mailto:support@infobip.com) for further assistance. |
| 5413 | false | `EC_VOICE_ERROR_REQUEST_ENTITY_TOO_LARGE` | The voice call request entity (for example, audio file) is too large.
Reduce the size of the request entity and try again. |
| 5414 | false | `EC_VOICE_ERROR_REQUEST_URI_TOO_LONG` | The server is refusing to process the request because the Request-URI is longer than the server is willing to interpret (destination too long). |
| 5415 | false | `EC_VOICE_UNSUPPORTED_MEDIA_TYPE` | The media type used in the voice call is not supported.
Ensure you are using a compatible media type for the voice call. |
| 5481 | false | `EC_VOICE_ERROR_CALL_DOES_NOT_EXIST` | The voice call record/transaction does not exist.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 5484 | false | `EC_VOICE_ERROR_ADDRESS_INCOMPLETE` | The address (for example, destination number) provided for the voice call is incomplete or invalid.
Make sure the address is correctly formatted. |
| 5487 | false | `EC_VOICE_ERROR_REQUEST_TERMINATED` | The voice call request was terminated with a cancel button or the end user refused to receive a voice call. |
| 5488 | false | `EC_VOICE_ERROR_NOT_ACCEPTABLE_HERE` | The voice call request is not acceptable on the operator’s end.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 5491 | false | `EC_VOICE_ERROR_REQUEST_PENDING` | The voice call request is pending and waiting for further processing.
Wait for the request to be processed or check the status later. |
| 5501 | true | `EC_NOT_IMPLEMENTED` | The requested voice call feature is not implemented or supported.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 5503 | true | `EC_SERVICE_UNAVAILABLE` | The voice call service is temporarily unavailable.
Retry the request later or contact [Support](mailto:support@infobip.com) for further information. |
## Voice and WebRTC error codes
### OK [#ok-voice-and-webrtc-error-codes]
**Group ID: 0**
The request has been completed successfully
| ID | Permanent | Error | Description |
|:------:|---------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 10000 | true | `NORMAL_HANGUP` | The call ended due to a hangup initiated by the caller, callee, or API. |
| 10001 | true | `ANSWERED_ELSEWHERE` | The call was answered on another device or platform.
Verify the call status on the intended device or investigate further if needed. |
| 10002 | true | `MACHINE_DETECTED` | The voice call was answered by a machine or voicemail system.
You may consider adjusting your communication strategy for machine-answered calls. |
| 10003 | true | `HUMAN_DETECTED` | A human answered the call.
You can take appropriate action based on the call's purpose. |
| 10004 | true | `MAX_DURATION_REACHED` | The call reached the maximum allowed duration.
If needed, initiate a new call or adjust the call duration settings and contact [Support](mailto:support@infobip.com) for further assistance. |
### Handset errors [#handset-errors-voice-and-webrtc-error-codes]
**Group ID: 1**
The request has not been completed due to handset-related issues
| ID | Permanent | Error | Description |
|:------:|---------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------|
| 10100 | true | `DEVICE_FORBIDDEN` | The device (camera and/or microphone) used for the call is not allowed or blocked.
Check device permissions or restrictions and take appropriate action. |
| 10101 | true | `DEVICE_NOT_FOUND` | The device (camera and/or microphone) for the call could not be found or is unavailable.
Ensure the device is accessible and try again. |
| 10102 | true | `DEVICE_UNAVAILABLE`| The device (camera and/or microphone) for the call is currently unavailable. |
| 10103 | true | `MEDIA_ERROR` | An error occurred with the media during the call (for example, an audio issue).
Check the media settings and equipment, and troubleshoot as necessary. |
### User errors [#user-errors-voice-and-webrtc-error-codes]
**Group ID: 2**
User error occurred
| ID | Permanent | Error | Description |
|:------:|---------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 10200 | true | `NO_ANSWER` | The call was successfully delivered to the end user device; however, it was not answered by the end user. |
| 10201 | true | `BUSY` | The call has been successfully delivered to the end user's device, but the end user's device indicates that they are currently busy and unable to answer the incoming call. |
| 10202 | true | `CANCELLED` | The call was canceled at the origination end before it could be successfully routed to the end user. |
| 10203 | true | `REJECTED` | The call was rejected/declined by the end user at the receiving end. |
| 10204 | true | `TEMPORARILY_UNAVAILABLE` | The end user was unavailable to receive the call at the moment.
The operator attempted to connect the call but encountered an issue with the end user's connection or availability, resulting in the call not being successfully connected. It is advisable to verify if the phone number provided is valid and reachable to ensure effective communication in the future. |
### Operator errors [#operator-errors-voice-and-webrtc-error-codes]
**Group ID: 3**
The request has not been completed due to operator issues
| ID | Permanent | Error | Description |
|:------:|---------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 10300 | true | `FORBIDDEN` | The received request was rejected.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 10301 | true | `INSUFFICIENT_FUNDS` | The account you are using does not have sufficient credits or funds available to initiate the phone call you are attempting to make.
In order to proceed with the call, you will need to ensure that there are enough credits or funds in your account. |
| 10302 | true | `UNAUTHENTICATED` | The caller's credentials or access rights are invalid or insufficient to initiate the call.
To resolve this, ensure that the caller provides valid authentication credentials or obtains proper authorization for making the call. |
| 10303 | true | `DESTINATION_NOT_FOUND` | The server was unable to locate the destination number you dialed.
This could be due to an incorrect country prefix or an invalid number format. To resolve this issue, double-check the country prefix and ensure that the number you dialed is accurate and in the correct format. |
| 10304 | true | `DESTINATION_UNAVAILABLE` | The destination number you attempted to call is currently unavailable to receive incoming calls.
To address this situation, it is recommended to verify if the number you dialed is valid and reachable. |
| 10305 | true | `INVALID_DESTINATION` | The server was unable to locate the destination number you dialed.
This could be due to an incorrect country prefix or an invalid number format. To resolve this issue, double-check the country prefix and ensure that the number you dialed is accurate and in the correct format. |
| 10306 | true | `INVALID_REQUEST` | The call request is invalid or malformed.
Review the request parameters and structure, and make necessary adjustments. |
| 10307 | true | `REQUEST_TIMEOUT` | The call request timed out without a response.
For more specific details and assistance, contact [Support](mailto:support@infobip.com). |
| 10308 | true | `NETWORK_ERROR` | An error occurred in the network during the call.
Check the network connection and contact [Support](mailto:support@infobip.com) for further investigation. |
| 10309 | true | `SERVICE_UNAVAILABLE` | The call service is temporarily unavailable.
Contact [Support](mailto:support@infobip.com) for assistance. |
| 10310 | true | `UNKNOWN` | An unknown error occurred during the call.
Contact [Support](mailto:support@infobip.com) for further investigation and assistance. |
| 10311 | true | `FEATURE_UNAVAILABLE` | The requested call feature is not available or supported.
Consider alternative features or methods for communication or contact [Support](mailto:support@infobip.com) for assistance. |
| 10312 | true | `CONGESTION` | The call could not be completed due to network congestion or overload.
Contact [Support](mailto:support@infobip.com) for further investigation and assistance. |
| 10313 | true | `UNAUTHORIZED` | The destination number you attempted to call has not authorized incoming calls. To resolve this situation, obtain authorization from the callee or their service provider. |
| 10400 | true | `URL_NOT_FOUND` | The requested URL for the call was not found.
Verify the URL and make necessary corrections. |
| 10401 | true | `URL_UNREACHABLE` | The requested URL for the call is unreachable.
Check the network connectivity and URL accessibility. |
| 10402 | true | `INVALID_RESPONSE` | The response received during the call is invalid or unexpected.
Contact [Support](mailto:support@infobip.com) for assistance. |
## Push notification error codes
### Registration errors [#registration-errors-push-notification-error-codes]
**Group ID: 1 - Push notification error codes**
Messages not sent due to device registration problems (for example, in cases of uninstalled applications)
| ID | Permanent | Error | Description |
|:------:|---------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 8001 | true | `EC_DEVICE_APP_UNINSTALL` | User has uninstalled the application on device or device cloud token expired. |
| 8002 | true | `EC_FCM_MISMATCH_SENDER_ID` | FCM responded with `MismatchSenderId` in response error field.
Sender ID is a unique numerical value created when you create your Firebase project, available in the **Cloud Messaging** tab of the Firebase console's **Settings** panel. The sender ID is used to identify each app server that can send messages to the client app.
Check your application build configuration. |
| 8003 | true | `EC_NO_APPLICATION_FOUND` | Application with provided `ApplicationCode` for sending push messages is not found.
Check your message target parameters. |
| 8004 | true | `EC_NO_REGISTRATION_ID_FOUND` | Registration with provided `PushRegistrationId` does not exist or has expired. |
### Cloud errors [#cloud-errors-push-notification-error-codes]
**Group ID: 3 - Push notification error codes**
Messages not sent due to Clouds communication issues
| ID | Permanent | Error | Description |
|:------:|:---------:|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 8005 | true | `EC_SYS_ERROR_FROM_CLOUD` | Failed to send push notification.
Cloud (FCM or APNS) responded with error while processing the request. |
| 8006 | true | `EC_INVALID_FCM_AUTH_DATA` | Invalid cloud authentication data (Server Key). FCM responded with status **401 (Unauthorized)**.
Check your Application configuration for Android on the web interface. |
| 8007 | true | `EC_INVALID_APNS_CERT` | Invalid certificate for APNS.
Check your Application configuration for iOS on the web interface. |
| 8008 | true | `EC_APPLICATION_CLOUD_TYPE_DISABLED`| Cloud type was disabled by client for the application.
Request is targeted to registration with cloud type that was disabled by the client. Check your Application configuration on the web interface. |
| 8009 | true | `EC_PUSH_INTERNAL_REQUEST_ERROR` | Internal error.
Try again later and, if the problem persists, contact [Support](mailto:support@infobip.com) for further assistance. |
| 8010 | true | `EC_INVALID_PUSH_PAYLOAD` | Invalid push payload data.
Contact [Support](mailto:support@infobip.com) for further assistance. |
| 8011 | true | `EC_PUSH_INTERNAL_GW_ERROR` | Internal error.
Try again later and if the problem persists, contact [Support](mailto:support@infobip.com) for further assistance. |
| 8012 | true | `EC_PUSH_CLOUD_TEMP_UNAVAILABLE` | Push Cloud (FCM or APNS) is temporarily unavailable. Message is pending in retry. |
| 8013 | true | `EC_REGISTRATION_ID_DISABLED` | Push notifications cannot be delivered because the recipient’s device is not able to receive them.
Possible causes from the recipient’s side:
- Manually disabled notifications
- App was uninstalled
Possible causes from your side:
- The installation was disabled for this recipient’s profile in People
- The installation was disabled in the app code
If cause was from your side, you can resolve the issue by enabling the installation again for this recipient’s profile in People or refer to the [SDK documentation for mobile messaging](https://github.com/infobip/mobile-messaging-sdk-ios/wiki/Users-and-installations#enablingdisabling-push-registration). |
## MMS error codes
| ID | Permanent | Name | Description |
|:-----:|:---------:|---------------|----------------|
| 15000 | false | `EC_MMS_GENERAL_ERROR` | Indicates an MMS provider general error occurred. |
| 15002 | true | `EC_SYSTEM_ERROR` | Indicates a system error occurred. |
| 15003 | true | `EC_MSISDN_NOT_REGISTERED` | The MSISDN is not registered by the operator. |
| 15004 | false | `EC_DEFERRED` | The message is deferred. The end user's handset has retrieved the MMS header, but not the full message. |
| 15005 | true | `EC_MMS_FORWARDED` | The end user has forwarded the MMS to another address without retrieving it. |
| 15006 | true | `EC_VALIDITY_EXPIRED` | The mobile operator could not contact the handset before the message expired. |
| 15007 | true | `EC_CONTENT_CANNOT_BE_DOWNLOADED_ON_HANDSET` | The content cannot be downloaded on the handset. |
| 15008 | true | `EC_PROVIDER_DELIVERY_ERROR` | Indicates an MMS provider error occurred during the delivery. |
| 15009 | true | `EC_RECIPIENT_NOT_FOUND` | The mobile operator could not find the recipient on the mobile. |
| 15010 | true | `EC_SOURCE_ADDRESS_NOT_REGISTERED` | The source address not provisioned with the operator. |
| 15011 | true | `EC_RECIPIENT_BLOCKED_BY_OPERATOR` | The recipient blocked by receiving MMS by the operator. |
| 15012 | true | `EC_DRM_NOT_SUPPORTED` | DRM is not supported. |
| 15013 | true | `EC_MMS_CONTENT_BLOCKED_BY_OPERATOR` | MMS content blocked or is unsupported by the operator. |
| 15014 | true | `EC_MMS_INVALID_SUBJECT` | The MMS subject in the request is invalid. |
| 15015 | true | `EC_MMS_SC_BLOCKED_BY_END_USER` | The end user has blocked traffic from this specific SC. |
| 15016 | true | `EC_UNKNOWN_CARRIER` | Unable to determine the mobile operator. |
| 15017 | true | `EC_RECIPIENT_DEACTIVATED` | The recipient is deactivated. |
| 15018 | true | `EC_RECIPIENT_SUSPENDED` | The recipient is suspended from the service. |
| 15019 | true | `EC_HANDSET_DOES_NOT_SUPPORT_MMS` | MMS is not supported on the handset. |
| 15020 | true | `EC_CAMPAIGN_BLOCKED_BY_OPERATOR` | The campaign is blocked by the mobile operator. |
| 15021 | true | `EC_CAMPAIGN_INFO_NOT_PROVISIONED` | Campaign information is not provisioned for this mobile operator. |
| 15022 | true | `EC_URL_ATTACHMENT_TOO_LARGE` | The MMS cannot be retrieved because the URL attachment is too large. |
| 15023 | true | `EC_FAILED_TO_ROUTE_MESSAGE` | The MMS message could not be routed. |
| 15024 | true | `EC_REMOTE_CONTENT_FAILURE` | The remote content could not be retrieved. |
| 15025 | true | `EC_REMOTE_CONTENT_INTERNAL_FAILURE` | An internal error occurred while trying to fetch the remote content. |
| 15026 | true | `EC_TOO_BIG_CONTENT` | The message was rejected because the submitted content exceeds operator limits. |
| 15200 | true | `EC_INVALID_MSG_TYPE` | The MMS message type is invalid. |
| 15201 | true | `EC_MMS_INVALID_DESTINATION_ADDRESS` | The MMS destination address is invalid. |
| 15202 | true | `EC_MMS_INVALID_SOURCE_ADDRESS` | The MMS source address is invalid. |
| 15203 | true | `EC_INVALID_SUBJECT` | The MMS subject parameter is invalid. |
## Email error codes
### Dropped [#dropped-email-error-codes]
**Group ID: 1**
The request has not been completed successfully as there was an issue noticed before the sending attempt causing an error
| ID | Permanent | Name | Description |
|:-----:|---------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 6002 | true | `EC_SPAM_DETECTED` | The content you are trying to send was detected as possible spam by the platform.
Review the [Email deliverability](https://www.infobip.com/docs/email/email-deliverability) section and adjust your content accordingly before retry. |
| 6003 | true | `EC_UNSUBSCRIBED_EMAIL_ADDRESS` | The recipient opted out of receiving updates from this specific address.
If removal is desired, complete the request by going to the [Do not contact](https://www.infobip.com/docs/people/manage-audience#do-not-contact-list) option in the web interface. |
| 6016 | true | `EC_SENDER_DOMAIN_BOUNCE_BLOCKED` | Your domain has been blocked due to a high bounce rate to protect IPs and its reputation.
The domain unblocking procedure is automated and will happen after a 24-hour cooling-off period.
To prevent this from occurring in the future, check the reports and clean up your recipient database from inactive addresses. Review the [Email validation](https://www.infobip.com/docs/email/email-validation) section to help you with the procedure. |
| 6018 | true | `EC_REQUEST_INVALID` | The submitted request is not valid.
Ensure that the data and request parameters are accurate and in the right format. |
| 6020 | true | `EC_EMAIL_TEMPLATE_NOT_FOUND` | The email template from the request could not be found.
Make sure that the template ID is correct before retry. |
| 6021 | true | `EC_EMAIL_PLACEHOLDERS_ERROR` | Error with placeholders in the content.
Check the placeholders to confirm there are no issues or typos in them and retry. |
| 6023 | true | `EC_BLOCKED_SUSPICIOUS_ACTIVITY` | Your domain has been blocked due to suspicious activity.
Should you require any additional information regarding this matter, contact [Support](mailto:support@infobip.com) or your account manager. |
| 6024 | true | `EC_EMAIL_TOO_MANY_URLS` | Maximum amount of URLs with Tracking enabled is 150.
Lower the amount of URLs or turn off the Tracking features before retry. |
| 6025 | true | `EC_EMAIL_INVALID_TRACKING_PARAMS` | Tracking parameters in the email are not valid. Review them and then retry. |
| 6026 | true | `EC_EMAIL_LANDING_PAGE_PLACEHOLDERS_SIZE_EXCEEDED` | Size of the placeholders on the landing page limit is 256 characters.
Adjust (decrease) the landing page placeholder size accordingly and retry. |
| 6027 | true | `EC_EMAIL_INVALID_HEADERS` | The headers of the email are invalid or improperly formatted.
Check the headers and ensure they meet the required format. |
| 6029 | true | `EC_SENDER_ADDRESS_INVALID` | The email sender is invalid or unauthorized to send emails.
To resolve the issue, check the sender domain for spelling mistakes and ensure that the domain is verified and properly configured. |
| 6030 | true | `EC_EMAIL_INVALID_LANDING_PAGE` | The specified landing page is invalid or inaccessible.
Confirm the landing page's URL and availability and retry. |
| 6031 | true | `EC_INVALID_PRESERVED_CC_OR_BCC_RECIPIENT` | Invalid preserved recipient in CC or BCC.
Check the recipient list and ensure that all preserved recipients are valid and the limit is not reached. |
| 6033 | true | `EC_INVALID_CC_BCC_EMAIL_ADDRESS` | The request contains invalid addresses in the CC and/or BCC.
Ensure that the addresses are correctly formatted by checking them. |
| 6034 | true | `EC_SUPPRESSED_BOUNCE` | A bounce SMTP response from the recipient's mailbox provider earlier has resulted in the recipient address being suppressed. |
| 6035 | true | `EC_SUPPRESSED_SPAM_COMPLAINT` | Due to the recipient reporting previous content sent from the same domain as spam, the recipient's address has been suppressed.
_Note that this error code will be deployed at a later stage. For the time being, spam complaints will be marked with **EC 6034**._ |
| 6036 | true | `EC_SENDER_DOMAIN_UNVERIFIED` | Domain does not currently have all required DNS records set up correctly.
Check your DNS configuration. See [Verify your sender domain](https://www.infobip.com/docs/email/get-started-with-email/set-up-your-domain#verify-your-outbound-domain-outbound-domain-configuration). |
| 6038 | true | `EC_EMAIL_CONTENT_EXPIRED` | The content in a template expired due to the lack of regular usage.
To resolve the issue, check the content and re-upload it. If the issue persists, contact [Support](mailto:support@infobip.com). |
| 6039 | true | `EC_EMAIL_TEMPLATE_LANGUAGE_ERROR` | Error in template language in your content. See [Template language](https://www.infobip.com/docs/email/email-editor/email-personalization#template-language) for more details. If the problem persists, contact [Support](mailto:support@infobip.com). |
| 6040 | true | `EC_EMAIL_TEMPLATE_EXPIRED` | The template validity period expired.
Either update a template to prolong the validity, or copy it and update the template ID before retry. |
| 6041 | true | `EC_EMAIL_TEMPLATE_NOT_SAVED` | The template was not saved.
Make sure the requested template is correctly stored on the web interface before retry. |
| 6050 | false | `EC_SENDER_WARMUP` | The sender domain has reached its reputation warmup limit for today. |
| 6051 | false | `EC_WARMUP` | The sender has reached its reputation warmup limit for today. |
| 6052 | true | `EC_RECIPIENT_DOMAIN_TYPO` | Recipient domain is blocked as it is listed on the Infobip internal blocklist. |
| 6053 | false | `EC_ACCESS_DENIED_BY_MAILBOX_PROVIDER` | The mailbox provider has denied access for the sender. |
| 6054 | true | `EC_SINGLE_SENDER_NOT_VERIFIED` | Single sender not verified. Verify your sender address before retrying the traffic.|
| 6055 | true | `EC_SINGLE_SENDER_TRAFFIC_EXCEEDED` | Your account has reached the limit of 100 emails sent from registered Single Sender address(es). To continue sending emails through Infobip, add your domain to your account. For more information, see [Register a new domain](https://www.infobip.com/docs/email/get-started-with-email/set-up-your-domain#outbound-domain-configuration). |
| 6056 | false | `EC_NO_IP_POOL_ASSIGNED` | The registered sending domain does not have an IP pool assigned. |
| 6057 | false | `EC_SAFETY_RATE_LIMIT` | The sending IP/domain is rate limited by the platform to protect the IP/domain reputation, as rejections were noticed from the specific mailbox provider. This usually relates to the lack of warmup or negative reactions by traffic recipients. To resolve the issue, slow down the traffic towards the specific provider to increase your reputation gradually. For more information, see [IP and domain warmup](https://www.infobip.com/docs/email/ip-and-domain-warmup). |
| 6058 | false | `EC_MAILBOX_PROVIDER_RATE_LIMIT` | The sending IP or domain is limited by the mailbox provider. |
### Bounced [#bounced-email-error-codes]
**Group ID: 2**
The response from the mailbox provider indicates that there was an error and the delivery attempt was unsuccessful
| ID | Permanent | Name | Description |
|:-----:|---------|-------------------------|--------------|
| 6006 | true | `EC_INVALID_EMAIL_ADDRESS` | The recipient's email address provided is either invalid, inactive, or disabled.
Check for possible typos and validate the address before the retry. Review the [Email validation](https://www.infobip.com/docs/email/email-validation) section to help you with the procedure. |
| 6007 | false | `EC_MAILBOX_TEMPORARY_UNAVAILABLE` | The recipient's mailbox is temporarily unavailable.
Retry the email in a few hours and contact [Support](mailto:support@infobip.com) if you continue to encounter the same response for the additional checks. |
| 6009 | true | `EC_MAILBOX_PERMANENTLY_UNAVAILABLE` | The recipient's mailbox provider (domain) might be permanently unavailable.
Contact the recipient and attend to the situation before retry. |
| 6010 | false | `EC_RECIPIENT_INBOX_FULL` | The recipient's mailbox storage limit has been reached and they cannot receive additional emails.
Contact the recipient and resolve this situation by clearing some data. |
| 6011 | false | `EC_SOFT_BOUNCE` | Response indicates a temporary delivery error.
Retry sending and if the same response is returned, contact the recipient to attend to the situation. |
| 6012 | true | `EC_HARD_BOUNCE` | Response is indicating a permanent error related to the delivery.
Contact the recipient to confirm and solve the situation. |
| 6017 | false | `EC_SENDER_IP_BLACKLISTED` | The IP address assigned to your domain has been blocklisted.
See [Email deliverability](https://www.infobip.com/docs/email/email-deliverability) and request the de-listing on the relevant blocklist. |
| 6037 | true | `EC_RECIPIENT_DOMAIN_MX_NOT_FOUND` | The domain to which this address belongs is possibly unavailable or does not exist due to the MX not being found or being unavailable.
Check the address for any typos and validate the address. |
| 6042 | true | `EC_SPAM_REVERTED` | The content in the email was flagged as spam by the mailbox provider.
See [Email deliverability](https://www.infobip.com/docs/email/email-deliverability) and adjust your content accordingly before retry. |
| 6043 | true | `EC_SUSPICIOUS_CONTENT` | Mailbox provider decided to deny your traffic due to the suspicious content.
Ensure that you are following content best practices before retrying the traffic. If the error persists, contact the mailbox provider. |
| 6044 | true | `EC_SUSPICIOUS_SENDER` | Recipient mailbox provider denied your messages due to very low reputation of your domain or IPs.
This usually happens due to different sending best practices not being followed. Ensure that you respect general and mailbox provider's best practices when sending traffic. If the error repeats, contact the mailbox provider to resolve the situation. |
| 6045 | true | `EC_RECIPIENT_DOMAIN_POLICY_ERROR` | Mailbox provider blocked your message as it does not meet their email policy requirements for your organization or for the recipient's organization.
Follow the best practices and if the error repeats, contact the recipient for additional details and possible solution. |
| 6046 | false | `EC_UNSOLICITED_RECIPIENT` | The recipient mailbox provider (domain) has detected that this message is likely to be an unsolicited email; therefore, it was blocked.
Ensure that your recipients are subscribed and interested in the traffic before retry. |
| 6047 | true | `EC_DOMAIN_CONFIGURATION_ERROR` | Your domain might be missing valid DKIM or SPF, so your traffic has been denied by the recipient mailbox provider.
Ensure that your DNS records are valid before retry. |
| 6048 | true | `EC_DMARC_POLICY_ISSUE` | Recipient mailbox provider denied your domain's DMARC policy.
Ensure that the policy is valid before retry and if the error repeats, contact the recipient mailbox provider for further instructions. |
| 6049 | true | `EC_SENDER_DOMAIN_BLACKLISTED` | Your domain has been blocklisted by the recipient mailbox.
See [Email deliverability](https://www.infobip.com/docs/email/email-deliverability) and request the de-listing on the relevant blocklist. |
### System errors [#system-errors-email-error-codes]
**Group ID: 3**
The request has not been successful due to the issue on the Infobip end
| ID | Permanent | Name | Description |
|:-----:|---------|----------------------------|--------------------------------|
| 6013 | false | `EC_INTERNAL_SYSTEM_ERROR` | Something went wrong on the Infobip end.
Retry the traffic and contact [Support](mailto:support@infobip.com) if the same error is returned. |
## Chat error codes
(RCS, WhatsApp, Messenger, LINE, Viber, Zalo, KakaoTalk)
### Client errors [#client-error-chat-error-codes]
**Group ID: 1 - Chat error codes**
The request has not been completed successfully due to application misconfiguration or a bad/invalid request issued by the client
| ID | Permanent | Error | Description |
|:-----:|:---------:|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 7001 | true | `EC_UNKNOWN_APPLICATION` | Indicates that the requested application is unknown or not recognized.
Resolution steps involve verifying the application details, ensuring proper configuration, and contacting the appropriate support channels for assistance. |
| 7002 | true | `EC_UNKNOWN_USER` | Signifies that the user is unknown or not registered.
In the context of RCS, this means the user cannot be reached through RCS because:
• Their device does not support RCS or RCS is disabled.
• Their mobile network does not support RCS for the agent (either the agent is not launched there or RCS traffic is not enabled).
• An unlaunched agent is requesting capabilities for a user who is not a registered tester.
To resolve this error, verify the user's details or ensure that the MSISDN is correct and belongs to an active user.
If the user’s device or network does not support RCS, use the fallback communication channels. Verify the Agent is launced with the Provider/Carrier to which the MSISDN belongs to. |
| 7003 | true | `EC_BLOCKED_USER` | Indicates that the user has been blocked or restricted from accessing the messages.
In RCS, this occurs when the user has opted out of further communication from the agent.
Resolution steps involve investigating the reason for the user block, reviewing any violation or restriction policies, and taking appropriate actions such as unblocking or contacting [Support](mailto:support@infobip.com) for further assistance. |
| 7004 | true | `EC_UNAUTHORIZED_ACCESS` | Denotes unauthorized access or unrecognized service access credentials.
To resolve this error, investigate the unauthorized access attempt, ensure proper authentication/credentials, and contact [Support](mailto:support@infobip.com) for further assistance. |
| 7005 | true | `EC_FORBIDDEN_ACCESS` | Indicates that access to the requested resource or service is forbidden.
In RCS, this may occur when:
• An unlaunched agent attempts to send a message, event, or capability callback to a non-tester.
• The carrier does not support RCS or the carrier itself is not supported.
Resolution steps involve verifying the user's access rights and permissions, ensuring the application is allowed to send messages, and verifying that it is published or approved by the provider. |
| 7006 | true | `EC_BAD_REQUEST` | The server cannot process the request due to invalid syntax or parameters.
In RCS, this typically occurs when:
• The message contains unsupported content.
• The message includes features or settings that the recipient’s device does not support.
Verify the request data and ensure that it follows the required format or check the API documentation for the correct request structure or contact [Support](mailto:support@infobip.com) for additional guidance. |
| 7007 | true | `EC_ILLEGAL_TRAFFIC_TYPE` | Indicates that the content of the submitted message does not align with the registered traffic type of the sender.
This could be due to the use of incompatible media elements or not understanding any restrictions or guidelines related to traffic types. For more specific details and assistance, contact [Support](mailto:support@infobip.com). |
| 7008 | true | `EC_INVALID_TEMPLATE_ARGS` | Denotes invalid or missing parameters in a message template.
To resolve this error, review the template structure, ensure that all required parameters are provided, and correct any invalid or missing parameters. |
| 7009 | true | `EC_INVALID_TEMPLATE` | Signifies an invalid or incorrect message template.
In RCS, it's used on connections that have template management.
Resolution steps involve reviewing the template and making the necessary modifications or corrections. |
| 7010 | true | `EC_NO_SESSION` | Indicates that the session has not been initiated or has expired.
To resolve this error, establish a valid session by authenticating the user or application, ensuring a new session, or extending the existing session. |
| 7011 | true | `EC_ACCOUNT_ISSUE` | Signifies an issue or problem related to the user's account.
Resolution steps involve investigating the account-related problem and contacting [Support](mailto:support@infobip.com) for further assistance. |
| 7012 | false | `EC_DEPLOYMENT_CONFIGURATION_ERROR` | Denotes an error or issue with the deployment or configuration of the system or service.
To resolve this error, contact [Support](mailto:support@infobip.com) for further assistance. |
| 7013 | false | `EC_MEDIA_HOSTING_ERROR` | Indicates an error or problem related to media hosting or storage.
Resolution steps involve verifying the media hosting setup, ensuring proper connectivity, and resolving any hosting-related issues. |
| 7014 | false | `EC_MEDIA_UPLOAD_ERROR` | Signifies an error or problem encountered during media upload.
To resolve this error, check for any network or connectivity issues, and ensure that the media file meets the specified requirements. |
| 7015 | true | `EC_MEDIA_METADATA_ERROR` | Denotes an error or issue with the metadata associated with media files.
Resolution steps involve reviewing the metadata information, ensuring content type and size, and resolving any metadata-related problems. |
| 7016 | true | `EC_SPAM_RATE` | Message failed because there are restrictions related to the sender quality rating on how many messages can be sent from this sender to unique end users during the period defined by the provider. |
| 7017 | false | `EC_TOO_MANY_REQUESTS` | Signifies that the number of requests from the application has exceeded the allowed limit.
In RCS, this occurs when tester request quotas are exceeded, such as sending more than 20 tester requests in a single day or surpassing the total maximum of 200 tester requests.
To resolve this error, reduce the frequency or number of requests, adhere to rate limits, and consider optimizing the request flow if necessary. |
| 7018 | true | `EC_INTERNAL_BAD_MAPPING` | Denotes an internal error related to mapping or data structures within the system.
In RCS, this occurs when a message is rejected due to an invalid request, such as using a disallowed image format or incorrectly applying message parameters.
Resolution steps involve investigating the mapping issue, reviewing and resolving any inconsistencies or errors in the mapping process, and contacting [Support](mailto:support@infobip.com) for further assistance. |
| 7019 | true | `EC_PROVIDER_BILLING_ERROR` | Indicates an error or problem with the billing process or integration with the provider.
To resolve this error, review the billing setup, ensure proper integration and configuration with the provider, and address any billing-related issues or errors. |
| 7020 | true | `EC_DEVICE_REPRODUCTION_ERROR` | Signifies an error or problem related to displaying content on the end user device.
To resolve it, check network connectivity and refresh the content, clear the cache, update the app or software, ensure device compatibility, and verify if the latest Terms of Service has been accepted. If the issue persists, contact [Support](mailto:support@infobip.com) for further assistance. |
| 7021 | true | `EC_LIMITED_FUNCTIONALITY` | Denotes limited functionality or restricted access to certain features or services on the Meta side.
To resolve this error, review the functionality restriction on the Meta side. |
| 7022 | true | `EC_MEDIA_UNSUPPORTED` | Indicates that the media file or format is not supported by Meta.
Resolution steps involve verifying the supported media formats, converting the media file to a supported format if necessary, and ensuring compatibility with Meta's media requirements. |
| 7023 | true | `EC_DATA_MISMATCH` | Signifies a mismatch or inconsistency in the data, either locally or remotely.
To resolve this error, validate its accuracy and consistency, and address any mismatches or inconsistencies. If you need additional assistance, contact [Support](mailto:support@infobip.com). |
| 7024 | false | `EC_NOT_ALLOWED_SENDING_TIME` | Denotes an error where the sending time for the message is not allowed or falls outside the permitted time window.
Resolution steps involve reviewing the sending time restrictions or policies, adjusting the sending time if necessary, and ensuring compliance with the permitted time frames. |
| 7025 | true | `EC_UNSUPPORTED_MOBILE_APP_VERSION` | Indicates that the mobile app version being used is not supported by Meta.
To resolve this error, update the mobile app to a supported version, ensure compatibility with Meta requirements, and address any version-related issues. Contact [Support](mailto:support@infobip.com) for further assistance. |
| 7026 | true | `EC_MESSAGE_TYPE_EXHAUSTED` | Denotes that the message type or category has been exhausted or reached the supplier's API limit.
Resolution steps involve reviewing the message type limitations and managing message usage within the allocated limits. |
| 7027 | true | `EC_BLOCKED_CONTENT` | Signifies that the content of the message is blocked or restricted due to policy violations or content filtering.
To resolve this error, review the message content, ensure compliance with content guidelines, modify the content if necessary, and address any policy violations. |
| 7029 | true | `EC_USER_IDENTITY_CHANGED` | Indicates that the user's identity or authentication details have changed or become invalid. Resolution steps involve verifying the user's identity, updating authentication information if necessary, and ensuring proper user identification and authentication. |
| 7030 | true | `EC_TEMPLATE_BLOCKED_BY_USER` | The receiving user has blocked a specific template. |
| 7031 | true | `EC_INVALID_WA_FLOW` | Indicates an invalid state of the flow or an incorrect mode in the Flow message.
Resolution steps involve verifying the message request and flow. Applies to cases where the flow is in a deprecated, blocked, or throttled state, as well as cases of an invalid flow mode in message requests (for example, using a draft when the flow is published). |
| 7032 | true | `EC_FREQUENCY_CAPPING` | Indicates that the message was rejected because Meta limits how many WhatsApp marketing template messages a person can receive from all businesses within a certain time period. Once a user reaches this per-user limit, additional marketing templates that would start a new conversation may be blocked, starting with messages that are less likely to be read.
For more details, refer to the [Meta documentation](https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/marketing-templates/per-user-limits). |
| 7033 | true | `EC_MARKETING_OPT_OUT` | Indicates that the message was not delivered because the recipient has opted out of receiving WhatsApp marketing messages from this business. This occurs when the end user disables the [Offers and announcements](https://www.infobip.com/docs/whatsapp/compliance/user-opt-ins#manage-user-marketing-preferences) setting in WhatsApp.
To resume receiving marketing messages, the user must manually re-enable this option in WhatsApp. For more information, refer to the [Meta documentation](https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates/marketing-templates#user-preferences-for-marketing-messages). |
| 7034 | true | `EC_SENDER_NOT_REGISTERED` | Sender not registered on the WhatsApp Business Platform. |
| 7035 | false | `EC_CALL_PERMISSION_REQUEST_FAILED` | The maximum number of call permission requests has been reached for this business–consumer pair. |
| 7102 | true | `EC_PHONE_MATCHING_DISABLED` | Indicates a data mismatch or inconsistency, either locally or remotely.
To resolve the issue, verify the accuracy and consistency of the data, and address any discrepancies or inconsistencies. Contact [Support](mailto:support@infobip.com) for additional assistance. |
| 7201 | true | `EC_UNSUPPORTED_DEVICE` | Denotes an unsupported or incompatible device attempting to access the service.
To resolve this error, verify the device compatibility requirements, and address any device-related issues or limitations. |
### Provider errors [#provider-errors-chat-error-codes]
**Group ID: 2 - Chat error codes**
The request has not been completed successfully due to a service provider error
| ID | Permanent | Error | Description |
|:----:|---------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 7036| false | `EC_TEMPLATE_NOT_SYNCED` | The newly created template was sent through MM Lite before completing ad synchronization. Please wait up to 10 minutes for ad synchronization to complete, then try again. |
| 7037 | false | `EC_TEMPLATE_NOT_AVAILABLE` | Meta was unable to complete ad synchronization for the template you want to send, or your business may not be eligible for MM Lite. |
| 7038 | true | `EC_INVALID_WA_ACCOUNT_TYPE` | The WhatsApp Business Account (WABA) uses the On-Behalf-Of (OBO) model. OBO WABAs are **not** supported. Use a different WABA or transfer ownership of the WABA to the business customer. |
| 7050 | false | `EC_PROVIDER_INTERNAL_ERROR` | Indicates an internal error or issue within the provider's system or infrastructure that is affecting the processing of messages.
If you encounter this error, it is recommended to wait for some time. If the issue persists, reach out to [Support](mailto:support@infobip.com) for assistance and investigation. |
| 7051 | false | `EC_PROVIDER_TIMEOUT` | Signifies a timeout or connection issue with the provider and the platform.
To resolve this error, contact [Support](mailto:support@infobip.com) for assistance in resolving the issue and investigating the underlying cause. |
| 7052 | true | `EC_PROVIDER_DR_ERROR` | Denotes an error or problem related to the provider's delivery report mechanisms or processes.
Resolution steps involve contacting [Support](mailto:support@infobip.com) for further assistance. |
### System errors [#system-errors-chat-error-codes]
**Group ID: 3 - Chat error codes**
The request has not been completed successfully due to a system-related error
| ID | Permanent | Error | Description |
|:----:|:---------:|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 7080 | true | `EC_INTERNAL_ERROR` | Indicates an internal error or issue within the system or service.
To resolve this error, contact [Support](mailto:support@infobip.com) for further assistance. |
| 7081 | true | `EC_CONFIGURATION_ERROR` | Signifies an error or problem related to the configuration settings of the sender or the sender is not registered for the targeted country on the provider's side.
Resolution steps involve reviewing the configuration settings related to the sender or contacting [Support](mailto:support@infobip.com) for further assistance. |
| 7082 | true | `EC_TEMPORARY_GATEWAY_ERROR` | Denotes a temporary error or issue in processing messages or the communication channel.
To resolve this error, contact [Support](mailto:support@infobip.com) for further assistance. |
| 7083 | true | `EC_SERVICE_NOT_ACTIVATED` | Indicates that the requested service or feature is not activated or enabled for the user or account.
Resolution steps involve checking the service activation status and contacting [Support](mailto:support@infobip.com) for further assistance. |
| 7084 | true | `EC_MISSING_SENDER_METADATA` | Denotes missing or incomplete sender metadata in the request.
To resolve this error, review and make sure that all required sender metadata is provided with accurate and complete sender information and contact [Support](mailto:support@infobip.com) for further assistance. |
| 7280 | true | `EC_DUPLICATE_REQUEST` | Signifies a duplicate or redundant request sent to the user.
Resolution steps involve identifying the duplicate request, removing or deduplicating the redundant requests, and ensuring a single valid request is processed. |
| 7281 | true | `EC_BAD_ORIGIN` | Indicates an invalid or unauthorized origin or source of the request.
To resolve this error, validate the request origin and contact [Support](mailto:support@infobip.com) for further assistance. |
## Mobile Identity error codes
| ID | Value | Response type | Description |
|:-----|:-----------------------------|:-------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------|
| 100 | `EC_NO_COVERAGE` | SYNC | No coverage for requested phone number. |
| 101 | `EC_GATEWAY_OPERATION_FAILED`| SYNC & CALLBACK | Provider service failed. |
| 102 | `EC_OPERATION_RESTRICTED` | SYNC | Operation restricted. |
| 200 | `EC_INVALID_REQUEST` | SYNC | Validation failed for requested arguments. |
| 201 | `EC_INVALID_TOKEN` | SYNC | The token is invalid or does not exist. |
| 202 | `EC_CONSENT_NOT_GRANTED` | SYNC | User consent not granted. |
| 300 | `EC_MI_ACCOUNT_DISABLED` | SYNC | User account is disabled for Mobile Identity service. Contact [Support](mailto:support@infobip.com) to enable it. |
| 301 | `EC_OPERATION_NOT_ALLOWED` | SYNC | Service is not allowed for this account. Contact [Support](mailto:support@infobip.com) to enable it. |
| 302 | `EC_COUNTRY_NOT_ALLOWED` | SYNC | Destination country is not allowed for this account. Contact [Support](mailto:support@infobip.com) to enable it. |
| 303 | `EC_GATEWAY_NOT_ALLOWED` | SYNC | Provider is not allowed for this account. Contact [Support](mailto:support@infobip.com) to enable it. |
| 304 | `EC_REJECTED_NOT_ENOUGH_CREDITS`| SYNC | Not enough credits for this service. |
| 305 | `EC_MOBILE_DEVICE_TIMEOUT` | CALLBACK | Timeout occurred during a mobile device redirect. |
| 306 | `EC_REJECTED_INVALID_IP_ADDRESS`| SYNC & CALLBACK | IP address not in MNO data range. |
| 307 | `EC_OTP_SMS_SEND_FAILED` | CALLBACK | Failed to send an SMS message. |
| 308 | `EC_NI_ATTRIBUTE_NOT_ALLOWED`| CALLBACK | Requested Number Intelligence attribute is not allowed for this account. Contact [Support](mailto:support@infobip.com) to enable it. |
| 309 | `EC_SIM_SWAP_CHECK_FAILED` | CALLBACK | Failed to execute SIM Swap check request due to an error on the MNO side. Contact [Support](mailto:support@infobip.com) for more details. |
| 310 | `EC_SIM_SWAP_DETECTED` | CALLBACK | No coverage for the requested phone number. |
| 400 | `EC_UNPROCESSABLE_CONTENT` | SYNC & CALLBACK | Unable to process provided data. |
| 1000 | `EC_USER_INTERNAL_ERROR` | SYNC & CALLBACK | Internal error on the platform. Contact [Support](mailto:support@infobip.com) to resolve the issue. |
## DLT error codes
Note
Applicable only to the **India** region
| ID | Status | Description |
|:----:|--------|------------|
| 4106 | `EC_BLOCKED_BY_DLT` | This error indicates that a message has been blocked by the DLT Provider due to regulatory compliance issues, sender registration, template registration, and so on. |
| 4107 | `EC_DLT_SCRUBBING_TIMEOUT` | Timeout while performing DLT Scrubbing. |
| 4108 | `EC_SENDER_BLOCKED_BY_DLT` | The error typically indicates that the sender of a message has been blocked by the DLT Provider.
This means that the sender has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider. |
| 4109 | `EC_TELEMARKETER_BLOCKED_BY_DLT` | Telemarketer blocked by DLT Scrubbing. |
| 4110 | `EC_ENTITY_BLOCKED_BY_DLT` | The error typically indicates that the principal entity ID of a message has been blocked by the DLT Provider.
This means that the entity has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider. |
| 4111 | `EC_TEMPLATE_BLOCKED_BY_DLT` | The error typically indicates that the template or content of a message has been blocked by the DLT Provider.
This means that the message template or content has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider. |
| 4112 | `EC_ENTITY_NOT_FOUND` | Indicates that the requested principal entity ID could not be found or located.
This means that the DLT Provider was unable to locate the specific PE ID being referenced. It could be due to various reasons, such as an incorrect identifier, a non-existent entity, or a misconfiguration. |
| 4113 | `EC_ENTITY_NOT_REGISTERED` | No entry of entity on the platform. |
| 4114 | `EC_ENTITY_INACTIVE` | This error code indicates that the principal entity in question is inactive or disabled.
This could be due to various reasons, such as principal entity ID suspension, temporary deactivation, or restrictions. Resolving this error typically includes checking with the DLT Provider. |
| 4115 | `EC_ENTITY_BLACKLISTED` | This error code indicates that the requested principal entity has been blocklisted.
It means that the entity is restricted or prohibited on DLT Provider, due to issues such as violation of policies, non-compliance, or suspicious activity. |
| 4116 | `EC_INVALID_ENTITY_ID` | This error code suggests that the provided Principal entity ID is in an invalid or wrong format or does not exist in the DLT Provider.
It means that the principal entity ID is incorrect or unrecognized. Verifying the accuracy of the entity ID or resolving any issues related to the entity's DLT provider can help resolve this error. |
| 4117 | `EC_ENTITY_ID_NOT_ALLOWED_FOR_TM` | Principal entity is not allowed for the TM. |
| 4118 | `EC_TELEMARKETER_NOT_REGISTERED` | No entry of TMID on the platform. |
| 4119 | `EC_TELEMARKETER_INACTIVE` | Telemarketer is inactive on the platform. |
| 4120 | `EC_TELEMARKETER_BLACKLISTED` | Telemarketer is blocklisted on all platforms. |
| 4121 | `EC_HEADER_NOT_FOUND` | This error code signifies that the requested header/sender ID information was not found.
It means that the DLT Provider could not locate the required header in the given context or request. Review the request structure, and ensure the presence of the necessary headers. |
| 4122 | `EC_HEADER_INACTIVE` | This error code indicates that the requested header is inactive or disabled.
It means that the header, typically used to send messages, is currently inactive. Activating the required header or checking for any configuration or permission-related issues on DLT Provider can help resolve this error. |
| 4123 | `EC_HEADER_BLACKLISTED` | This error code suggests that the requested header has been blocklisted, meaning it is restricted or prohibited from being used.
It could be due to policy violations, non-compliance, or suspicious activity. |
| 4124 | `EC_PEID_NOT_MATCHED_WITH_HEADER` | This error code indicates that the provided PEID (Principal Entity ID) does not match the header/sender ID information.
It means that there is a mismatch between the specified PEID and the associated header in the request. Verifying the accuracy and alignment of the PEID and header on the DLT Provider can help resolve this error. |
| 4125 | `EC_HEADER_IN_FREEPOOL` | Header in free pool. |
| 4126 | `EC_TEMPLATE_NOT_FOUND` | This error code signifies that the requested template could not be found.
It means that the DLT Provider was unable to locate the specified template, which is typically used for standardized message formats or content. Verifying the template's existence, correcting the identifier, or troubleshooting any issues related to template retrieval can help address this error. |
| 4127 | `EC_TEMPLATE_INACTIVE` | This error code suggests that the requested template is inactive or disabled.
It means that the template, which is typically used for predefined message structures, is currently not active on DLT Provider. Activating the required template or addressing any configuration or permission-related issues with DLT Provider can help resolve this error. |
| 4128 | `EC_TEMPLATE_BLACKLISTED` | This error code indicates that the requested template has been blocklisted, meaning it is restricted or prohibited from being used.
It could be due to policy violations, non-compliance, or suspicious activity. |
| 4129 | `EC_TEMPLATE_NOT_MATCHED` | This error code suggests that the requested template does not match the provided content or message.
It means that there is a mismatch between the specified template and the actual content being sent. Ensuring the alignment between the registered template and the actual content being sent can help resolve this error. |
| 4130 | `EC_HEADER_NOT_REGISTERED_FOR_TEMPLATE` | This error code signifies that the specified header is not registered or associated with the requested template.
It means that the header being used does not align with the template requirements or associations. Verifying the registration and link between the header and template can help address this error. |
| 4131 | `EC_TEMPLATE_VARIABLE_EXCEEDED_MAX_LENGTH` | This error code indicates that a variable within the template exceeds the maximum allowed length.
It means that variables used within the template exceed the defined character limit. Adjusting the character length can help resolve this error. |
| 4132 | `EC_ERROR_IDENTIFYING_TEMPLATE` | Error in identifying the template. |
| 4133 | `EC_INVALID_TEMPLATE_ID` | This error code suggests that the provided template ID is invalid or does not exist in the system.
It means that the template ID/content ID used to reference a specific template is incorrect or unrecognized. Verifying the accuracy of the template ID or troubleshooting any issues related to the template's existence can help address this error. |
| 4134 | `EC_TEMPLATE_NOT_REGISTERED_TO_ENTITY` | This error code signifies that the requested template is not registered or associated with the specified principal entity ID.
It means the template being used does not link to the intended principal entity. Verifying the registration and association between the template and principal entity ID can help resolve this error. |
| 4135 | `EC_PROMOTIONAL_TEMPLATE_USED_ON_OTHERS_HEADER` | Promotional template used on other/transaction header. |
| 4136 | `EC_INVALID_TEMPLATE_TYPE` | Invalid template type. |
| 4137 | `EC_PREFERENCE_NOT_MATCHED` | This error code indicates that the requested preference does not match the specified criteria on the end user number.
It means that the preference being used does not align with the end user number. |
| 4138 | `EC_INVALID_PROMO_TIME` | This error code suggests that the provided promotional time is invalid or outside the allowed range (9 PM to 10 AM).
It means that the specified promotional time period does not adhere to the defined constraints or rules. |
| 4139 | `EC_SE_CATEGORY_BLOCK` | This error code indicates that the requested category of service entity (SE) has been blocked.
It means that the particular category or type of service entity is restricted or prohibited from being used. Resolving this error typically includes checking the category of service entity or using a DND consent on a specific number. |
| 4140 | `EC_CONSENT_FAILED` | General error code for consent. |
| 4141 | `EC_SCRUBBING_FAILED` | General error code in case of any exceptions. |
| 4142 | `EC_TLV_PEID_NOT_FOUND` | This error code suggests that the requested Principal Entity ID (PEID) within the TLV structure was not found.
It means that the system or service could not locate the specified PEID within the TLV data. Verifying the correct use and presence of the PEID within the TLV structure in the SMPP request can help resolve this error. |
| 4143 | `EC_TLV_TMPID_NOT_FOUND` | This error code signifies that the requested Template ID within the TLV structure was not found.
It means that the system or service was unable to locate the specified template ID within the TLV data. Verifying the correct usage and presence of the template ID within the TLV structure in the SMPP request can help address this error. |
| 4144 | `EC_CONTENT_MULTIPART_INCOMPLETE_BY_DLT` | Undelivered/expired.
If the DLT has not received long SMS parts or if any part is missing, the DLT shows this code. |
| 4146 | `EC_HEADER_SUSPENDED_DUE_TO_VALIDITY` | This error signifies that the header has been suspended due to validity issues concerning DLT compliance.
To resolve this, review and ensure that the header information complies with DLT regulations. |
| 4147 | `EC_HEADER_SUSPENDED_DUE_TO_USAGE` | This error occurs when the header is suspended due to excessive usage that violates DLT regulations.
Evaluate your SMS sending practices, consider reducing the volume of messages sent, and adhere to DLT guidelines. |
| 4148 | `EC_HEADER_SUSPENDED_DUE_TO_CUSTOMER` | This error suggests that the header has been suspended due to issues related to the customer's DLT account.
Contact your DLT service provider or [Support](mailto:support@infobip.com) to address and resolve customer-specific DLT compliance concerns. |
| 4149 | `EC_TEMPLATE_SUSPENDED_DUE_TO_VALIDITY` | This error indicates that the template has been suspended due to validity problems concerning DLT compliance.
To rectify this, review and correct the template content to ensure it aligns with DLT regulations and standards. |
| 4150 | `EC_TEMPLATE_SUSPENDED_DUE_TO_USAGE` | This error arises when the template is suspended due to excessive usage that violates DLT regulations.
Optimize your SMS templates or reduce the frequency of template usage to comply with DLT guidelines. |
| 4151 | `EC_TEMPLATE_SUSPENDED_DUE_TO_CUSTOMER` | This error implies that the template has been suspended due to issues related to the customer's DLT compliance status.
Contact your DLT service provider or [Support](mailto:support@infobip.com) to address and resolve customer-specific DLT compliance matters. |
| 4153 | `EC_CTA_NOT_WHITELISTED` | This error indicates that the URL in your SMS template has not been safelisted on the DLT platform, a requirement for SMS delivery in accordance with TRAI regulations. |
| 4154 | `EC_PE_TM_HASH_NOT_RECEIVED` | This error indicates that the PE-TM hash was not received or an empty value was provided in the request. |
| 4155 | `EC_PE_TM_HASH_NOT_REGISTERED` | This error indicates that the submitted PE-TM hash does not match any registered hash for the specified PE. |
| 4156 | `EC_PE_TM_HASH_INACTIVE` | This error indicates that the status of the PE-TM hash is invalid because one of the telemarketers in the chain is inactive. |
| 4157 | `EC_PE_TM_HASH_BLACKLISTED` | This error implies that the status of the PE-TM hash is blocklisted. |
| 4158 | `EC_PE_TM_HASH_SUSPENDED` | This error indicates that the status of the PE-TM hash is suspended by the customer. |
## Live Chat error codes
Below are the possible error codes for:
- Web widget
- Enable authenticated customer session with widget API
- Invalidate authenticated customer session
| ID | Status | Description |
|:-----:|----------------------------|---------------------------------------------------------------------------------------------|
| 1001 | `Mandatory field missing` | Param `widgetId` is required in the method. |
| 1011 | `Widget initializing error` | Widget already initialized. |
| 1012 | `Widget initializing error` | Error in the widget configuration. |
| 1013 | `Widget initializing error` | Already authenticated with another widget id. |
| 1031 | `Widget visibility error` | Initializing on pages that are not allowed. |
| 1032 | `Widget visibility error` | Auth customers only. |
| 1033 | `Widget visibility error` | Outside working hours. |
| 1101 | `Mandatory field missing` | `token` parameter is required in the method. |
| 1102 | `Mandatory field missing` | `ski` field is required in JWT. |
| 1103 | `Mandatory field missing` | `sub` field is required in JWT. |
| 1104 | `Mandatory field missing` | `iss` field is required in JWT. |
| 1105 | `Mandatory field missing` | `iat` field is required in JWT. |
| 1106 | `Mandatory field missing` | `jti` field is required in JWT. |
| 1111 | `Field in wrong type` | `iat` should be a `number` type and should be in seconds. |
| 1112 | `Field in wrong type` | `exp` should be a `number` type and should be in seconds. |
| 1113 | `Field in wrong type` | `stp` should be one of [`email`, `msisdn`, `externalPersonId`]. |
| 1114 | `Field in wrong format` | Check `sub` for `stp` type. |
| 1121 | `Method invocation error` | User is already authenticated. |
| 1122 | `Method invocation error` | JWT payload is broken. |
| 1123 | `Method invocation error` | `ski` is wrong, no widget key with this id. |
| 1124 | `Method invocation error` | `alg` is incorrect. |
| 1125 | `Method invocation error` | There is something wrong with the encryption. |
| 1126 | `Method invocation error` | `iss` differs from the initialized widget id. |
| 1127 | `Method invocation error` | `iat` is not valid, should be earlier than now. |
| 1128 | `Method invocation error` | `exp` is not valid, should be later than now. |
| 1198 | `Connection issue` | Failed to authenticate. Try again later. |
| 1199 | `Request error` | Request failed with status `${status}`. |
| 1321 | `Method invocation error` | User is already logged out. |
## Moments error codes
Below are the possible error codes for batch flow processing
### Rejected [#rejected-moments-error-codes]
| ID | Status | Description |
|:-----:|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
| 200 | `REJECTED_INVALID_CONTACT` | A person started to be processed but was rejected as the contact was not recognized. |
| 202 | `REJECTED_VARIABLE_MISSED` | One of the Flow variables specified in the request does not exist or has a spelling error. |
| 203 | `REJECTED_PERSON_ALREADY_IN_FLOW` | Person is already in Flow. |
| 204 | `REJECTED_PERSON_NOT_ALLOWED_TO_REENTER` | Person is currently not allowed to re-enter Flow. |
| 205 | `REJECTED_FLOW_ERROR_UNKNOWN` | A generic Flow error. |
| 206 | `REJECTED_NOT_ENOUGH_CREDITS` | Your account is out of credits.
Top up your account. Contact your account manager for assistance in topping up or applying for an online account top-up service. |
## People API error codes
Below you can find the error codes for People API
```json
{
"requestError": {
"serviceException": {
"messageId": "TOO_MANY_REQUESTS",
"text": "Too many requests"
}
}
}
```
### 400 Bad Request [#400-bad-request-people-api-error-codes]
| ID | Status | Description |
|:------:|--------------------------------|-----------------------------------------------------------------------------------------------------|
| 40001 | `BAD_REQUEST` | Generic request validation error. |
| 40002 | `DUPLICATE` | Profile already exists. |
| 40003 | `DUPLICATE_EXT_PERSON_ID` | Profile with this External ID already exists. |
| 40004 | `DUPLICATE_NUMBER_DESTINATION` | Profile with the phone number already exists. |
| 40005 | `DUPLICATE_EMAIL_DESTINATION` | Profile with the email address already exists. |
| 40006 | `DUPLICATE_NAME` | Object (tag, attribute, company) with this name already exists. |
| 40007 | `INVALID_ADDITIONAL_FIELD_TYPE` | Invalid value type for the custom attribute (for example, when a string value is specified for a numeric attribute). |
| 40010 | `CUSTOM_ATTRIBUTE_OUT_OF_BOUNDS`| Invalid value for the custom attribute. |
| 40012 | `INVALID_UNIQUE_FIELD` | Invalid profile identifier value in the request. |
| 40013 | `NON_MANAGED_DESTINATIONS_EXCEPTION` | You can only modify the email and phone contacts using this API. |
| 40014 | `INVALID_UPDATE_ENTRIES` | Invalid query (wrong field or missing value) in the batch update request. |
| 40015 | `UNKNOWN_PROPERTY` | Unknown profile attribute in the request. |
| 40016 | `INVALID_DELETE_ENTRIES` | Invalid query (wrong field or missing value) in the batch delete request. |
| 40018 | `EMPTY_DESTINATIONS` | Missing contact information for the profile. |
| 40019 | `BAD_QUERY` | Bad filter query in the request. |
| 40020 | `PLACEHOLDER_CANNOT_BE_DELETED` | Custom attribute cannot be deleted. |
| 40021 | `TAG_CANNOT_BE_DELETED` | The tag cannot be deleted. |
| 40022 | `INVALID_PLACEHOLDER` | Invalid custom attribute. |
| 40023 | `INTEGRATIONS_CANNOT_BE_MODIFIED` | Integrations data cannot be modified. |
| 40024 | `WEB_SDK_RESTRICTED_OPERATION` | You cannot create or change Customer profiles from Web SDK. |
### 404 Not Found [#404-not-found-people-api-error-codes]
| ID | Status | Description |
|:------:|:---------------------------------------|:-----------------------------------------------|
| 40401 | `PERSON_DOES_NOT_EXIST` | The person does not exist. |
| 40403 | `TAG_DOES_NOT_EXIST` | The tag does not exist. |
| 40404 | `ADDITIONAL_FIELD_DOES_NOT_EXIST` | The additional field does not exist. |
| 40404 | `CUSTOM_ATTRIBUTE_DOES_NOT_EXIST` | The custom attribute does not exist. |
| 40405 | `COMPANY_DOES_NOT_EXIST` | The company does not exist. |
| 40406 | `PLACEHOLDER_LIST_SCHEMA_MUST_EXIST` | The list attribute must be created before use. |
| 40407 | `NON_PARSABLE_DATE` | Invalid date/time value format in the request. |
### 405 Method Not Allowed [#405-method-not-allowed-people-api-error-codes]
| ID | Status | Description |
|:------:|---------------------------|:---------------------------------------------|
| 40501 | `READ_ONLY_ALLOWED` | This account is in read-only mode. |
| 40502 | `WRITE_SOURCES_RESTRICTED` | Profile data modification over API is disabled. |
### 409 Conflict [#409-conflict-people-api-error-codes]
| ID | Status | Description |
|:------:|----------------------------|:--------------------------------------------------------------------------------|
| 40901 | `IMPORT_ALREADY_IN_PROGRESS`| The merge batch is already in progress, please wait until the previous merge is completed. |
| 40902 | `OPTIMISTIC_LOCK` | Optimistic lock due to concurrent data updates. |
### 429 Too Many Requests [#429-too-many-requests-people-api-error-codes]
| ID | Status | Description |
|:------:|--------------------|--------------------------|
| 42901 | `TOO_MANY_REQUESTS` | There are too many requests. |