{"_id":"588b3e266aca6f2500d114da","parentDoc":null,"__v":0,"category":{"_id":"54eb63b959b1172100334faf","project":"54eb50e5615ffc1900305a16","version":"54eb63b859b1172100334fae","pages":["54eb63b959b1172100334fb4","54eb63b959b1172100334fb5","54eb63b959b1172100334fb6","551539c3c859ac2f0001b46b","55153c3ac28d6125001b886d","55153e1fc859ac2f0001b470","5515424bc28d6125001b887b","55154597f854a3190036872d","551547cdbc466623002afe73","56c06e1ccfc5470d0018915d"],"__v":8,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-02-23T16:10:14.298Z","from_sync":false,"order":1,"slug":"getting-started","title":"Getting started"},"version":{"_id":"54eb63b859b1172100334fae","project":"54eb50e5615ffc1900305a16","forked_from":"54eb63a1867e1917009b711d","__v":26,"createdAt":"2015-02-23T17:30:32.501Z","releaseDate":"2015-02-23T17:30:32.501Z","categories":["54eb63b959b1172100334faf","54eb63b959b1172100334fb0","54eb63b959b1172100334fb1","54eb63b959b1172100334fb2","54ed8dd4ab373e2300f50eae","54ed99b2ab373e2300f50ede","55153a6de68daa2f00cff838","551546edbc466623002afe72","5515472ac28d6125001b8884","55154749c28d6125001b8885","555d9b4106dfec0d00d38ea7","5613e06e433e5735007c7708","5624bbb785a31117001c5403","56669e857cc81e0d00253f8e","568b8d837a42220d00498311","56a632277ef6620d00e2f18a","56d8147c3eb4dd0b00201aac","57a9ce2fac6db30e000d7efd","57a9cf4e944ea60e00dc3f74","58172386715dce0f00da4aa0","582dc59ee1b8692300c0dd03","589b19b4fec2730f0082e040","58b04a023529383900a759b5","58b92d1598157a0f004869bf","592e7685c58275000f20174f","59392839e376d4002f8a0474","59393064e376d4002f8a05a1","5947ae0d4005e2000f3a4fec","594a74df1d1de5001ab3517a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1"},"project":"54eb50e5615ffc1900305a16","user":"54eb4fdedf7add210007b29b","updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-01-27T12:33:42.611Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":11,"body":"While 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 in case you are looking for a resolution of the problem. \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"Use page **Search field** or **Find on page** web browser feature to quickly locate the code name you are looking for.\",\n  \"title\": \"Find code name\"\n}\n[/block]\nCode lists:\n\n* [HTTP status codes](#http-status-codes)\n* [API Status codes](#api-status-codes)\n * [General status codes](#section-general-status-codes)\n * [Voice status codes](#section-voice-status-codes)\n * [Push notification status codes](#section-push-notifications-status-codes)\n* [Error codes](#error-codes)\n * [General error codes](#section-general-error-codes)\n * [Voice error codes](#section-voice-error-codes)\n * [Push notification error codes](#section-push-notification-error-codes)\n * [Email error codes](#section-email-error-codes)\n * [Chat error codes](#section-chat-error-codes)\n\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"HTTP status codes\"\n}\n[/block]\nEvery HTTP transaction has a status code sent back by the server to define how the server handled the transaction. Most common statuses you may have encountered are `200 OK` and `404 Not Found`\n\n[Learn more about HTTP status codes here](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"API Status codes\"\n}\n[/block]\nBesides standard HTTP status code, status object may be returned as part of the API response message, delivery report or message log.\n\nStatus object example:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{  \\n   \\\"groupId\\\":3,\\n   \\\"groupName\\\":\\\"DELIVERED\\\",\\n   \\\"id\\\":5,\\n   \\\"name\\\":\\\"DELIVERED_TO_HANDSET\\\",\\n   \\\"description\\\":\\\"Message delivered to handset\\\"\\n}\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n##General status codes\n\n###PENDING (group id: 1) - general status codes\nMessage has been processed and sent to the next instance i.e. mobile operator.\n\n|Id|Status|\n|-|-|\n|3|`PENDING_WAITING_DELIVERY`<ul><li>Message has been processed and sent to the next instance i.e. mobile operator with request acknowledgment from their platform. Delivery report has not yet been received, and is awaited thus the status is still pending.</li></ul>|\n|7|`PENDING_ENROUTE`<ul><li>Message has been processed and sent to the next instance i.e. mobile operator.</li></ul>|\n|26|`PENDING_ACCEPTED`<ul><li>Message has been accepted and processed, and is ready to be sent to the next instance i.e. operator.</li></ul>|\n\n###UNDELIVERABLE (group id: 2) - general status codes\nMessage has not been delivered.\n\n|Id|Status|\n|-|-|\n|4|`UNDELIVERABLE_REJECTED_OPERATOR`<ul><li>Message has been sent to the operator, whereas the request was rejected, or a delivery report with status \"REJECTED\" was reverted.</li></ul>|\n|9|`UNDELIVERABLE_NOT_DELIVERED`<ul><li>Message has been sent to the operator, but has failed to delivery, since a delivery report with status \"UNDELIVERED\" was reverted from the operator.</li></ul>|\n\n###DELIVERED (group id: 3) - general status codes\nMessage has successfully been processed and delivered.\n\n|Id|Status|\n|-|-|\n|2|`DELIVERED_TO_OPERATOR`<ul><li>Message has been successfully sent and delivered to the operator.</li></ul>|\n|5|`DELIVERED_TO_HANDSET`<ul><li>Message has been successfully processed and delivered to recipient.</li></ul>|\n\n###EXPIRED (group id: 4) - general status codes\nMessage has been sent, and has either expired due to being pending past its validity period (our platform default is 48 hours), or the delivery report from the operator has reverted the expired as a final status.\n\n|Id|Status|\n|-|-|\n|15|`EXPIRED_EXPIRED`<ul><li>The message was received and sent to the operator, however it has been pending until the validity period has expired, or the operator returned EXPIRED status in the meantime.</li></ul>|\n|29|`EXPIRED_DLR_UNKNOWN`<ul><li>The message has been received and forwarded to the operator for delivery, however the delivery report from the operator has not been formatted correctly, or has not been recognized as valid.</li></ul>|\n\n###REJECTED (group id: 5) - general status codes\nMessage has been received, but has either been rejected by Infobip, or the operator has reverted Rejected as final status.\n\n|Id|Status|\n|-|-|\n|6|`REJECTED_NETWORK`<ul><li>Message has been received, but the network is either out of our coverage or not setup on your account. Your account manager can inform you on the coverage status or setup the network in question.</li></ul>|\n|8|`REJECTED_PREFIX_MISSING`<ul><li>Message has been received, but has been rejected as the number is not recognized due to either incorrect number prefix or  number length. This information is different for each network and is regularly updated.</li></ul>|\n|10|`REJECTED_DND`<ul><li>Message has been received, and rejected due to the user being subscribed to DND (Do Not Disturb) services, disabling any service traffic to their number.</li></ul>|\n|11|`REJECTED_SOURCE`<ul><li>Your account is set to accept only registered sender ID-s while the sender ID defined in the request has not been registered on your account.</li></ul>|\n|12|`REJECTED_NOT_ENOUGH_CREDITS`<ul><li>Your account is out of credits for further submission - please top up your account. For further assistance in topping up or applying for online account topup service you may contact your account manager.</li></ul>|\n|13|`REJECTED_SENDER`<ul><li>The sender ID has been blacklisted on your account via Infobip webites portals - please remove the blacklist on your account or contact Support for further assistance.</li></ul>|\n|14|`REJECTED_DESTINATION`<ul><li>The destination number has been blacklisted either at the operator request or on your account via Infobip webites portals - please remove the blacklist on your account via portal.infobip.com or contact Support for more information.</li></ul>|\n|17|`REJECTED_PREPAID_PACKAGE_EXPIRED`<ul><li>Account credits have been expired past their validity period - please topup your subaccount with credits to extend the validity period.</li></ul>|\n|18|`REJECTED_DESTINATION_NOT_REGISTERED`<ul><li>Your account has been setup for submission only to a single number for testing purposes - kindly contact your manager to remove the limitation.</li></ul>|\n|19|`REJECTED_ROUTE_NOT_AVAILABLE`<ul><li>Mesage has been received on the system, however your account has not been setup to send messages i.e. no routes on your account are available for further submission. Your account manager will be able to setup your account based on your preference.</li></ul>|\n|20|`REJECTED_FLOODING_FILTER`<ul><li>Message has been rejected due to a anti-flooding mechanism. By default, a single number can only receive 20 varied messages and 6 identical messages per hour. If there is a requirement, the limitation can be extended per account on request to your account manager.</li></ul>|\n|21|`REJECTED_SYSTEM_ERROR`<ul><li>The request has been rejected due to an expected system system error, please retry submission or contact our technical support team for more details.</li></ul>|\n|23|`REJECTED_DUPLICATE_MESSAGE_ID`<ul><li>The request has been rejected due to a duplicate message ID specified in the submit request, while message ID-s should be a unique value. For more information, please revisit https://dev.infobip.com/v1/docs/bulk-id-and-message-id.</li></ul>|\n|24|`REJECTED_INVALID_UDH`<ul><li>Message has been received, while 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 feel free to visit the below articles or contact our Support team for clarification.<br />https://en.wikipedia.org/wiki/User_Data_Header<br />https://en.wikipedia.org/wiki/Concatenated_SMS</li></ul>|\n|25|`REJECTED_MESSAGE_TOO_LONG`<ul><li>Message has been received, but the total message length is more than 25 parts or message text which exceeds 4000 bytes as per our system limitation.</li></ul>|\n|51|`MISSING_TO`<ul><li>The request has been received, however the \"to\" parameter has not been set or it is empty, i.e. there must be valid recipients to send the message.</li></ul>|\n\n##Voice status codes\n\n###REJECTED (group id: 5) - voice status codes\nMessage has been received, but has either been rejected by Infobip, or the operator has reverted the rejected as final status.\n\n|Id|Status|\n|-|-|\n|52|`REJECTED_INVALID_DESTINATION`<ul><li>The request has been received, however the destination is invalid - the number prefix is not correct as it does not match a valid number prefix by any mobile operator. Number length is also taken into consideration in verifying number number validity.</li></ul>|\n|53|`REJECTED_INVALID_AUDIO_FILE_URL`<ul><li>The URL of audio file is invalid and could not be read properly.</li></ul>|\n|54|`REJECTED_UNSUPPORTED_LANGUAGE`<ul><li>The language submitted within the request is not supported and request couldn't be processed correctly.</li></ul>|\n|55|`REJECTED_MESSAGE_IS_EMPTY`<ul><li>Native to Voice services, this status is returned in case there is no text sent in your Voice message request.</li></ul>|\n|56|`REJECTED_INVALID_NOTIFY_URL`<ul><li>Native to Voice services, this status is returned in case the notifyUrl parameter is not formatter properly. Please revisit the documentation [here](/docs/fully-featured-voice-messages).</li></ul>|\n|57|`REJECTED_INVALID_NOTIFY_CONTENT_TYPE`<ul><li>Native to Voice services, this status is returned in case the notifyContentType parameter is not formatter properly. Please revisit the documentation on [here](/docs/fully-featured-voice-messages).</li></ul>|\n|58|`REJECTED_INVALID_DTMF_SIGN`<ul><li>Defined value for repeating message is invalid and must be positive number.</li></ul>|\n|59|`REJECTED_INVALID_DTMF_TIMEOUT`<ul><li>Defined value for the waiting period is invalid and must be positive number.</li></ul>|\n|60|`REJECTED_INVALID_RING_TIMEOUT`<ul><li>Defined value for duration of call is invalid and must be positive number.</li></ul>|\n|61|`REJECTED_INVALID_CALL_TIMEOUT`<ul><li>Defined value for total period of call is invalid and must be positive number.</li></ul>|\n|62|`REJECTED_INVALID_MACHINE_DETECTION`<ul><li>The action which attempts to detect answering machines at the beginning of the call is invalid.</li></ul>|\n|63|`REJECTED_INVALID_ACTIONS`<ul><li>Actions submitted in HTTP API request are invalid.</li></ul>|\n|64|`REJECTED_INVALID_ACTION_GROUPS`<ul><li>Action groups submitted in HTTP API request are invalid.</li></ul>|\n\n##Push notifications status codes\n\n###UNDELIVERABLE (group id: 2) - push notifications status codes\nMessage has not been delivered.\n\n|Id|Status|\n|-|-|\n|66|`UNDELIVERABLE_NO_DESTINATION`<ul><li>The status occurs when in 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 by some \"tag\" which doesn't exist at any of instances of requested ApplicationCode, then it will return \"no destinations\" as we couldn't find in our database anyone which would satisfy requested conditions. In another example, you may want to target all application instances (devices) with Android OS. In this case you have to use CloudType: `GCM` and API internally will resolve all destinations and will send message to all android devices linked to requested ApplicationCode. You also can check you valid registrations by filtering in our [web interface](https://portal.infobip.com/subscribers/subscribers). More information about User Data you can find at our SDK pages: [iOS ](https://github.com/infobip/mobile-messaging-sdk-ios/wiki/User-data)and [Android](https://github.com/infobip/mobile-messaging-sdk-android/wiki/User-data)</li></ul>|\n\n###REJECTED (group id: 5) - push notifications status codes\nMessage has been received, but has either been rejected by Infobip, or the operator has reverted the rejected as final status.\n\n|Id|Status|\n|-|-|\n|65|`REJECTED_NO_APPLICATION `<ul><li>The status occurs when in Push API call is used invalid or not existent ApplicationCode in field `from`. Each application profile has it's own unique ApplicationCode. ApplicationCode is used in SDK as key identifier for Applicatoin installed on end user device being able to communicate with our platform. For the pair device + installed app pushRegistrationId is issued and it is uniquely linked to ApplicactionCode.  It's possible to get all available applications [here](/docs/push-application-get). Or check configuration [here](/push/applications).</li></ul>|\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Error codes\"\n}\n[/block]\nError object can be returned as part of the send message response or Delivery report response.\n\nError object example:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{  \\n   \\\"groupId\\\":0,\\n   \\\"groupName\\\":\\\"OK\\\",\\n   \\\"id\\\":0,\\n   \\\"name\\\":\\\"NO_ERROR\\\",\\n   \\\"description\\\":\\\"No Error\\\",\\n   \\\"permanent\\\":false\\n}\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\n##General error codes\n\n###OK (group id: 0) - general error codes\nThe request has been completed successfully.\n\n|Id|Permanent|Error|\n|-|-|-|\n|0|false|`NO_ERROR`<ul><li>There is no error description provided. Mostly returned for successful delivery or when error code was not returned by the operator.</li></ul>|\n\n###HANDSET_ERRORS (group id: 1) - general error codes\nThe request has not been completed due to handset related issues.\n\n|Id|Permanent|Error|\n|-|-|-|\n|1|true|`EC_UNKNOWN_SUBSCRIBER`<ul><li>The number does not exist or it has not been assigned to any active subscriber in the operator's user database.</li></ul>|\n|5|false|`EC_UNIDENTIFIED_SUBSCRIBER`<ul><li>Unidentified Subscriber</li></ul>|\n|6|false|`EC_ABSENT_SUBSCRIBER_SM`<ul><li>The subscriber is detected unavailable, as there was no paging response from the handset. This is often due to the handset being switched off or in low signal area. Applies to MAP protocol version 3.</li></ul>|\n|8|false|`EC_ROAMING_NOT_ALLOWED`<ul><li>The subscriber is currently in roaming at another country or other operator's infrastructure - roaming delivery is not guaranteed due to lack of roaming agreements between many different operator.</li></ul>|\n|9|true|`EC_ILLEGAL_SUBSCRIBER`<ul><li>Illegal Subscriber</li></ul>|\n|11|true|`EC_TELESERVICE_NOT_PROVISIONED`<ul><li>The subscriber's mobile service has been suspended by the operator.</li></ul>|\n|12|true|`EC_ILLEGAL_EQUIPMENT`<ul><li>Illegal Equipment</li></ul>|\n|13|false|`EC_CALL_BARRED`<ul><li>The subscriber is set to DND (Do Not Disturb) service, opting out of receiving any service traffic to their number.</li></ul>|\n|21|false|`EC_FACILITY_NOT_SUPPORTED`<ul><li>Facility Not Supported</li></ul>|\n|27|false|`EC_ABSENT_SUBSCRIBER`<ul><li>The subscriber is offline in the network, as confirmed by the handset's paging response. This is often due to the handset being switched off.</li></ul>|\n|31|false|`EC_SUBSCRIBER_BUSY_FOR_MT_SMS`<ul><li>Subscriber Busy For Mt SMS</li></ul>|\n|32|false|`EC_SM_DELIVERY_FAILURE`<ul><li>SM Delivery Failure</li></ul>|\n|33|false|`EC_MESSAGE_WAITING_LIST_FULL`<ul><li>Message Waiting List Full</li></ul>|\n|34|false|`EC_SYSTEM_FAILURE`<ul><li>System Failure</li></ul>|\n|35|false|`EC_DATA_MISSING`<ul><li>Data Missing</li></ul>|\n|36|false|`EC_UNEXPECTED_DATA_VALUE`<ul><li>Unexpected Data Value</li></ul>|\n|255|false|`EC_UNKNOWN_ERROR`<ul><li>Unknown Error</li></ul>|\n|256|false|`EC_SM_DF_MEMORYCAPACITYEXCEEDED`<ul><li>SM DF Memory Capacity Exceeded</li></ul>|\n|257|false|`EC_SM_DF_EQUIPMENTPROTOCOLERROR`<ul><li>SM DF Equipment Protocol Error</li></ul>|\n|258|false|`EC_SM_DF_EQUIPMENTNOTSM_EQUIPPED`<ul><li>SM DF Equipment Not SM Equipped</li></ul>|\n|259|false|`EC_SM_DF_UNKNOWNSERVICECENTRE`<ul><li>SM DF Unknown Service Centre</li></ul>|\n|260|false|`EC_SM_DF_SC_CONGESTION`<ul><li>SM DF Sc Congestion</li></ul>|\n|261|false|`EC_SM_DF_INVALIDSME_ADDRESS`<ul><li>SM DF InvalidSME Address</li></ul>|\n|262|false|`EC_SM_DF_SUBSCRIBERNOTSC_SUBSCRIBER`<ul><li>SM DF Subscribernotsc Subscriber</li></ul>|\n|500|false|`EC_PROVIDER_GENERAL_ERROR`<ul><li>Provider General Error</li></ul>|\n|502|false|`EC_NO_RESPONSE`<ul><li>The message has been successfully processed and forwarded to the operator, but no response was returned from the operator upon message submit request, or such error was reverted by the operator. The error also applies to similar errors on SS7 network level.</li></ul>|\n|503|false|`EC_SERVICE_COMPLETION_FAILURE`<ul><li>Service Completion Failure</li></ul>|\n|504|false|`EC_UNEXPECTED_RESPONSE_FROM_PEER`<ul><li>Unexpected Response From Peer</li></ul>|\n|507|false|`EC_MISTYPED_PARAMETER`<ul><li>Mistyped Parameter</li></ul>|\n|508|false|`EC_NOT_SUPPORTED_SERVICE`<ul><li>Not Supported Service</li></ul>|\n|509|false|`EC_DUPLICATED_INVOKE_ID`<ul><li>Duplicated Invoke Id</li></ul>|\n|1024|false|`EC_OR_APPCONTEXTNOTSUPPORTED`<ul><li>App Context Not Supported</li></ul>|\n|1025|false|`EC_OR_INVALIDDESTINATIONREFERENCE`<ul><li>Invalid Destination Reference</li></ul>|\n|1026|false|`EC_OR_INVALIDORIGINATINGREFERENCE`<ul><li>Invalid Originating Reference</li></ul>|\n|1027|false|`EC_OR_ENCAPSULATEDAC_NOTSUPPORTED`<ul><li>Encapsulated AC Not Supported</li></ul>|\n|1028|false|`EC_OR_TRANSPORTPROTECTIONNOTADEQUATE`<ul><li>Transport Protection Not Adequate</li></ul>|\n|1029|false|`EC_OR_NOREASONGIVEN`<ul><li>No Reason Given</li></ul>|\n|1030|false|`EC_OR_POTENTIALVERSIONINCOMPATIBILITY`<ul><li>Potential Version Incompatibility</li></ul>|\n|1031|false|`EC_OR_REMOTENODENOTREACHABLE`<ul><li>Remote Node Not Reachable</li></ul>|\n|1152|false|`EC_NNR_NOTRANSLATIONFORANADDRESSOFSUCHNATURE`<ul><li>No Translation For An Address Of Such Nature</li></ul>|\n|1153|false|`EC_NNR_NOTRANSLATIONFORTHISSPECIFICADDRESS`<ul><li>No Translation For This Specific Address</li></ul>|\n|1154|false|`EC_NNR_SUBSYSTEMCONGESTION`<ul><li>Subsystem Congestion</li></ul>|\n|1155|false|`EC_NNR_SUBSYSTEMFAILURE`<ul><li>Subsystem Failure</li></ul>|\n|1156|false|`EC_NNR_UNEQUIPPEDUSER`<ul><li>Unequipped User</li></ul>|\n|1157|false|`EC_NNR_MTPFAILURE`<ul><li>MTP Failure</li></ul>|\n|1158|false|`EC_NNR_NETWORKCONGESTION`<ul><li>The request had failed due to network congestion at the time of submission.</li></ul>|\n|1159|false|`EC_NNR_UNQUALIFIED`<ul><li>Unqualified</li></ul>|\n|1160|false|`EC_NNR_ERRORINMESSAGETRANSPORTXUDT`<ul><li>Error In Message Transport XUDT</li></ul>|\n|1161|false|`EC_NNR_ERRORINLOCALPROCESSINGXUDT`<ul><li>Error In Local Processing XUDT</li></ul>|\n|1162|false|`EC_NNR_DESTINATIONCANNOTPERFORMREASSEMBLYXUDT`<ul><li>Destination Cannot Perform Reassembly XUDT</li></ul>|\n|1163|false|`EC_NNR_SCCPFAILURE`<ul><li>SCCP Failure</li></ul>|\n|1164|false|`EC_NNR_HOPCOUNTERVIOLATION`<ul><li>Hop Counter Violation</li></ul>|\n|1165|false|`EC_NNR_SEGMENTATIONNOTSUPPORTED`<ul><li>Segmentation Not Supported</li></ul>|\n|1166|false|`EC_NNR_SEGMENTATIONFAILURE`<ul><li>Segmentation Failure</li></ul>|\n|1281|false|`EC_UA_USERSPECIFICREASON`<ul><li>User Specific Reason</li></ul>|\n|1282|false|`EC_UA_USERRESOURCELIMITATION`<ul><li>User Resource Limitation</li></ul>|\n|1283|false|`EC_UA_RESOURCEUNAVAILABLE`<ul><li>Resource Unavailable</li></ul>|\n|1284|false|`EC_UA_APPLICATIONPROCEDURECANCELLATION`<ul><li>Application Procedure Cancellation</li></ul>|\n|1536|false|`EC_PA_PROVIDERMALFUNCTION`<ul><li>Provider Malfunction</li></ul>|\n|1537|false|`EC_PA_SUPPORTINGDIALOGORTRANSACTIONREALEASED`<ul><li>Supporting Dialog Or Transaction Realeased</li></ul>|\n|1538|false|`EC_PA_RESSOURCELIMITATION`<ul><li>Resource Limitation</li></ul>|\n|1539|false|`EC_PA_MAINTENANCEACTIVITY`<ul><li>Maintenance Activity</li></ul>|\n|1540|false|`EC_PA_VERSIONINCOMPATIBILITY`<ul><li>Version Incompatibility</li></ul>|\n|1541|false|`EC_PA_ABNORMALMAPDIALOG`<ul><li>Abnormal Map Dialog</li></ul>|\n|1792|false|`EC_NC_ABNORMALEVENTDETECTEDBYPEER`<ul><li>Abnormal Event Detected By Peer</li></ul>|\n|1793|false|`EC_NC_RESPONSEREJECTEDBYPEER`<ul><li>Response Rejected By Peer</li></ul>|\n|1794|false|`EC_NC_ABNORMALEVENTRECEIVEDFROMPEER`<ul><li>Abnormal Event Received From Peer</li></ul>|\n|1795|false|`EC_NC_MESSAGECANNOTBEDELIVEREDTOPEER`<ul><li>Message Cannot Be Delivered To Peer</li></ul>|\n|1796|false|`EC_NC_PROVIDEROUTOFINVOKE`<ul><li>Provider Out Of Invoke</li></ul>|\n\n###USER_ERRORS (group id: 2) - general error codes\nUser error occurred.\n\n|Id|Permanent|Error|\n|-|-|-|\n|2049|true|`EC_IMSI_BLACKLISTED`<ul><li>IMSI blacklisted.</li></ul>|\n|2052|true|`EC_BLACKLISTED_DESTINATIONADDRESS`<ul><li>The destination number has been blacklisted either at the operator request or on your account via Infobip web portals - please remove the blacklist on your account via portal.infobip.com or contact Support for more information.</li></ul>|\n|2053|true|`EC_SOURCE_ADDRESS_BLACKLISTED`<ul><li>Source address is blacklisted on infobip account.</li></ul>|\n|4096|true|`EC_INVALID_PDU_FORMAT`<ul><li>Invalid PDU Format.</li></ul>|\n|4100|true|`EC_MESSAGE_CANCELED`<ul><li>The request was received, but has not been sent to the next instance within its validity period, and is expired with the appropriate error code EC_MESSAGE_CANCELED, or the same error code was reverted from the operator.</li></ul>|\n|4101|true|`EC_VALIDITYEXPIRED`<ul><li>The message was sent to the next instance, and has not been delivered within the message validity period, thus it is expired with the appropriate error code EC_VALIDITYEXPIRED or the error code was reverted from the operator.</li></ul>|\n|4102|true|`EC_NOTSUBMITTEDTOSMPPCHANNEL`<ul><li>Inbound SM can not be transfered via SMPP due the lack of SMPP conectivity.</li></ul>|\n|4103|true|`EC_DESTINATION_FLOODING`<ul><li>Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of messages sent to a single number.</li></ul>|\n|4104|true|`EC_DESTINATION_TXT_FLOODING`<ul><li>Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of identical messages sent to a single number.</li></ul>|\n\n\n###OPERATOR_ERRORS (group id: 3) - general error codes\nThe request has not been completed due to operator issues.\n\n|Id|Permanent|Error|\n|-|-|-|\n|10|true|`EC_BEARER_SERVICE_NOT_PROVISIONED`<ul><li>Bearer Service Not Provisioned</li></ul>|\n|20|false|`EC_SS_INCOMPATIBILITY`<ul><li>SS Incompatibility</li></ul>|\n|51|true|`EC_RESOURCE_LIMITATION`<ul><li>Indicates that invoked MAP operation could not be finished due the network congestion - this is an SS7 network congestion error on MAP protocol level.</li></ul>|\n|71|false|`EC_UNKNOWN_ALPHABET`<ul><li>Unknown Alphabet</li></ul>|\n|501|false|`EC_INVALID_RESPONSE_RECEIVED`<ul><li>Invalid Response Received</li></ul>|\n|2048|false|`EC_TIME_OUT`<ul><li>Time Out</li></ul>|\n|2050|true|`EC_DEST_ADDRESS_BLACKLISTED`<ul><li>The number was found blacklisted in the DND (Do Not Disturb) blacklist provided by the operator, or the same error code was reverted by the operator.</li></ul>|\n|2051|false|`EC_INVALIDMSCADDRESS`<ul><li>Text blacklisted</li></ul>|\n|4097|false|`EC_NOTSUBMITTEDTOGMSC`<ul><li>Not Submitted To GMSC</li></ul>|\n|4102|true|`EC_NOTSUBMITTEDTOSMPPCHANNEL`<ul><li>Not Submitted To Smpp Channel</li></ul>|\n\n\n##Voice error codes\n\n###OK (group id: 0) - voice error codes\nThe request has been completed successfully.\n\n|Id|Permanent|Error|\n|-|-|-|\n|5000|true|`VOICE_ANSWERED`<ul><li>The call has been received and answered.</li></ul>|\n|5001|true|`VOICE_ANSWERED_MACHINE`<ul><li>The call has been received and answered by a voice machine.</li></ul>|\n\n\n\n\n###HANDSET_ERRORS (group id: 1) - voice error codes\nThe request has not been completed due to handset related issues.\n\n|Id|Permanent|Error|\n|-|-|-|\n|5480|false|`EC_VOICE_ERROR_TEMPORARILY_NOT_AVAILABLE`<ul><li>Destination address is currently not available.</li></ul>|\n\n\n\n\n###OPERATOR_ERRORS (group id: 3) - voice error codes\nThe request has not been completed due to operator issues.\n\n|Id|Permanent|Error|\n|-|-|-|\n|5002|true|`EC_VOICE_USER_BUSY`<ul><li>The end user is currently busy to receive the Voice call.</li></ul>|\n|5003|true|`EC_VOICE_NO_ANSWER`<ul><li>The end user received a call but didn't answer it.</li></ul>|\n|5004|true|`EC_VOICE_ERROR_DOWNLOADING_FILE`<ul><li>The file specified in the HTTP request is inaccessible, and could not have been downloaded.</li></ul>|\n|5005|true|`EC_VOICE_ERROR_UNSUPPORTED_AUDIO_FORMAT`<ul><li>Format of the file specified  is not supported.</li></ul>|\n|5400|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>Received request was rejected because is wasn't formatted correctly.</li></ul>|\n|5403|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>Received request was rejected by the operator.</li></ul>|\n|5404|false|`EC_VOICE_ERROR_DESTINATION_NOT_FOUND`<ul><li>The server has definitive information that the user does not exist at the domain specified in the Request-URI.</li></ul>|\n|5407|false|`EC_VOICE_ERROR_PROXY_AUTHENTICATION_REQUIRED`<ul><li>The request requires user authentication on the operator's end.</li></ul>|\n|5408|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>There was no coverage for specific destination number or the end user couldn't be found on time during the call.</li></ul>|\n|5410|false|`EC_VOICE_ERROR_GONE`<ul><li>The user existed once, but operator doesn't support destination address anymore.</li></ul>|\n|5413|false|`EC_VOICE_ERROR_REQUEST_ENTITY_TOO_LARGE`<ul><li>Request entity-body is larger than the server is willing or able to process.</li></ul>|\n|5414|false|`EC_VOICE_ERROR_REQUEST_URI_TOO_LONG`<ul><li>The server is refusing to process the request because the Request-URI is longer than the server is willing to interpret (destination too long).</li></ul>|\n|5415|false|`EC_VOICE_UNSUPPORTED_MEDIA_TYPE`<ul><li>Format of the file is not supported.</li></ul>|\n|5484|false|`EC_VOICE_ERROR_ADDRESS_INCOMPLETE`<ul><li>Specified destination number is incomplete.</li></ul>|\n|5487|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>Request has terminated by a cancel button and end user refused to receive a voice call.</li></ul>|\n|5488|false|`EC_VOICE_ERROR_NOT_ACCEPTABLE_HERE`<ul><li>The format of the request is not acceptable on operator's end.</li></ul>|\n|5491|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>The format of the request is not supported on operator's end.</li></ul>|\n|5492|true|`EC_DUPLICATE_MESSAGE`<ul><li>The same voice message has already been sent to this destination address.</li></ul>|\n|5501|true|`EC_VOICE_NOT_IMPLEMENTED`<ul><li>Submitted request is not supported on operator's end.</li></ul>|\n|5503|true|`EC_VOICE_SERVICE_UNAVAILABLE`<ul><li>The service failed to complete the request. </li></ul>|\n\n\n\n\n\n##Push notification error codes\n\n###Registration error (group id: 1) - push notification error codes\nMessages not sent due to device registration problems (e.g. in cases of uninstalled applications).\n\n|Id|Permanent|Error|\n|-|-|-|\n|8001|true|`EC_DEVICE_APP_UNINSTALL`<ul><li>User has uninstalled the application on device or device cloud token expired.</li></ul>|\n|8002|true|`EC_GCM_MISMATCH_SENDER_ID`<ul><li>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 Settings pane. The sender ID is used to identify each app server that can send messages to the client app. Check your application build configuration.</li></ul>|\n|8003|true|`EC_NO_APPLICATION_FOUND`<ul><li>Application with provided ApplicationCode is not found at Infobip Push service. Check your message target parameters.</li></ul>|\n|8004|true|`EC_NO_REGISTRATION_ID_FOUND`<ul><li>Registration with provided PushRegistrationId does not exist or had been expired.</li></ul>|\n\n\n\n###Cloud error (group id: 3) - push notification error codes\nMessages not sent due to Clouds communication issues.\n\n|Id|Permanent|Error|\n|-|-|-|\n|8005|true|`EC_SYS_ERROR_FROM_CLOUD`<ul><li>Failed to send push notification. Cloud (FCM or APNS) responded with error while processing the request.</li></ul>|\n|8006|true|`EC_INVALID_GCM_AUTH_DATA`<ul><li>Invalid cloud authentication data (Server Key). FCM responded with status 401 (Unauthorized). Check your Application configuration for Android at Infobip Portal.</li></ul>|\n|8007|true|`EC_INVALID_APNS_CERT`<ul><li>Invalid certificate for APNS. Check your Application configuration for iOS at Infobip Portal.</li></ul>|\n|8008|true|`EC_APPLICATION_CLOUD_TYPE_DISABLED`<ul><li>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 at Infobip Portal.</li></ul>|\n|8009|true|`EC_PUSH_INTERNAL_REQUEST_ERROR`<ul><li>Internal error. Please try again later and if problem persists, contact Support for further assistance.</li></ul>|\n|8010|true|`EC_INVALID_PUSH_PAYLOAD`<ul><li>Invalid push payload data. Please contact Support for further assistance.</li></ul>|\n|8011|true|`EC_PUSH_INTERNAL_GW_ERROR`<ul><li>Internal error. Please try again later and if problem persists, contact Support for further assistance.</li></ul>|\n|8012|true|`EC_PUSH_CLOUD_TEMP_UNAVAILABLE`<ul><li>Push Cloud (FCM or APNS) is temporary unavailable. Message is pending in retry.</li></ul>|\n\n\n\n\n\n##Email error codes\n\n###Dropped (group id: 1) - email error codes\nThe request has not been completed successfully as emails were dropped by the mail delivery system on end-user's side.\n\n|Id|Permanent|Error|\n|-|-|-|\n|6001|true|`EC_EMAIL_BLACKLISTED`<ul><li>Sender name used is a part of real-time database which consists of forbidden domains/sender names/IPs that are categorized as spam-friendly.</li></ul>|\n|6002|true|`EC_EMAIL_SPAM_CONTENT`<ul><li>Email's content/sender name/domain has been recognized/categorized as spam.</li></ul>|\n|6003|true|`EC_UNSUBSCRIBED_EMAIL_ADDRESS`<ul><li>End-user has unsubscribed from receiving emails from the domain/sender name used.</li></ul>|\n|6004|true|`EC_BOUNCED_EMAIL_ADDRESS`<ul><li>Confirmation that email cannot be delivered as bounce message was reverted on the previous attempt.</li></ul>|\n|6005|true|`EC_EMAIL_DROPPED`<ul><li>Recipient had previously bounced, unsubscribed, or complained of spam so we will not attempt delivery and message will be dropped.</li></ul>|\n\n\n\n###Bounced (group id: 2) - email error codes\nThe request has not been completed successfully and we received NDR (Non-delivery receipt).\n\n|Id|Permanent|Error|\n|-|-|-|\n|6006|true|`EC_INVALID_EMAIL_ADDRESS`<ul><li>Sender name is not a valid one - Either invalid characters or either invalid domain was used.</li></ul>|\n|6007|false|`EC_MAILBOX_TEMPORARILY_UNAVAILABLE`<ul><li>Server on which end-user's mailbox is hosted might having intermittent issues or smtp route/port is not available.</li></ul>|\n|6008|false|`EC_DEFERRED_DUE_TO_INSUFFICIENT_STORAGE`<ul><li>End-user's mailbox is hosted on server that does not have enough to storage to process/store the email.</li></ul>|\n|6009|true|`EC_MAILBOX_UNAVAILABLE`<ul><li>End-user's mailbox might have restricted access or simply does not exist on the server.</li></ul>|\n|6010|true|`EC_STORAGE_LIMIT_EXCEEDED`<ul><li>End-user's mailbox has reached its full capacity defined on the server.</li></ul>|\n|6011|false|`EC_SOFT_BOUNCE`<ul><li>We received bounced message (Non-delivery receipt) - Possible reasons: Mailbox is full (over quota); Recipient email server is down or offline; Email message is too large.</li></ul>|\n|6012|true|`EC_HARD_BOUNCE`<ul><li>We received bounced message (Non-delivery receipt) - Possible reasons: Recipient email address does not exist; Domain name does not exist; Recipient email server has completely blocked delivery.</li></ul>|\n\n\n\n\n###System Error (group id: 3) - email error codes\nThe request has not been completed successfully due to system-related errors.\n\n|Id|Permanent|Error|\n|-|-|-|\n|6013|false|`EC_TEMPORARY_SENDING_ERROR`<ul><li>Possible throttling on end-user's' side due to server configuration (limited amount of emails within certain period of time).</li></ul>|\n|6014|true|`EC_PERMANENT_SENDING_ERROR`<ul><li>Most commonly the issue lies within the domain used as sender as it probably was not registered yet.</li></ul>|\n|6015|true|`EC_GATEWAY_ERROR`<ul><li>Indicates that email failed due to configuration error or error that is not recognized/defined.</li></ul>|\n\n\n\n\n##Chat error codes\n(Facebook messenger, Line, Viber)\n\n###Client error (group id: 1) - chat error codes\nThe request has not been completed successfully due to application misconfiguration or a bad/invalid request issued by client.\n\n|Id|Permanent|Error|\n|-|-|-|\n|7001|true|`EC_UNKNOWN_APPLICATION`<ul><li>Application used to send the message does not exist. Make sure you have created the application and that you are using a valid application key.</li></ul>|\n|7002|true|`EC_UNKNOWN_USER`<ul><li>Receiving user does not exists. Check that the user has subscribed to the service and that you are using the correct user key.</li></ul>|\n|7003|true|`EC_BLOCKED_USER`<ul><li>Receiving user has blocked communication.</li></ul>|\n|7004|true|`EC_UNAUTHORIZED_ACCESS`<ul><li>Invalid or unrecognized service access credentials. Make sure that you are using the correct access credentials issued by the service provider.</li></ul>|\n|7005|true|`EC_FORBIDDEN_ACCESS`<ul><li>Authentication was recognized, but not allowed. Check that your application is allowed to send messages, and that it is published or approved by the provider.</li></ul>|\n|7102|true|`EC_PHONE_MATCHING_DISABLED`<ul><li>Facebook's Phone matching option not enabled for application. Check out the Facebook documentation to see if your application is eligible for this paid feature.</li></ul>|\n|7201|true|`EC_UNSUPPORTED_DEVICE`<ul><li>Receiving user does not have a device that can receive this type of message.</li></ul>|\n\n\n###Provider error (group id: 2) - chat error codes\nThe request has not been completed successfully due to a service provider error.\n\n|Id|Permanent|Error|\n|-|-|-|\n|7050|false|`EC_PROVIDER_INTERNAL_ERROR`<ul><li>Internal service provider error.</li></ul>|\n|7051|false|`EC_PROVIDER_TIMEOUT`<ul><li>Connection to service provider timed out.</li></ul>|\n\n\n###System Error (group id: 3) - chat error codes\nThe request has not been completed successfully due to a system-related error.\n\n|Id|Permanent|Error|\n|-|-|-|\n|7080|true|`EC_INTERNAL_ERROR`<ul><li>Internal error in Infobip platform. Contact Support to resolve the issue.</li></ul>|\n|7081|true|`EC_CONFIGURATION_ERROR`<ul><li>Internal configuration error. Contact Support to resolve the issue.</li></ul>|\n|7280|true|`EC_DUPLICATE_REQUEST`<ul><li>Identical message was already sent to the user recently.</li></ul>|\n|7281|true|`EC_BAD_ORIGIN`<ul><li>Request was sent from an unapproved origin. Contact Support to resolve the issue.</li></ul>|","excerpt":"List of API status and error codes.","slug":"response-codes","type":"basic","title":"Response status and error codes"}

Response status and error codes

List of API status and error codes.

While 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 in case you are looking for a resolution of the problem. [block:callout] { "type": "warning", "body": "Use page **Search field** or **Find on page** web browser feature to quickly locate the code name you are looking for.", "title": "Find code name" } [/block] Code lists: * [HTTP status codes](#http-status-codes) * [API Status codes](#api-status-codes) * [General status codes](#section-general-status-codes) * [Voice status codes](#section-voice-status-codes) * [Push notification status codes](#section-push-notifications-status-codes) * [Error codes](#error-codes) * [General error codes](#section-general-error-codes) * [Voice error codes](#section-voice-error-codes) * [Push notification error codes](#section-push-notification-error-codes) * [Email error codes](#section-email-error-codes) * [Chat error codes](#section-chat-error-codes) [block:api-header] { "type": "basic", "title": "HTTP status codes" } [/block] Every HTTP transaction has a status code sent back by the server to define how the server handled the transaction. Most common statuses you may have encountered are `200 OK` and `404 Not Found` [Learn more about HTTP status codes here](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) [block:api-header] { "type": "basic", "title": "API Status codes" } [/block] Besides standard HTTP status code, status object may be returned as part of the API response message, delivery report or message log. Status object example: [block:code] { "codes": [ { "code": "{ \n \"groupId\":3,\n \"groupName\":\"DELIVERED\",\n \"id\":5,\n \"name\":\"DELIVERED_TO_HANDSET\",\n \"description\":\"Message delivered to handset\"\n}", "language": "json" } ] } [/block] ##General status codes ###PENDING (group id: 1) - general status codes Message has been processed and sent to the next instance i.e. mobile operator. |Id|Status| |-|-| |3|`PENDING_WAITING_DELIVERY`<ul><li>Message has been processed and sent to the next instance i.e. mobile operator with request acknowledgment from their platform. Delivery report has not yet been received, and is awaited thus the status is still pending.</li></ul>| |7|`PENDING_ENROUTE`<ul><li>Message has been processed and sent to the next instance i.e. mobile operator.</li></ul>| |26|`PENDING_ACCEPTED`<ul><li>Message has been accepted and processed, and is ready to be sent to the next instance i.e. operator.</li></ul>| ###UNDELIVERABLE (group id: 2) - general status codes Message has not been delivered. |Id|Status| |-|-| |4|`UNDELIVERABLE_REJECTED_OPERATOR`<ul><li>Message has been sent to the operator, whereas the request was rejected, or a delivery report with status "REJECTED" was reverted.</li></ul>| |9|`UNDELIVERABLE_NOT_DELIVERED`<ul><li>Message has been sent to the operator, but has failed to delivery, since a delivery report with status "UNDELIVERED" was reverted from the operator.</li></ul>| ###DELIVERED (group id: 3) - general status codes Message has successfully been processed and delivered. |Id|Status| |-|-| |2|`DELIVERED_TO_OPERATOR`<ul><li>Message has been successfully sent and delivered to the operator.</li></ul>| |5|`DELIVERED_TO_HANDSET`<ul><li>Message has been successfully processed and delivered to recipient.</li></ul>| ###EXPIRED (group id: 4) - general status codes Message has been sent, and has either expired due to being pending past its validity period (our platform default is 48 hours), or the delivery report from the operator has reverted the expired as a final status. |Id|Status| |-|-| |15|`EXPIRED_EXPIRED`<ul><li>The message was received and sent to the operator, however it has been pending until the validity period has expired, or the operator returned EXPIRED status in the meantime.</li></ul>| |29|`EXPIRED_DLR_UNKNOWN`<ul><li>The message has been received and forwarded to the operator for delivery, however the delivery report from the operator has not been formatted correctly, or has not been recognized as valid.</li></ul>| ###REJECTED (group id: 5) - general status codes Message has been received, but has either been rejected by Infobip, or the operator has reverted Rejected as final status. |Id|Status| |-|-| |6|`REJECTED_NETWORK`<ul><li>Message has been received, but the network is either out of our coverage or not setup on your account. Your account manager can inform you on the coverage status or setup the network in question.</li></ul>| |8|`REJECTED_PREFIX_MISSING`<ul><li>Message has been received, but has been rejected as the number is not recognized due to either incorrect number prefix or number length. This information is different for each network and is regularly updated.</li></ul>| |10|`REJECTED_DND`<ul><li>Message has been received, and rejected due to the user being subscribed to DND (Do Not Disturb) services, disabling any service traffic to their number.</li></ul>| |11|`REJECTED_SOURCE`<ul><li>Your account is set to accept only registered sender ID-s while the sender ID defined in the request has not been registered on your account.</li></ul>| |12|`REJECTED_NOT_ENOUGH_CREDITS`<ul><li>Your account is out of credits for further submission - please top up your account. For further assistance in topping up or applying for online account topup service you may contact your account manager.</li></ul>| |13|`REJECTED_SENDER`<ul><li>The sender ID has been blacklisted on your account via Infobip webites portals - please remove the blacklist on your account or contact Support for further assistance.</li></ul>| |14|`REJECTED_DESTINATION`<ul><li>The destination number has been blacklisted either at the operator request or on your account via Infobip webites portals - please remove the blacklist on your account via portal.infobip.com or contact Support for more information.</li></ul>| |17|`REJECTED_PREPAID_PACKAGE_EXPIRED`<ul><li>Account credits have been expired past their validity period - please topup your subaccount with credits to extend the validity period.</li></ul>| |18|`REJECTED_DESTINATION_NOT_REGISTERED`<ul><li>Your account has been setup for submission only to a single number for testing purposes - kindly contact your manager to remove the limitation.</li></ul>| |19|`REJECTED_ROUTE_NOT_AVAILABLE`<ul><li>Mesage has been received on the system, however your account has not been setup to send messages i.e. no routes on your account are available for further submission. Your account manager will be able to setup your account based on your preference.</li></ul>| |20|`REJECTED_FLOODING_FILTER`<ul><li>Message has been rejected due to a anti-flooding mechanism. By default, a single number can only receive 20 varied messages and 6 identical messages per hour. If there is a requirement, the limitation can be extended per account on request to your account manager.</li></ul>| |21|`REJECTED_SYSTEM_ERROR`<ul><li>The request has been rejected due to an expected system system error, please retry submission or contact our technical support team for more details.</li></ul>| |23|`REJECTED_DUPLICATE_MESSAGE_ID`<ul><li>The request has been rejected due to a duplicate message ID specified in the submit request, while message ID-s should be a unique value. For more information, please revisit https://dev.infobip.com/v1/docs/bulk-id-and-message-id.</li></ul>| |24|`REJECTED_INVALID_UDH`<ul><li>Message has been received, while 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 feel free to visit the below articles or contact our Support team for clarification.<br />https://en.wikipedia.org/wiki/User_Data_Header<br />https://en.wikipedia.org/wiki/Concatenated_SMS</li></ul>| |25|`REJECTED_MESSAGE_TOO_LONG`<ul><li>Message has been received, but the total message length is more than 25 parts or message text which exceeds 4000 bytes as per our system limitation.</li></ul>| |51|`MISSING_TO`<ul><li>The request has been received, however the "to" parameter has not been set or it is empty, i.e. there must be valid recipients to send the message.</li></ul>| ##Voice status codes ###REJECTED (group id: 5) - voice status codes Message has been received, but has either been rejected by Infobip, or the operator has reverted the rejected as final status. |Id|Status| |-|-| |52|`REJECTED_INVALID_DESTINATION`<ul><li>The request has been received, however the destination is invalid - the number prefix is not correct as it does not match a valid number prefix by any mobile operator. Number length is also taken into consideration in verifying number number validity.</li></ul>| |53|`REJECTED_INVALID_AUDIO_FILE_URL`<ul><li>The URL of audio file is invalid and could not be read properly.</li></ul>| |54|`REJECTED_UNSUPPORTED_LANGUAGE`<ul><li>The language submitted within the request is not supported and request couldn't be processed correctly.</li></ul>| |55|`REJECTED_MESSAGE_IS_EMPTY`<ul><li>Native to Voice services, this status is returned in case there is no text sent in your Voice message request.</li></ul>| |56|`REJECTED_INVALID_NOTIFY_URL`<ul><li>Native to Voice services, this status is returned in case the notifyUrl parameter is not formatter properly. Please revisit the documentation [here](/docs/fully-featured-voice-messages).</li></ul>| |57|`REJECTED_INVALID_NOTIFY_CONTENT_TYPE`<ul><li>Native to Voice services, this status is returned in case the notifyContentType parameter is not formatter properly. Please revisit the documentation on [here](/docs/fully-featured-voice-messages).</li></ul>| |58|`REJECTED_INVALID_DTMF_SIGN`<ul><li>Defined value for repeating message is invalid and must be positive number.</li></ul>| |59|`REJECTED_INVALID_DTMF_TIMEOUT`<ul><li>Defined value for the waiting period is invalid and must be positive number.</li></ul>| |60|`REJECTED_INVALID_RING_TIMEOUT`<ul><li>Defined value for duration of call is invalid and must be positive number.</li></ul>| |61|`REJECTED_INVALID_CALL_TIMEOUT`<ul><li>Defined value for total period of call is invalid and must be positive number.</li></ul>| |62|`REJECTED_INVALID_MACHINE_DETECTION`<ul><li>The action which attempts to detect answering machines at the beginning of the call is invalid.</li></ul>| |63|`REJECTED_INVALID_ACTIONS`<ul><li>Actions submitted in HTTP API request are invalid.</li></ul>| |64|`REJECTED_INVALID_ACTION_GROUPS`<ul><li>Action groups submitted in HTTP API request are invalid.</li></ul>| ##Push notifications status codes ###UNDELIVERABLE (group id: 2) - push notifications status codes Message has not been delivered. |Id|Status| |-|-| |66|`UNDELIVERABLE_NO_DESTINATION`<ul><li>The status occurs when in 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 by some "tag" which doesn't exist at any of instances of requested ApplicationCode, then it will return "no destinations" as we couldn't find in our database anyone which would satisfy requested conditions. In another example, you may want to target all application instances (devices) with Android OS. In this case you have to use CloudType: `GCM` and API internally will resolve all destinations and will send message to all android devices linked to requested ApplicationCode. You also can check you valid registrations by filtering in our [web interface](https://portal.infobip.com/subscribers/subscribers). More information about User Data you can find at our SDK pages: [iOS ](https://github.com/infobip/mobile-messaging-sdk-ios/wiki/User-data)and [Android](https://github.com/infobip/mobile-messaging-sdk-android/wiki/User-data)</li></ul>| ###REJECTED (group id: 5) - push notifications status codes Message has been received, but has either been rejected by Infobip, or the operator has reverted the rejected as final status. |Id|Status| |-|-| |65|`REJECTED_NO_APPLICATION `<ul><li>The status occurs when in Push API call is used invalid or not existent ApplicationCode in field `from`. Each application profile has it's own unique ApplicationCode. ApplicationCode is used in SDK as key identifier for Applicatoin installed on end user device being able to communicate with our platform. For the pair device + installed app pushRegistrationId is issued and it is uniquely linked to ApplicactionCode. It's possible to get all available applications [here](/docs/push-application-get). Or check configuration [here](/push/applications).</li></ul>| [block:api-header] { "type": "basic", "title": "Error codes" } [/block] Error object can be returned as part of the send message response or Delivery report response. Error object example: [block:code] { "codes": [ { "code": "{ \n \"groupId\":0,\n \"groupName\":\"OK\",\n \"id\":0,\n \"name\":\"NO_ERROR\",\n \"description\":\"No Error\",\n \"permanent\":false\n}", "language": "json" } ] } [/block] ##General error codes ###OK (group id: 0) - general error codes The request has been completed successfully. |Id|Permanent|Error| |-|-|-| |0|false|`NO_ERROR`<ul><li>There is no error description provided. Mostly returned for successful delivery or when error code was not returned by the operator.</li></ul>| ###HANDSET_ERRORS (group id: 1) - general error codes The request has not been completed due to handset related issues. |Id|Permanent|Error| |-|-|-| |1|true|`EC_UNKNOWN_SUBSCRIBER`<ul><li>The number does not exist or it has not been assigned to any active subscriber in the operator's user database.</li></ul>| |5|false|`EC_UNIDENTIFIED_SUBSCRIBER`<ul><li>Unidentified Subscriber</li></ul>| |6|false|`EC_ABSENT_SUBSCRIBER_SM`<ul><li>The subscriber is detected unavailable, as there was no paging response from the handset. This is often due to the handset being switched off or in low signal area. Applies to MAP protocol version 3.</li></ul>| |8|false|`EC_ROAMING_NOT_ALLOWED`<ul><li>The subscriber is currently in roaming at another country or other operator's infrastructure - roaming delivery is not guaranteed due to lack of roaming agreements between many different operator.</li></ul>| |9|true|`EC_ILLEGAL_SUBSCRIBER`<ul><li>Illegal Subscriber</li></ul>| |11|true|`EC_TELESERVICE_NOT_PROVISIONED`<ul><li>The subscriber's mobile service has been suspended by the operator.</li></ul>| |12|true|`EC_ILLEGAL_EQUIPMENT`<ul><li>Illegal Equipment</li></ul>| |13|false|`EC_CALL_BARRED`<ul><li>The subscriber is set to DND (Do Not Disturb) service, opting out of receiving any service traffic to their number.</li></ul>| |21|false|`EC_FACILITY_NOT_SUPPORTED`<ul><li>Facility Not Supported</li></ul>| |27|false|`EC_ABSENT_SUBSCRIBER`<ul><li>The subscriber is offline in the network, as confirmed by the handset's paging response. This is often due to the handset being switched off.</li></ul>| |31|false|`EC_SUBSCRIBER_BUSY_FOR_MT_SMS`<ul><li>Subscriber Busy For Mt SMS</li></ul>| |32|false|`EC_SM_DELIVERY_FAILURE`<ul><li>SM Delivery Failure</li></ul>| |33|false|`EC_MESSAGE_WAITING_LIST_FULL`<ul><li>Message Waiting List Full</li></ul>| |34|false|`EC_SYSTEM_FAILURE`<ul><li>System Failure</li></ul>| |35|false|`EC_DATA_MISSING`<ul><li>Data Missing</li></ul>| |36|false|`EC_UNEXPECTED_DATA_VALUE`<ul><li>Unexpected Data Value</li></ul>| |255|false|`EC_UNKNOWN_ERROR`<ul><li>Unknown Error</li></ul>| |256|false|`EC_SM_DF_MEMORYCAPACITYEXCEEDED`<ul><li>SM DF Memory Capacity Exceeded</li></ul>| |257|false|`EC_SM_DF_EQUIPMENTPROTOCOLERROR`<ul><li>SM DF Equipment Protocol Error</li></ul>| |258|false|`EC_SM_DF_EQUIPMENTNOTSM_EQUIPPED`<ul><li>SM DF Equipment Not SM Equipped</li></ul>| |259|false|`EC_SM_DF_UNKNOWNSERVICECENTRE`<ul><li>SM DF Unknown Service Centre</li></ul>| |260|false|`EC_SM_DF_SC_CONGESTION`<ul><li>SM DF Sc Congestion</li></ul>| |261|false|`EC_SM_DF_INVALIDSME_ADDRESS`<ul><li>SM DF InvalidSME Address</li></ul>| |262|false|`EC_SM_DF_SUBSCRIBERNOTSC_SUBSCRIBER`<ul><li>SM DF Subscribernotsc Subscriber</li></ul>| |500|false|`EC_PROVIDER_GENERAL_ERROR`<ul><li>Provider General Error</li></ul>| |502|false|`EC_NO_RESPONSE`<ul><li>The message has been successfully processed and forwarded to the operator, but no response was returned from the operator upon message submit request, or such error was reverted by the operator. The error also applies to similar errors on SS7 network level.</li></ul>| |503|false|`EC_SERVICE_COMPLETION_FAILURE`<ul><li>Service Completion Failure</li></ul>| |504|false|`EC_UNEXPECTED_RESPONSE_FROM_PEER`<ul><li>Unexpected Response From Peer</li></ul>| |507|false|`EC_MISTYPED_PARAMETER`<ul><li>Mistyped Parameter</li></ul>| |508|false|`EC_NOT_SUPPORTED_SERVICE`<ul><li>Not Supported Service</li></ul>| |509|false|`EC_DUPLICATED_INVOKE_ID`<ul><li>Duplicated Invoke Id</li></ul>| |1024|false|`EC_OR_APPCONTEXTNOTSUPPORTED`<ul><li>App Context Not Supported</li></ul>| |1025|false|`EC_OR_INVALIDDESTINATIONREFERENCE`<ul><li>Invalid Destination Reference</li></ul>| |1026|false|`EC_OR_INVALIDORIGINATINGREFERENCE`<ul><li>Invalid Originating Reference</li></ul>| |1027|false|`EC_OR_ENCAPSULATEDAC_NOTSUPPORTED`<ul><li>Encapsulated AC Not Supported</li></ul>| |1028|false|`EC_OR_TRANSPORTPROTECTIONNOTADEQUATE`<ul><li>Transport Protection Not Adequate</li></ul>| |1029|false|`EC_OR_NOREASONGIVEN`<ul><li>No Reason Given</li></ul>| |1030|false|`EC_OR_POTENTIALVERSIONINCOMPATIBILITY`<ul><li>Potential Version Incompatibility</li></ul>| |1031|false|`EC_OR_REMOTENODENOTREACHABLE`<ul><li>Remote Node Not Reachable</li></ul>| |1152|false|`EC_NNR_NOTRANSLATIONFORANADDRESSOFSUCHNATURE`<ul><li>No Translation For An Address Of Such Nature</li></ul>| |1153|false|`EC_NNR_NOTRANSLATIONFORTHISSPECIFICADDRESS`<ul><li>No Translation For This Specific Address</li></ul>| |1154|false|`EC_NNR_SUBSYSTEMCONGESTION`<ul><li>Subsystem Congestion</li></ul>| |1155|false|`EC_NNR_SUBSYSTEMFAILURE`<ul><li>Subsystem Failure</li></ul>| |1156|false|`EC_NNR_UNEQUIPPEDUSER`<ul><li>Unequipped User</li></ul>| |1157|false|`EC_NNR_MTPFAILURE`<ul><li>MTP Failure</li></ul>| |1158|false|`EC_NNR_NETWORKCONGESTION`<ul><li>The request had failed due to network congestion at the time of submission.</li></ul>| |1159|false|`EC_NNR_UNQUALIFIED`<ul><li>Unqualified</li></ul>| |1160|false|`EC_NNR_ERRORINMESSAGETRANSPORTXUDT`<ul><li>Error In Message Transport XUDT</li></ul>| |1161|false|`EC_NNR_ERRORINLOCALPROCESSINGXUDT`<ul><li>Error In Local Processing XUDT</li></ul>| |1162|false|`EC_NNR_DESTINATIONCANNOTPERFORMREASSEMBLYXUDT`<ul><li>Destination Cannot Perform Reassembly XUDT</li></ul>| |1163|false|`EC_NNR_SCCPFAILURE`<ul><li>SCCP Failure</li></ul>| |1164|false|`EC_NNR_HOPCOUNTERVIOLATION`<ul><li>Hop Counter Violation</li></ul>| |1165|false|`EC_NNR_SEGMENTATIONNOTSUPPORTED`<ul><li>Segmentation Not Supported</li></ul>| |1166|false|`EC_NNR_SEGMENTATIONFAILURE`<ul><li>Segmentation Failure</li></ul>| |1281|false|`EC_UA_USERSPECIFICREASON`<ul><li>User Specific Reason</li></ul>| |1282|false|`EC_UA_USERRESOURCELIMITATION`<ul><li>User Resource Limitation</li></ul>| |1283|false|`EC_UA_RESOURCEUNAVAILABLE`<ul><li>Resource Unavailable</li></ul>| |1284|false|`EC_UA_APPLICATIONPROCEDURECANCELLATION`<ul><li>Application Procedure Cancellation</li></ul>| |1536|false|`EC_PA_PROVIDERMALFUNCTION`<ul><li>Provider Malfunction</li></ul>| |1537|false|`EC_PA_SUPPORTINGDIALOGORTRANSACTIONREALEASED`<ul><li>Supporting Dialog Or Transaction Realeased</li></ul>| |1538|false|`EC_PA_RESSOURCELIMITATION`<ul><li>Resource Limitation</li></ul>| |1539|false|`EC_PA_MAINTENANCEACTIVITY`<ul><li>Maintenance Activity</li></ul>| |1540|false|`EC_PA_VERSIONINCOMPATIBILITY`<ul><li>Version Incompatibility</li></ul>| |1541|false|`EC_PA_ABNORMALMAPDIALOG`<ul><li>Abnormal Map Dialog</li></ul>| |1792|false|`EC_NC_ABNORMALEVENTDETECTEDBYPEER`<ul><li>Abnormal Event Detected By Peer</li></ul>| |1793|false|`EC_NC_RESPONSEREJECTEDBYPEER`<ul><li>Response Rejected By Peer</li></ul>| |1794|false|`EC_NC_ABNORMALEVENTRECEIVEDFROMPEER`<ul><li>Abnormal Event Received From Peer</li></ul>| |1795|false|`EC_NC_MESSAGECANNOTBEDELIVEREDTOPEER`<ul><li>Message Cannot Be Delivered To Peer</li></ul>| |1796|false|`EC_NC_PROVIDEROUTOFINVOKE`<ul><li>Provider Out Of Invoke</li></ul>| ###USER_ERRORS (group id: 2) - general error codes User error occurred. |Id|Permanent|Error| |-|-|-| |2049|true|`EC_IMSI_BLACKLISTED`<ul><li>IMSI blacklisted.</li></ul>| |2052|true|`EC_BLACKLISTED_DESTINATIONADDRESS`<ul><li>The destination number has been blacklisted either at the operator request or on your account via Infobip web portals - please remove the blacklist on your account via portal.infobip.com or contact Support for more information.</li></ul>| |2053|true|`EC_SOURCE_ADDRESS_BLACKLISTED`<ul><li>Source address is blacklisted on infobip account.</li></ul>| |4096|true|`EC_INVALID_PDU_FORMAT`<ul><li>Invalid PDU Format.</li></ul>| |4100|true|`EC_MESSAGE_CANCELED`<ul><li>The request was received, but has not been sent to the next instance within its validity period, and is expired with the appropriate error code EC_MESSAGE_CANCELED, or the same error code was reverted from the operator.</li></ul>| |4101|true|`EC_VALIDITYEXPIRED`<ul><li>The message was sent to the next instance, and has not been delivered within the message validity period, thus it is expired with the appropriate error code EC_VALIDITYEXPIRED or the error code was reverted from the operator.</li></ul>| |4102|true|`EC_NOTSUBMITTEDTOSMPPCHANNEL`<ul><li>Inbound SM can not be transfered via SMPP due the lack of SMPP conectivity.</li></ul>| |4103|true|`EC_DESTINATION_FLOODING`<ul><li>Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of messages sent to a single number.</li></ul>| |4104|true|`EC_DESTINATION_TXT_FLOODING`<ul><li>Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of identical messages sent to a single number.</li></ul>| ###OPERATOR_ERRORS (group id: 3) - general error codes The request has not been completed due to operator issues. |Id|Permanent|Error| |-|-|-| |10|true|`EC_BEARER_SERVICE_NOT_PROVISIONED`<ul><li>Bearer Service Not Provisioned</li></ul>| |20|false|`EC_SS_INCOMPATIBILITY`<ul><li>SS Incompatibility</li></ul>| |51|true|`EC_RESOURCE_LIMITATION`<ul><li>Indicates that invoked MAP operation could not be finished due the network congestion - this is an SS7 network congestion error on MAP protocol level.</li></ul>| |71|false|`EC_UNKNOWN_ALPHABET`<ul><li>Unknown Alphabet</li></ul>| |501|false|`EC_INVALID_RESPONSE_RECEIVED`<ul><li>Invalid Response Received</li></ul>| |2048|false|`EC_TIME_OUT`<ul><li>Time Out</li></ul>| |2050|true|`EC_DEST_ADDRESS_BLACKLISTED`<ul><li>The number was found blacklisted in the DND (Do Not Disturb) blacklist provided by the operator, or the same error code was reverted by the operator.</li></ul>| |2051|false|`EC_INVALIDMSCADDRESS`<ul><li>Text blacklisted</li></ul>| |4097|false|`EC_NOTSUBMITTEDTOGMSC`<ul><li>Not Submitted To GMSC</li></ul>| |4102|true|`EC_NOTSUBMITTEDTOSMPPCHANNEL`<ul><li>Not Submitted To Smpp Channel</li></ul>| ##Voice error codes ###OK (group id: 0) - voice error codes The request has been completed successfully. |Id|Permanent|Error| |-|-|-| |5000|true|`VOICE_ANSWERED`<ul><li>The call has been received and answered.</li></ul>| |5001|true|`VOICE_ANSWERED_MACHINE`<ul><li>The call has been received and answered by a voice machine.</li></ul>| ###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`<ul><li>Destination address is currently not available.</li></ul>| ###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`<ul><li>The end user is currently busy to receive the Voice call.</li></ul>| |5003|true|`EC_VOICE_NO_ANSWER`<ul><li>The end user received a call but didn't answer it.</li></ul>| |5004|true|`EC_VOICE_ERROR_DOWNLOADING_FILE`<ul><li>The file specified in the HTTP request is inaccessible, and could not have been downloaded.</li></ul>| |5005|true|`EC_VOICE_ERROR_UNSUPPORTED_AUDIO_FORMAT`<ul><li>Format of the file specified is not supported.</li></ul>| |5400|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>Received request was rejected because is wasn't formatted correctly.</li></ul>| |5403|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>Received request was rejected by the operator.</li></ul>| |5404|false|`EC_VOICE_ERROR_DESTINATION_NOT_FOUND`<ul><li>The server has definitive information that the user does not exist at the domain specified in the Request-URI.</li></ul>| |5407|false|`EC_VOICE_ERROR_PROXY_AUTHENTICATION_REQUIRED`<ul><li>The request requires user authentication on the operator's end.</li></ul>| |5408|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>There was no coverage for specific destination number or the end user couldn't be found on time during the call.</li></ul>| |5410|false|`EC_VOICE_ERROR_GONE`<ul><li>The user existed once, but operator doesn't support destination address anymore.</li></ul>| |5413|false|`EC_VOICE_ERROR_REQUEST_ENTITY_TOO_LARGE`<ul><li>Request entity-body is larger than the server is willing or able to process.</li></ul>| |5414|false|`EC_VOICE_ERROR_REQUEST_URI_TOO_LONG`<ul><li>The server is refusing to process the request because the Request-URI is longer than the server is willing to interpret (destination too long).</li></ul>| |5415|false|`EC_VOICE_UNSUPPORTED_MEDIA_TYPE`<ul><li>Format of the file is not supported.</li></ul>| |5484|false|`EC_VOICE_ERROR_ADDRESS_INCOMPLETE`<ul><li>Specified destination number is incomplete.</li></ul>| |5487|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>Request has terminated by a cancel button and end user refused to receive a voice call.</li></ul>| |5488|false|`EC_VOICE_ERROR_NOT_ACCEPTABLE_HERE`<ul><li>The format of the request is not acceptable on operator's end.</li></ul>| |5491|false|`EC_VOICE_ERROR_BAD_REQUEST`<ul><li>The format of the request is not supported on operator's end.</li></ul>| |5492|true|`EC_DUPLICATE_MESSAGE`<ul><li>The same voice message has already been sent to this destination address.</li></ul>| |5501|true|`EC_VOICE_NOT_IMPLEMENTED`<ul><li>Submitted request is not supported on operator's end.</li></ul>| |5503|true|`EC_VOICE_SERVICE_UNAVAILABLE`<ul><li>The service failed to complete the request. </li></ul>| ##Push notification error codes ###Registration error (group id: 1) - push notification error codes Messages not sent due to device registration problems (e.g. in cases of uninstalled applications). |Id|Permanent|Error| |-|-|-| |8001|true|`EC_DEVICE_APP_UNINSTALL`<ul><li>User has uninstalled the application on device or device cloud token expired.</li></ul>| |8002|true|`EC_GCM_MISMATCH_SENDER_ID`<ul><li>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 Settings pane. The sender ID is used to identify each app server that can send messages to the client app. Check your application build configuration.</li></ul>| |8003|true|`EC_NO_APPLICATION_FOUND`<ul><li>Application with provided ApplicationCode is not found at Infobip Push service. Check your message target parameters.</li></ul>| |8004|true|`EC_NO_REGISTRATION_ID_FOUND`<ul><li>Registration with provided PushRegistrationId does not exist or had been expired.</li></ul>| ###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`<ul><li>Failed to send push notification. Cloud (FCM or APNS) responded with error while processing the request.</li></ul>| |8006|true|`EC_INVALID_GCM_AUTH_DATA`<ul><li>Invalid cloud authentication data (Server Key). FCM responded with status 401 (Unauthorized). Check your Application configuration for Android at Infobip Portal.</li></ul>| |8007|true|`EC_INVALID_APNS_CERT`<ul><li>Invalid certificate for APNS. Check your Application configuration for iOS at Infobip Portal.</li></ul>| |8008|true|`EC_APPLICATION_CLOUD_TYPE_DISABLED`<ul><li>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 at Infobip Portal.</li></ul>| |8009|true|`EC_PUSH_INTERNAL_REQUEST_ERROR`<ul><li>Internal error. Please try again later and if problem persists, contact Support for further assistance.</li></ul>| |8010|true|`EC_INVALID_PUSH_PAYLOAD`<ul><li>Invalid push payload data. Please contact Support for further assistance.</li></ul>| |8011|true|`EC_PUSH_INTERNAL_GW_ERROR`<ul><li>Internal error. Please try again later and if problem persists, contact Support for further assistance.</li></ul>| |8012|true|`EC_PUSH_CLOUD_TEMP_UNAVAILABLE`<ul><li>Push Cloud (FCM or APNS) is temporary unavailable. Message is pending in retry.</li></ul>| ##Email error codes ###Dropped (group id: 1) - email error codes The request has not been completed successfully as emails were dropped by the mail delivery system on end-user's side. |Id|Permanent|Error| |-|-|-| |6001|true|`EC_EMAIL_BLACKLISTED`<ul><li>Sender name used is a part of real-time database which consists of forbidden domains/sender names/IPs that are categorized as spam-friendly.</li></ul>| |6002|true|`EC_EMAIL_SPAM_CONTENT`<ul><li>Email's content/sender name/domain has been recognized/categorized as spam.</li></ul>| |6003|true|`EC_UNSUBSCRIBED_EMAIL_ADDRESS`<ul><li>End-user has unsubscribed from receiving emails from the domain/sender name used.</li></ul>| |6004|true|`EC_BOUNCED_EMAIL_ADDRESS`<ul><li>Confirmation that email cannot be delivered as bounce message was reverted on the previous attempt.</li></ul>| |6005|true|`EC_EMAIL_DROPPED`<ul><li>Recipient had previously bounced, unsubscribed, or complained of spam so we will not attempt delivery and message will be dropped.</li></ul>| ###Bounced (group id: 2) - email error codes The request has not been completed successfully and we received NDR (Non-delivery receipt). |Id|Permanent|Error| |-|-|-| |6006|true|`EC_INVALID_EMAIL_ADDRESS`<ul><li>Sender name is not a valid one - Either invalid characters or either invalid domain was used.</li></ul>| |6007|false|`EC_MAILBOX_TEMPORARILY_UNAVAILABLE`<ul><li>Server on which end-user's mailbox is hosted might having intermittent issues or smtp route/port is not available.</li></ul>| |6008|false|`EC_DEFERRED_DUE_TO_INSUFFICIENT_STORAGE`<ul><li>End-user's mailbox is hosted on server that does not have enough to storage to process/store the email.</li></ul>| |6009|true|`EC_MAILBOX_UNAVAILABLE`<ul><li>End-user's mailbox might have restricted access or simply does not exist on the server.</li></ul>| |6010|true|`EC_STORAGE_LIMIT_EXCEEDED`<ul><li>End-user's mailbox has reached its full capacity defined on the server.</li></ul>| |6011|false|`EC_SOFT_BOUNCE`<ul><li>We received bounced message (Non-delivery receipt) - Possible reasons: Mailbox is full (over quota); Recipient email server is down or offline; Email message is too large.</li></ul>| |6012|true|`EC_HARD_BOUNCE`<ul><li>We received bounced message (Non-delivery receipt) - Possible reasons: Recipient email address does not exist; Domain name does not exist; Recipient email server has completely blocked delivery.</li></ul>| ###System Error (group id: 3) - email error codes The request has not been completed successfully due to system-related errors. |Id|Permanent|Error| |-|-|-| |6013|false|`EC_TEMPORARY_SENDING_ERROR`<ul><li>Possible throttling on end-user's' side due to server configuration (limited amount of emails within certain period of time).</li></ul>| |6014|true|`EC_PERMANENT_SENDING_ERROR`<ul><li>Most commonly the issue lies within the domain used as sender as it probably was not registered yet.</li></ul>| |6015|true|`EC_GATEWAY_ERROR`<ul><li>Indicates that email failed due to configuration error or error that is not recognized/defined.</li></ul>| ##Chat error codes (Facebook messenger, Line, Viber) ###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 client. |Id|Permanent|Error| |-|-|-| |7001|true|`EC_UNKNOWN_APPLICATION`<ul><li>Application used to send the message does not exist. Make sure you have created the application and that you are using a valid application key.</li></ul>| |7002|true|`EC_UNKNOWN_USER`<ul><li>Receiving user does not exists. Check that the user has subscribed to the service and that you are using the correct user key.</li></ul>| |7003|true|`EC_BLOCKED_USER`<ul><li>Receiving user has blocked communication.</li></ul>| |7004|true|`EC_UNAUTHORIZED_ACCESS`<ul><li>Invalid or unrecognized service access credentials. Make sure that you are using the correct access credentials issued by the service provider.</li></ul>| |7005|true|`EC_FORBIDDEN_ACCESS`<ul><li>Authentication was recognized, but not allowed. Check that your application is allowed to send messages, and that it is published or approved by the provider.</li></ul>| |7102|true|`EC_PHONE_MATCHING_DISABLED`<ul><li>Facebook's Phone matching option not enabled for application. Check out the Facebook documentation to see if your application is eligible for this paid feature.</li></ul>| |7201|true|`EC_UNSUPPORTED_DEVICE`<ul><li>Receiving user does not have a device that can receive this type of message.</li></ul>| ###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`<ul><li>Internal service provider error.</li></ul>| |7051|false|`EC_PROVIDER_TIMEOUT`<ul><li>Connection to service provider timed out.</li></ul>| ###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`<ul><li>Internal error in Infobip platform. Contact Support to resolve the issue.</li></ul>| |7081|true|`EC_CONFIGURATION_ERROR`<ul><li>Internal configuration error. Contact Support to resolve the issue.</li></ul>| |7280|true|`EC_DUPLICATE_REQUEST`<ul><li>Identical message was already sent to the user recently.</li></ul>| |7281|true|`EC_BAD_ORIGIN`<ul><li>Request was sent from an unapproved origin. Contact Support to resolve the issue.</li></ul>|