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
Use the Find option to quickly locate the code name you are looking for.
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 (opens in a new tab) 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
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 |
|---|---|
| 3 | PENDING_WAITING_DELIVERY Message has been successfully sent from our 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 our 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
Group ID: 2
The message has not been delivered.
| ID | Status |
|---|---|
| 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 the Support 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 for assistance. |
| 31 | UNDELIVERABLE_NOT_SENT The message has not been sent. |
DELIVERED
Group ID: 3
The message has been delivered.
| ID | Status |
|---|---|
| 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
Group ID: 4
The message has been sent and has either expired due to pending past its validity period (our platform defaults to 48 hours), or the delivery report from the operator has returned EXPIRED as a final status.
| ID | Status |
|---|---|
| 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 the Support 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 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
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 |
|---|---|
| 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 [email protected]. |
| 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 [email protected]. |
| 13 | REJECTED_SENDER The sender ID has been blocklisted on your account via the Infobip web interface. Remove the blocklist on your account or contact support for further assistance. |
| 14 | REJECTED_DESTINATION_BLOCKLISTED The destination address has been blocklisted either at the operator's request or on your account via the web interface. Remove the blocklist on your account via the Infobip web interface or contact support for more information. |
| 17 | REJECTED_PREPAID_PACKAGE_EXPIRED Account credits are past their validity period. Top up your sub-account 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 at [email protected] 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 [email protected] 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 at [email protected]. |
| 21 | REJECTED_SYSTEM_ERROR The request has been rejected due to an expected system error. Retry the submission or contact our Technical Support team 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 SMS 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 (fully featured binary message API method) or an inaccurate amount of characters when using esmclass:64 (UDH). For more information, visit the articles below or contact our support team 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. |
Voice status codes
REJECTED (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 |
|---|---|
| 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 request couldn’t be processed correctly. |
| 55 | REJECTED_MESSAGE_IS_EMPTY Native to Voice services, this status is returned in case there is no text sent in your Voice message request. |
| 56 | REJECTED_INVALID_NOTIFY_URL Native to Voice services, this status is returned in case the notifyUrl parameter is not formatted properly. For more information, see Voice messages over API. |
| 57 | REJECTED_INVALID_NOTIFY_CONTENT_TYPE Native to Voice services, this status is returned in case the notifyContentType parameter is not formatted properly. For more information, see Voice messages over API. |
| 58 | REJECTED_INVALID_DTMF_SIGN Defined value for repeating 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 at [email protected]. |
| 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 (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 |
|---|---|
| 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 set as our system limitation. |
Email status codes
REJECTED (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 |
|---|---|
| 75 | REJECTED_FREE_TRIAL_EXCEEDED This status code is returned by the API when a user's free trial has been exceeded. It means that the user has exceeded the allowed number of messages or other usage limits during the trial period and must upgrade to their plan 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. The error can be caused by the 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. It is set when a message goes over the limit of retries 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 the message processing. The validation error can be caused by issues such as an invalid sender, an invalid landing page, invalid preserved recipients, a missing template, and so on. |
Push notifications status codes
UNDELIVERABLE (group id: 2) - push notifications status codes
The message has not been delivered.
| ID | Status |
|---|---|
| 66 | UNDELIVERABLE_NO_DESTINATION The status occurs when in a Push API call in object TO defined filter which doesn’t resolve any pushRegistrationIds as destinations for Push delivery. Field to is used to query the message recipient segment. For example, you can try to target according to a “tag” which doesn’t exist in any of the instances of the requested ApplicationCode. It returns no destinations as we couldn’t find anything that would satisfy the requested conditions in our database. In another example, you can target all application instances (devices) with the Android OS. In this case, CloudType: GCM and API internally will resolve all destinations and send the message to all Android devices linked to the requested ApplicationCode. You can also check your valid registrations by using filtering in the Infobip web interface. For more information about User Data go to the following links: iOS and Android. |
REJECTED (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 |
|---|---|
| 65 | REJECTED_NO_APPLICATION The status occurs when an invalid or non-existent ApplicationCode is used in the field from in a Push API call. Each application profile has its own unique ApplicationCode. ApplicationCode is used in the SDK as a key identifier for the Application installed on an end user’s device able to communicate with our platform. For the paired device and installed app, pushRegistrationId is issued and it is uniquely linked to ApplicationCode. You should be able to get all available applications or check the configuration. |
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
}
Moments status codes
Below are the possible status codes for batch flow processing.
Status group PENDING
| ID | Status | Description |
|---|---|---|
| 200 | PENDING_ACCEPTED | A person has been accepted and going to be processed by Flow. |
General error codes
Error codes are grouped into error code groups with their own unique ID.
OK
Group ID: 0
The request has been completed successfully.
| ID | Permanent | Error |
|---|---|---|
| 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
Group ID: 1
The request has not been completed due to handset-related issues.
| ID | Permanent | Error |
|---|---|---|
| 1 | true | EC_UNKNOWN_SUBSCRIBER Typically, this indicates that the subscriber or recipient of the message is unknown or not recognized by the network. It means that the provided subscriber information, such as the phone number, does not exist or is an unknown user in the network's database. To resolve this error, it is recommended to verify the accuracy of the subscriber details by dialing the provided number. If the number is available, contact support for assistance. |
| 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 various reasons, such as an invalid or unregistered number, incomplete or incorrect subscriber information, or technical issues retrieving subscriber details. Resolving this error typically involves verifying and correcting the subscriber information and if the destination is correct and available, contact Support for assistance. |
| 6 | false | EC_ABSENT_SUBSCRIBER_SM This indicates that the destination numbers provided during the submissions were unreachable (not properly connected to the operator's network), powered off, or located in an area with limited/low coverage or subject to roaming restrictions. Resolving this error ensures that 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 currently roaming in another country or another operator’s infrastructure - roaming delivery is not guaranteed due to a lack of roaming agreements between many different operators. |
| 9 | true | EC_ILLEGAL_SUBSCRIBER Indicates that the mobile station failed authentication, often due to the subscriber's number being blocklisted or subscribed. Resolving this error typically involves investigating and addressing the underlying reasons for the subscriber's illegal status, which may involve contacting the network operator, or contact Support for assistance. |
| 11 | true | EC_TELESERVICE_NOT_PROVISIONED This indicates that the mobile subscription associated with this number does not support the short message service (SMS). It means that the requested service, such as SMS, is not available or activated for the subscriber's account. Resolving this error usually involves contacting the service provider or network operator to ensure the necessary teleservice is provisioned and activated for the subscriber's account. |
| 12 | true | EC_ILLEGAL_EQUIPMENT The IMEI check on the handset failed, indicating that the IMEI of the device is either blocklisted or unauthorized according to the system. Resolving this error typically involves ensuring the use of authorization. |
| 13 | false | EC_CALL_BARRED The operator suspended the subscriber's service, usually because of unpaid invoices. Resolving this error usually involves checking the subscriber's account status, ensuring sufficient balance or subscription plan, and contacting the network operator to lift any call barring restrictions if necessary. |
| 21 | false | EC_FACILITY_NOT_SUPPORTED The requested functionality or service is not supported by the handset or the network being used due to limitations, restrictions, or incompatibility. Resolving this error typically involves verifying the supported facilities or services, ensuring the subscriber's compatibility with the requested feature, and handset devices restart, and applying the newest software/firmware updates. |
| 27 | false | EC_ABSENT_SUBSCRIBER This indicates that the destination numbers provided during the submissions were unreachable (not properly connected to the operator's network), powered off, or located in an area with limited/low coverage or subject to roaming restrictions. Resolving this error involves ensuring that the subscriber's device is turned on and has a stable network connection. |
| 31 | false | EC_SUBSCRIBER_BUSY_FOR_MT_SMS Subscriber Busy For Mt SMS |
| 32 | false | EC_SM_DELIVERY_FAILURE Indicates that there was a failure in delivering an SMS message to the intended recipient. The failure may be related to the recipient's unavailability, memory capacity issues, or temporary communication issues between the operator and the end user. Resolving this error may involve verifying recipient details, or contact Support to investigate any potential network or configuration issues. |
| 33 | false | EC_MESSAGE_WAITING_LIST_FULL Message Waiting List Full |
| 34 | false | EC_SYSTEM_FAILURE System Failure |
| 35 | false | EC_DATA_MISSING Data Missing |
| 36 | false | EC_UNEXPECTED_DATA_VALUE Unexpected Data Value |
| 255 | false | EC_UNKNOWN_ERROR Unknown Error |
| 256 | false | EC_SM_DF_MEMORYCAPACITYEXCEEDED Indicates that the message inbox on the recipient's mobile phone is currently full, preventing the storage of new messages. To resolve this issue, delete the messages and clear the message inbox on the end user handset. |
| 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 two network components. |
| 502 | false | EC_NO_RESPONSE The message has been successfully processed and forwarded to the operator, but no response was returned from the operator upon the message submit request, or such error was reverted by the operator. The error also applies to similar errors on the SS7 network level. |
| 503 | false | EC_SERVICE_COMPLETION_FAILURE General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 504 | false | EC_UNEXPECTED_RESPONSE_FROM_PEER General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 507 | false | EC_MISTYPED_PARAMETER General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 508 | false | EC_NOT_SUPPORTED_SERVICE General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 509 | false | EC_DUPLICATED_INVOKE_ID General network protocol error caused by incompatible operator network protocol versions or parameters between two 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 via a mobile virtual network operator (MVNO). This restriction is on Short Code messages. |
| 573 | true | EC_SC_BLOCKED_BY_END_USER The end user has asked their mobile operator to block any messages sent from your Short Code. Additional messages from the same Short Code must not be sent to the phone number unless the end user opts in again. |
| 581 | false | EC_USER_OUT_OF_CREDIT End user out of prepay credit. The end user does not have enough credit on their phone account to receive the message. Message sending can be retried every 24 hours for no more than seven days. |
| 628 | true | EC_TEMPORARY_HANDSET_FAILURE Temporary handset failure. |
| 629 | true | EC_DEST_ADDRESS_UNABLE_TO_RECEIVE_SMS Destination address unable to receive SMS. |
| 1024 | false | EC_OR_APPCONTEXTNOTSUPPORTED General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1025 | false | EC_OR_INVALIDDESTINATIONREFERENCE General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1026 | false | EC_OR_INVALIDORIGINATINGREFERENCE General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1027 | false | EC_OR_ENCAPSULATEDAC_NOTSUPPORTED General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1028 | false | EC_OR_TRANSPORTPROTECTIONNOTADEQUATE General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1029 | false | EC_OR_NOREASONGIVEN General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1030 | false | EC_OR_POTENTIALVERSIONINCOMPATIBILITY General network protocol error caused by incompatible operator network protocol versions or parameters between two network components. |
| 1031 | false | EC_OR_REMOTENODENOTREACHABLE Mobile subscriber was not reachable due to a network operator protocol error. |
| 1152 | false | EC_NNR_NOTRANSLATIONFORANADDRESSOFSUCHNATURE 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 Mobile subscriber was not reachable due to a network operator protocol error. |
| 1155 | false | EC_NNR_SUBSYSTEMFAILURE Mobile subscriber was not reachable due to a network operator protocol error. |
| 1156 | false | EC_NNR_UNEQUIPPEDUSER Mobile subscriber was not reachable due to a network operator protocol error. |
| 1157 | false | EC_NNR_MTPFAILURE Mobile subscriber was not reachable due to a network operator protocol error. |
| 1158 | false | EC_NNR_NETWORKCONGESTION Mobile subscriber was not reachable due to a network operator protocol error. |
| 1159 | false | EC_NNR_UNQUALIFIED Mobile subscriber was not reachable due to a network operator protocol error. |
| 1160 | false | EC_NNR_ERRORINMESSAGETRANSPORTXUDT Mobile subscriber was not reachable due to a network operator protocol error. |
| 1161 | false | EC_NNR_ERRORINLOCALPROCESSINGXUDT Mobile subscriber was not reachable due to a network operator protocol error. |
| 1162 | false | EC_NNR_DESTINATIONCANNOTPERFORMREASSEMBLYXUDT Mobile subscriber was not reachable due to a network operator protocol error. |
| 1163 | false | EC_NNR_SCCPFAILURE Mobile subscriber was not reachable due to a network operator protocol error. |
| 1164 | false | EC_NNR_HOPCOUNTERVIOLATION Mobile subscriber was not reachable due to a network operator protocol error. |
| 1165 | false | EC_NNR_SEGMENTATIONNOTSUPPORTED Mobile subscriber was not reachable due to a network operator protocol error. |
| 1166 | false | EC_NNR_SEGMENTATIONFAILURE Mobile subscriber was not reachable due to a network operator protocol error. |
| 1281 | false | EC_UA_USERSPECIFICREASON Message was aborted by a network peer because of a network protocol error. |
| 1282 | false | EC_UA_USERRESOURCELIMITATION Message was aborted by a network peer because of a network protocol error. |
| 1283 | false | EC_UA_RESOURCEUNAVAILABLE Message was aborted by a network peer because of a network protocol error. |
| 1284 | false | EC_UA_APPLICATIONPROCEDURECANCELLATION Message was aborted by a network peer because of 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
Group ID: 2
User error occurred.
| ID | Permanent | Error |
|---|---|---|
| 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: - The mobile number is not on the mobile operator's network. - The phone number belongs to a prepaid user who does not have enough credit to receive a message. - The end user is not provisioned to receive a message from all short codes (or from specific short codes). |
| 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 at [email protected] to determine if your MT source address should be supported by the end user's mobile operator. |
| 433 | true | EC_ACCOUNT_ACCESS_DENIED Account access 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 Account not provisioned to use 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 Destination address not in whitelist 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 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_BLOCKED_AS_SPAM 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. |
| 2049 | true | EC_IMSI_BLACKLISTED IMSI blocklisted |
| 2052 | true | EC_BLACKLISTED_DESTINATIONADDRESS The destination number has been blocklisted either at the operator`s request or on your account via the Infobip web interface. Go to the Infobip web interface to remove the blocklist on your account or contact Support for more information. |
| 2053 | true | EC_BLACKLISTED_SENDERADDRESS The sender number has been blocklisted either at the operator's request or on your account via the Infobip web interface. Go to the Infobip web interface to remove the blocklist on your account or contact Support 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 reach out at [email protected]. |
| 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 EC_MESSAGE_CANCELED, or the same error code was reverted from the operator. |
| 4101 | true | EC_VALIDITYEXPIRED 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 EC_VALIDITYEXPIRED or the error code was reverted from the operator. |
| 4102 | true | EC_NOTSUBMITTEDTOSMPPCHANNEL Inbound SM can not be transferred via 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 at [email protected]. |
| 4104 | true | EC_DESTINATION_TXT_FLOODING Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of identical messages sent to a single number. |
OPERATOR_ERRORS
Group ID: 3
The request has not been completed due to operator issues.
| ID | Permanent | Error |
|---|---|---|
| 10 | true | EC_BEARER_SERVICE_NOT_PROVISIONED Suggests that the requested bearer service is not available or activated for the user or device attempting to access it. This can be due to service unavailability in the subscription, lack of network support, or configuration/provisioning issues. Resolving this error typically involves contacting the service provider or network operator to ensure the necessary bearer service is provisioned and activated for the subscriber's account. |
| 20 | false | EC_SS_INCOMPATIBILITY SS Incompatibility |
| 51 | true | EC_RESOURCE_LIMITATION Indicates that invoked MAP operation could not be finished due to the network congestion - this is an SS7 network congestion error on the MAP protocol level. |
| 71 | false | EC_UNKNOWN_ALPHABET Unknown Alphabet |
| 345 | true | EC_OPERATOR_NOT_FOUND Mobile operator not found for the destination address. The service performed a dynamic carrier lookup for the destination address, but it could not be identified; or, the MT source address is not a North American toll-free phone number or landline. |
| 375 | true | EC_SOURCE_ADDRESS_IS_BLOCKED Source address (recipient) is blocked or is not provisioned. |
| 488 | true | EC_TF_NUMBER_NOT_VERIFIED ''Toll-Free Number Not Verified'' which indicates that the number has either gone over the limit or they are trying to send to Canada and the number is not verified. Contact your Account Manager or reach out at [email protected] to get the TFN verified. |
| 501 | false | EC_INVALID_RESPONSE_RECEIVED Invalid Response Received |
| 560 | true | EC_SC_BLOCKED_FOR_END_USER Mobile operator blocking the end user from this Short Code |
| 561 | true | EC_CONTENT_BLOCKED_BY_OPERATOR Content blocked by mobile operator for this end user. |
| 562 | true | EC_SC_NOT_PROVISIONED Short code not provisioned with mobile operator. Contact your dedicated Account Manager or reach out at [email protected] if you believe that you are provisioned for the operator or if you want to begin provisioning. |
| 563 | true | EC_SC_EXPIRED Short code expired with mobile operator. Contact your dedicated Account Manager or reach out at [email protected] if you believe that you are provisioned for the operator or if you want to begin provisioning. |
| 564 | true | EC_SC_BLOCKED
|
| 566 | true | EC_DESTINATION_BLOCKED_BY_OPERATOR The mobile operator is blocking the phone number from receiving messages from Short Codes. This is likely due to the end user's account being suspended or barred in some way. |
| 568 | true | EC_DESTINATION_NOT_SMS_PROVISIONED Destination address not provisioned for SMS. |
| 569 | true | EC_DEST_ADDRESS_SUSPENDED Destination address suspended by the mobile operator. |
| 571 | false | EC_CAMPAIGN_ID_REJECTED Program ID or Campaign ID rejected by mobile operator. This error applies to messages sent to US mobile operators. The error indicates the program ID or campaign ID in the message request is not provisioned with the mobile operator. Contact your dedicated Account Manager or [email protected] if you are unsure why you received this error. |
| 574 | true | EC_BLOCKED_NEW_SUBSCRIPTIONS_FOR_SC New subscriptions for this short code are blocked by the mobile operator. Indicates that for a given short code, new subscribers are not allowed to receive or send messages. However, existing subscribers are still allowed to receive and send messages. |
| 592 | true | EC_ACCOUNT_NOT_PROVISIONED_FOR_SMS The end user's number belongs to a network for which the account is not provisioned, or we do not provide coverage for the specific network. |
| 630 | true | EC_DEST_OVERLOADED Destination overloaded. |
| 631 | true | EC_MOBILE_OPERATOR_NETWORK_ERROR Mobile operator network error. |
| 632 | true | EC_SMS_REJECTED_BY_MOBILE_OPERATOR SMS rejected by the mobile operator for attempted destination address. |
| 633 | true | EC_UNKNOWN_MOBILE_OPERATOR Message failed due to an unknown mobile operator error. |
| 810 | true | EC_FAILED_MESSAGE_DELIVERY Failed message delivery. |
| 811 | true | EC_MESSAGE_EXPIRED Message expired before it reached handset. |
| 815 | true | EC_MESSAGE_SUBMITTED_NOT_ACKED Message submitted to but not acknowledged by the mobile operator. |
| 2048 | false | EC_TIME_OUT Time Out |
| 2050 | true | EC_DEST_ADDRESS_BLACKLISTED The numbers were identified as blocklisted in the operator's DND (Do Not Disturb) database, provided by the operator, or the operator reverted the same error code. Resolving this error typically involves reviewing the blocklist status of the destination address, checking for any legitimate reasons for blocklisting, and taking appropriate actions to remove it. |
| 2051 | false | EC_INVALIDMSCADDRESS Text blocklisted |
| 4097 | false | EC_NOTSUBMITTEDTOGMSC Messages not passed to any operator and failed at Infobip platform |
| 4102 | true | EC_NOTSUBMITTEDTOSMPPCHANNEL Not Submitted To Smpp Channel |
| 5492 | true | EC_DUPLICATE_MESSAGE The same message has already been sent to this destination address. |
Voice error codes (legacy)
OK (group id: 0) - voice error codes
The request has been completed successfully.
| ID | Permanent | Error |
|---|---|---|
| 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 (group id: 1) - voice error codes
The request has not been completed due to handset-related issues.
| ID | Permanent | Error |
|---|---|---|
| 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 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 (group id: 3) - voice error codes
The request has not been completed due to operator issues.
| ID | Permanent | Error | |
|---|---|---|---|
| 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 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 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 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 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 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 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 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_VOICE_NOT_IMPLEMENTED The requested voice call feature is not implemented or supported. Contact Support for further assistance. | |
| 5503 | true | EC_VOICE_SERVICE_UNAVAILABLE The voice call service is temporarily unavailable. Retry the request later or contact Support for further information. |
Voice and WebRTC error codes
OK (group id: 0)
The request has been completed successfully.
| ID | Permanent | Error |
|---|---|---|
| 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 for further assistance. |
HANDSET_ERRORS (group id: 1)
The request has not been completed due to handset-related issues.
| ID | Permanent | Error |
|---|---|---|
| 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 (group id: 2)
User error occurred.
| ID | Permanent | Error |
|---|---|---|
| 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 | CANCELED 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 (group id: 3)
The request has not been completed due to operator issues.
| ID | Permanent | Error |
|---|---|---|
| 10300 | true | FORBIDDEN The received request was rejected. Contact Support 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 the Support team, who can provide further information and guidance. |
| 10308 | true | NETWORK_ERROR An error occurred in the network during the call. Check the network connection and contact Support for further investigation. |
| 10309 | true | SERVICE_UNAVAILABLE The call service is temporarily unavailable. Contact Support for assistance. |
| 10310 | true | UNKNOWN An unknown error occurred during the call. Contact Support 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 for assistance. |
| 10312 | true | CONGESTION The call could not be completed due to network congestion or overload. Contact Support for further investigation and assistance. |
| 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 for assistance. |
HANDSET_ERRORS (group id: 1) - WebRTC error codes
The request has not been completed due to handset-related issues.
| ID | Permanent | Error |
|---|---|---|
| 5720 | true | EC_NO_PEER_CONNECTION The peer connection has not been established. |
| 5721 | true | EC_INVALID_DTMF_CONFIG_NO_AUDIO_TRACK Invalid DTMF configuration (no audio track). |
| 5722 | true | EC_DTMF_UNAVAILABLE DTMF options are not available. |
| 5723 | true | EC_DTMF_INVALID_TONE Invalid DTMF tone sent. Allowed tones are digits 1-9, * and #. |
| 5724 | true | EC_NO_LOCAL_STREAM Local stream was not initialized. |
| 5725 | true | EC_NO_AUDIO_TRACK The audio track is missing. |
| 5726 | true | EC_NO_VIDEO_TRACK The video track is missing. |
| 5727 | true | EC_NO_DISPLAY_MEDIA Display media API is not available. |
| 5728 | true | EC_UNKNOWN_SCREEN_SHARE_ERROR Unknown screen share error. |
USER_ERRORS (group id: 2) - WebRTC error codes
User error occurred.
| ID | Permanent | Error |
|---|---|---|
| 5800 | true | EC_NO_ANSWER The end user received the call but did not answer it. |
| 5801 | true | EC_USER_BUSY The end user is currently busy and not able to receive the call. |
| 5802 | true | EC_PERMISSION_DENIED Permission to use a camera and/or microphone was denied. |
| 5803 | true | EC_DEVICE_NOT_FOUND Device does not have a camera and/or microphone connected/enabled. |
| 5804 | true | EC_DEVICE_NOT_AVAILABLE Camera or microphone is already in use. |
| 5805 | true | EC_ACTIVE_CALL_ON_INCOMING_CAL The end user received an incoming call while they were on another active call. |
| 5806 | true | EC_CALL_TERMINATED Call terminated. |
| 5850 | true | EC_USER_ALREADY_JOINED The end user is already joined on another device. |
| 5851 | true | EC_MAX_USERS_LIMIT_REACHED The maximum number of users was already reached. |
| 5852 | true | EC_VIDEO_PUBLISHERS_LIMIT_REACHED The maximum number of users that are publishing a video was already reached. |
OPERATOR_ERRORS (group id: 3) - WebRTC error codes
The request has not been completed due to operator issues.
| ID | Permanent | Error |
|---|---|---|
| 5768 | true | EC_CLIENT_URL_READ_FAILURE Could not read the client's URL. |
| 5769 | true | EC_CLIENT_URL_REACH_FAILURE Could not reach the client's URL. |
| 5900 | true | EC_FORBIDDEN The received request was rejected. |
| 5901 | true | EC_REQUEST_TIMEOUT There was no coverage for a specific destination number, or the end user could not be reached in time for the call. |
| 5902 | true | EC_INTERNAL_SERVER_ERROR The server could not process the request because of an unexpected error. |
| 5903 | true | EC_DESTINATION_NOT_FOUND The server has definitive information that the end user does not exist within the domain specified in the Request-URI. |
| 5904 | true | EC_SERVICE_TEMPORARY_UNAVAILABLE The service is temporarily unavailable. |
| 5905 | true | EC_REQUEST_PENDING The server has a pending request from the same dialog. |
| 5906 | true | EC_ADDRESS_INCOMPLETE The specified destination number is incomplete. |
| 5907 | true | EC_TEMPORARILY_NOT_AVAILABLE The destination address is currently unavailable. |
| 5990 | true | EC_CONNECTION_ERROR There has been a connection error. |
| 5991 | true | EC_UNKNOWN_WEBRTC_ERROR There has been an unknown WebRTC error. |
Push notification error codes
Registration error (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 |
|---|---|---|
| 8001 | true | EC_DEVICE_APP_UNINSTALL User has uninstalled the application on device or device cloud token expired. |
| 8002 | true | EC_GCM_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 is not found at Infobip Push service. Check your message target parameters. |
| 8004 | true | EC_NO_REGISTRATION_ID_FOUND Registration with provided PushRegistrationId does not exist or has expired. |
Cloud error (group id: 3) - push notification error codes
Messages not sent due to Clouds communication issues.
| Id | Permanent | Error |
|---|---|---|
| 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_GCM_AUTH_DATA Invalid cloud authentication data (Server Key). FCM responded with status 401 (Unauthorized). Check your Application configuration for Android on the Infobip web interface. |
| 8007 | true | EC_INVALID_APNS_CERT Invalid certificate for APNS. Check your Application configuration for iOS on the Infobip 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 Infobip web interface. |
| 8009 | true | EC_PUSH_INTERNAL_REQUEST_ERROR Internal error. Try again later and, if the problem persists, contact Support for further assistance. |
| 8010 | true | EC_INVALID_PUSH_PAYLOAD Invalid push payload data. Contact Support for further assistance. |
| 8011 | true | EC_PUSH_INTERNAL_GW_ERROR Internal error. Try again later and if problem persists, contact Support for further assistance. |
| 8012 | true | EC_PUSH_CLOUD_TEMP_UNAVAILABLE Push Cloud (FCM or APNS) is temporarily unavailable. Message is pending in retry. |
MMS Error Codes
| ID | Status |
|---|---|
| 15000 | EC_MMS_GENERAL_ERROR MMS provider general error. |
| 15002 | EC_SYSTEM_ERROR System error. |
| 15003 | EC_MSISDN_NOT_REGISTERED MSISDN is not registered by the operator. |
| 15004 | EC_DEFFERED Message is deferred. The end user's handset has retrieved the MMS header, but not downloaded the full message. |
| 15005 | EEC_MMS_FORWARDED The end user has forwarded the MMS to another address without retrieving it. |
| 15006 | EC_VALIDITY_EXPIRED Mobile operator could not contact the handset before reaching the expiry time. |
| 15007 | EC_CONTENT_CANNOT_BE_DOWNLOADED_ON_HANDSET Content cannot be downloaded on handset. |
| 15008 | EC_PROVIDER_DELIVERY_ERROR MMS provider delivery error. |
| 15009 | EC_RECEPIENT_NOT_FOUND Recipient not found on mobile operator. |
| 15010 | EC_SOURCE_ADDRESS_NOT_PROVISIONED Source address not provisioned with the operator. |
| 15011 | EC_RECEPIENT_BLOCKED_BY_OPERATOR Recipient blocked by receiving MMS by the operator. |
| 15012 | EC_DRM_NOT_SUPPORTED DRM not supported. |
| 15013 | EC_MMS_CONTENT_BLOCKED_BY_OPERATOR MMS content blocked or unsupported by the operator. |
| 15014 | EC_MMS_INVALID_SUBJECT Invalid MMS subject in request. |
| 15015 | EC_MMS_SC_BLOCKED_BY_END_USER End user has blocked traffic from this specific SC. |
| 15016 | EC_UNKNOWN_CARRIER Unable to determine the mobile operator. |
| 15017 | EC_RECEPIENT_DEACTIVATED Recipient is deactivated. |
| 15018 | EC_RECEPIENT_SUSPENDED Recipient is suspended from the service. |
| 15019 | EC_HANDSET_DOES_NOT_SUPPORT_MMS MMS is not supported on handset. |
| 15020 | EC_CAMPAIGN_BLOCKED_BY_OPERATOR Campaign blocked by mobile operator. |
| 15021 | EC_CAMPAIGN_INFO_NOT_PROVISIONED Campaign information is not provisioned for this mobile operator. |
| 15022 | EC_URL_ATTACHMENT_TO_LARGE Cannot retrieve MMS as the URL attachment is too large. |
| 15023 | EC_FAILED_TO_ROUTE_MESSAGE Failed to route MMS message. |
| 15024 | EC_REMOTE_CONTENT_FAILURE Could not retrieve remote content. |
| 15025 | EC_REMOTE_CONTENT_INTERNAL_FAILURE Internal error trying to fetch remote content. |
| 15026 | EC_TOO_BIG_CONTENT Message has been rejected. |
| 15200 | EC_INVALID_MSG_TYPE Invalid MMS message type. |
| 15201 | EC_MMS_INVALID_DESTINATION_ADDRESS Invalid MMS destination address. |
| 15202 | EC_MMS_INVALID_SOURCE_ADDRESS Invalid MMS source address. |
| 15203 | EC_INVALID_SUBJECT Invalid MMS subject parameter. |
Email error codes
Dropped (group id: 1)
The request has not been completed successfully as there was an issue noticed before the sending attempt causing an error.
The
| ID | Permanent | Name |
|---|---|---|
| 6003 | true | EC_UNSUBSCRIBED_EMAIL_ADDRESSThe recipient opted out of receiving updates from this specific address. If removal is desired, complete the request by going to Do not contact in the web interface. |
| 6034 | true | EC_SUPPRESSED_BOUNCEA bounce SMTP response from the recipient's mailbox provider earlier has resulted in the recipient address being suppressed. |
| 6035 | true | EC_SUPPRESSED_SPAM_COMPLAINTDue 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. |
| 6033 | true | EC_INVALID_CC_BCC_EMAIL_ADDRESSThe request contains invalid addresses in the CC and/or BCC. Ensure that the addresses are correctly formatted by checking them. |
| 6023 | true | EC_BLOCKED_SUSPICIOUS_ACTIVITYYour domain has been blocked by Infobip due to suspicious activity. Should you require any additional information regarding this matter, contact Support or your account manager. |
| 6036 | true | EC_SENDING_DOMAIN_UNVERIFIEDDomain does not currently have all required DNS records set up correctly. Check your DNS configuration. See Verify your sender domain. |
| 6016 | true | EC_SENDER_DOMAIN_BOUNCE_BLOCKEDYour 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. Use the Email validation service to help you with the procedure. |
| 6029 | true | EC_SENDER_ADDRESS_INVALIDThe 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. |
| 6018 | true | EC_REQUEST_INVALIDThe submitted request is not valid. Ensure that the data and request parameters are accurate and in the right format. |
| 6002 | true | EC_SPAM_DETECTEDThe content you are trying to send was detected as possible spam by Infobip. Review the Deliverability recommendations and adjust your content accordingly before retry. |
| 6038 | true | EC_EMAIL_CONTENT_EXPIREDThe content in a Template expired due to the lack of regular usage. To help the situation, check the content and re-upload it to help the situation. If the issue persists, contact Support. |
| 6021 | true | EC_EMAIL_PLACEHOLDERS_ERRORError with Placeholders in the Content. Check the placeholders and confirm that there are no issues or typos in them and retry. |
| 6039 | true | EC_EMAIL_TEMPLATE_LANGUAGE_ERRORError in Template Language in your Content. See Template language personalization or more details. If the problem persists, contact Support. |
| 6024 | true | EC_EMAIL_TOO_MANY_URLSMaximum 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_PARAMSTracking parameters in the email are invalid. Review and help these before the retry. |
| 6026 | true | EC_EMAIL_LANDING_PAGE_PLACEHOLDERS_SIZE_EXCEEDEDSize 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_HEADERSThe headers of the email are invalid or improperly formatted. Check the headers and ensure they meet the required format. |
| 6030 | true | EC_EMAIL_INVALID_LANDING_PAGEThe 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_RECIPIENTInvalid preserved recipient in CC or BCC. Check the recipient list and ensure that all preserved recipients are valid and the limit is not reached. |
| 6020 | true | EC_EMAIL_TEMPLATE_NOT_FOUNDThe Email Template from the request could not be found. Make sure that the Template ID is correct before retry. |
| 6040 | true | EC_EMAIL_TEMPLATE_EXPIREDThe 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_SAVEDThe Template was not saved. Make sure the requested Template is correctly stored on the Infobip web interface before retry. |
Bounced (group id: 2)
The response from the mailbox provider indicates that there was an error and the delivery attempt was unsuccessful.
| ID | Permanent | Name |
|---|---|---|
| 6010 | false | EC_RECIPIENT_INBOX_FULLThe 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. |
| 6007 | false | EC_MAILBOX_TEMPORARY_UNAVAILABLEThe recipient's mailbox is temporarily unavailable. Retry the email in a few hours and contact Support if you continue to encounter the same response for the additional checks. |
| 6017 | false | EC_SENDER_IP_BLACKLISTEDThe IP address assigned to your domain has been blacklisted. Review using the Deliverability recommendations and request the delisting on the relevant blacklist. |
| 6046 | false | EC_UNSOLICITED_RECIPIENTThe 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. |
| 6011 | false | EC_SOFT_BOUNCEResponse indicates a temporary delivery error. Retry sending and if the same response is returned, contact the recipient to attend to the situation. |
| 6006 | true | EC_INVALID_EMAIL_ADDRESSThe recipient's email address provided is either invalid, inactive, or disabled. Check for possible typos and validate the address before the retry. Use the Email validation service to help you with the procedure. |
| 6009 | true | EC_MAILBOX_PERMANENTLY_UNAVAILABLEThe recipient's mailbox provider (domain) might be permanently unavailable. Contact the recipient and attend to the situation before retry. |
| 6037 | true | EC_RECIPIENT_DOMAIN_MX_NOT_FOUNDThe 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_REVERTEDThe content in the email was flagged as spam by the mailbox provider. Review the Deliverability recommendations and adjust your content accordingly before retry. |
| 6043 | true | EC_SUSPICIOUS_CONTENTMailbox 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_SENDERRecipient 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 and if the error repeats, contact the mailbox provider to resolve the situation. |
| 6045 | true | EC_RECIPIENT_DOMAIN_POLICY_ERRORMailbox 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. |
| 6047 | true | EC_DOMAIN_CONFIGURATION_ERRORYour 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_ISSUERecipient 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 the further instructions. |
| 6049 | true | EC_SENDER_DOMAIN_BLACKLISTEDYour domain has been blockisted by the recipient mailbox. Review the Deliverability recommendations and request the delisting on the relevant blocklist. |
| 6012 | true | EC_HARD_BOUNCEResponse is indicating a permanent error related to the delivery. Contact the recipient to confirm and solve the situation. |
System Error (group id: 3)
The request has not been successful due to the issue on the Infobip end.
| ID | Permanent | Name |
|---|---|---|
| 6013 | false | EC_INTERNAL_SYSTEM_ERRORSomething went wrong on the Infobip end. Retry the traffic and contact Support if the same error is returned. |
Chat error codes
(RCS, WhatsApp, Messenger, LINE, Viber, Zalo, KakaoTalk)
Client error (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 |
|---|---|---|
| 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. To resolve this error, verify the user's details or ensure that the MSISDN is correct and belongs to an active user. |
| 7003 | true | EC_BLOCKED_USER Indicates that the user has been blocked or restricted from accessing the messages. 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 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 for further assistance. |
| 7005 | true | EC_FORBIDDEN_ACCESS Indicates that access to the requested resource or service is forbidden. Resolution steps involve verifying the user's access rights and permissions, that the application is allowed to send messages, and 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. Verify the request data and ensure that it follows the required format or check the API documentation for the correct request structure or contact our customer support for additional guidance. |
| 7007 | true | EC_ILLEGAL_TRAFIC_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 the support team who can provide further information and guidance. |
| 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 on an incorrect message template. 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, ensure a new session, or extend the existing session by the user or application. |
| 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 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 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. 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. Resolution steps involve investigating the mapping issue, reviewing and resolving any inconsistencies or errors in the mapping process, and contacting support 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 this error, check network connectivity and refresh the content, clear the cache and update the app or software, or verify device compatibility and contact support if the error persists. |
| 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 local or remotely. To resolve this error, validate its accuracy and consistency, and address any mismatches or inconsistencies, consider reaching out to our support team for additional assistance. |
| 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 the Meta. To resolve this error, update the mobile app to a supported version, ensure compatibility with the Meta requirements, and address any version-related issues towards support 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. |
| 7102 | true | EC_DATA_MISMATCH Indicates a data mismatch or inconsistency, whether it's in a local or remote context. To resolve this issue, first, verify the accuracy and consistency of the data. If you identify any discrepancies or inconsistencies, consider reaching out to our support team 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 error (group id: 2) - chat error codes
The request has not been completed successfully due to a service provider error.
| ID | Permanent | Error |
|---|---|---|
| 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 and If the issue persists, it is advised to reach out to Support for further assistance and investigation. |
| 7051 | false | EC_PROVIDER_TIMEOUT Signifies a timeout or connection issue with the provider and Infobip's platform. To resolve this error, It is recommended to contact customer support 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 for further assistance. |
System Error (group id: 3) - chat error codes
The request has not been completed successfully due to a system-related error.
| ID | Permanent | Error |
|---|---|---|
| 7080 | true | EC_INTERNAL_ERROR Indicates an internal error or issue within the system or service. To resolve this error, contact support 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 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 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 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 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 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 Sales to enable it. |
| 301 | EC_OPERATION_NOT_ALLOWED | SYNC | Service is not allowed for this account. Contact Sales to enable it. |
| 302 | EC_COUNTRY_NOT_ALLOWED | SYNC | Destination country is not allowed for this account. Contact Sales to enable it. |
| 303 | EC_GATEWAY_NOT_ALLOWED | SYNC | Provider is not allowed for this account. Contact Sales 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 Sales 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 [email protected] for more details. |
| 310 | EC_SIM_SWAP_DETECTED | CALLBACK | No coverage for the requested phone number. |
| 1000 | EC_USER_INTERNAL_ERROR | SYNC & CALLBACK | Internal error on the Infobip platform. Contact Support to resolve the issue. |
DLT error codes
NOTE
Applicable only to the India region.
| ID | Status |
|---|---|
| 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, etc. |
| 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 check with 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, 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 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, and correct 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 linkage 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 check the category of service entity or 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 usage 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 team 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. Engage with your DLT service provider or support team to address and resolve customer-specific DLT compliance matters. |
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's 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.
Status group REJECTED
| 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
| 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 (e.g., 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
| 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
| 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
| ID | Status | Description |
|---|---|---|
| 40901 | IMPORT_ALREADY_IN_PROGRESS | The merge batch is already in progress, please wait until previous merge is completed. |
| 40902 | OPTIMISTIC_LOCK | Optimistic lock due to concurrent data updates. |
429 Too Many Requests
| ID | Status | Description |
|---|---|---|
| 42901 | TOO_MANY_REQUESTS | Too many requests. |