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 to resolve a problem. 

Find code name

Use the page Search field or the Find on page web browser feature to quickly locate the code name you are looking for.

Code lists:

HTTP status codes


Every HTTP transaction has a status code sent back by the server to define how the server handled the transaction. The most common statuses you may have encountered are 200 OK and 404 Not Found.

Learn more about HTTP status codes here.

 

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:

{  
   "groupId":3,
   "groupName":"DELIVERED",
   "id":5,
   "name":"DELIVERED_TO_HANDSET",
   "description":"Message delivered to handset"
}	
  

General status codes

PENDING (group id: 1) - general status codes

The message has been processed and sent to the next instance i.e. mobile operator.

Id Status
3 PENDING_WAITING_DELIVERY
  • 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, so the status is still pending.
  • 7 PENDING_ENROUTE
  • Message has been processed and sent to the next instance i.e. mobile operator.
  • 26 PENDING_ACCEPTED
  • Message has been accepted and processed, and is ready to be sent to the next instance i.e. operator.
  • UNDELIVERABLE (group id: 2) - general status codes

    The message has not been delivered.

    Id Status
    4 UNDELIVERABLE_REJECTED_OPERATOR
  • Message has been sent to the operator, whereas the request was rejected, or a delivery report with status “REJECTED” was reverted.
  • 9 UNDELIVERABLE_NOT_DELIVERED
  • Message has been sent to the operator, but has failed to deliver, since a delivery report with status “UNDELIVERED” was reverted from the operator.
  • DELIVERED (group id: 3) - general status codes

    The message has successfully been processed and delivered.

    Id Status
    2 DELIVERED_TO_OPERATOR
  • Message has been successfully sent and delivered to the operator.
  • 5 DELIVERED_TO_HANDSET
  • Message has been successfully processed and delivered to the recipient.
  • EXPIRED (group id: 4) - general status codes

    The message has been sent and has either expired due to 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
  • 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.
  • 29 EXPIRED_DLR_UNKNOWN
  • 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.
  • REJECTED (group id: 5) - general status codes

    The 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
  • 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 on the coverage status or set up the network in question.
  • 8 REJECTED_PREFIX_MISSING
  • Message has been received but has been rejected as the number is not recognized due to an incorrect number prefix or number length. This information is different for each network and is regularly updated.
  • 10 REJECTED_DND
  • 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.
  • 11 REJECTED_SOURCE
  • Your account is set to accept only registered sender IDs while 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 - please top up your account. For further assistance in topping up or applying for online account top up service, you may contact your Account Manager.
  • 13 REJECTED_SENDER
  • The sender ID has been blacklisted on your account via Infobip websites portals - please remove the blacklist on your account or contact Support for further assistance.
  • 14 REJECTED_DESTINATION
  • The destination number has been blacklisted either at the operator request or on your account via Infobip websites portals - please remove the blacklist on your account via portal.infobip.com or contact Support for more information.
  • 17 REJECTED_PREPAID_PACKAGE_EXPIRED
  • Account credits have expired past their validity period - please 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 - kindly contact your Account Manager 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 i.e. no routes on your account are available for further submission. Your Account Manager will be able to set up your account based on your preference.
  • 20 REJECTED_FLOODING_FILTER
  • Message has been rejected due to an 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.
  • 21 REJECTED_SYSTEM_ERROR
  • The request has been rejected due to an expected system error, please 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, while message IDs should be a unique value. For more information, please revisit https://dev.infobip.com/docs/bulk-id-and-message-id.
  • 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 feel free to visit the below articles or contact our Support team for clarification.
    User Data Header
    Concatenated SMS
  • 25 REJECTED_MESSAGE_TOO_LONG
  • 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.
  • 51 MISSING_TO
  • 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.
  • 52 REJECTED_INVALID_DESTINATION
  • 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 validity.
  • 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 rejected as 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 formatter properly. Please revisit the documentation here.
  • 57 REJECTED_INVALID_NOTIFY_CONTENT_TYPE
  • Native to Voice services, this status is returned in case the notifyContentType parameter is not formatted properly. Please revisit the documentation here.
  • 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.
  • 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 at any of instances of requested ApplicationCode, then it will return “no destinations” as we couldn’t find anything that would satisfy the requested conditions in our database. In another example, you may want to target all application instances (devices) with the Android OS. In this case, you have to use CloudType: GCM and API internally will resolve all destinations and will send the message to all android devices linked to the requested ApplicationCode. You can also check your valid registrations by using filtering in our web interface. You can more information about User Data at our SDK pages: 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 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 SDK as a key identifier for the Application installed on an end user’s device being able to communicate with our platform. For the paired device + installed app pushRegistrationId is issued and it is uniquely linked to ApplicactionCode. It’s possible to get all available applications here. Or check configuration here.
  • Error codes


    Error object can be returned as part of the send message response or Delivery report response.

    Error object example:

    {  
       "groupId":0,
       "groupName":"OK",
       "id":0,
       "name":"NO_ERROR",
       "description":"No Error",
       "permanent":false
    }	
      

    General error codes

    OK (group id: 0) - general error codes

    The request has been completed successfully.

    Id Permanent Error
    0 false NO_ERROR
  • There is no error description provided. Mostly returned for successful delivery or when an error code was not returned by the operator.
  • 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
  • The number does not exist or it has not been assigned to any active subscriber in the operator’s user database.
  • 5 false EC_UNIDENTIFIED_SUBSCRIBER
  • Unidentified Subscriber.
  • 6 false EC_ABSENT_SUBSCRIBER_SM
  • As there was no paging response from the handset the subscriber was detected as unavailable. This is often due to the handset being switched off or in a low signal area. Applies to MAP protocol version 3.
  • 7 false EC_UNKNOWN_EQUIPMENT
  • The mobile device has not been recognized by EIR (Equipment Identity Register) during device verification on MAP protocol level at the operator’s infrastructure.
  • 8 false EC_ROAMING_NOT_ALLOWED
  • The subscriber is currently in roaming in another country or using another operator’s infrastructure - roaming delivery is not guaranteed due to lack of roaming agreements between many different operators.
  • 9 true EC_ILLEGAL_SUBSCRIBER
  • Illegal Subscriber.
  • 11 true EC_TELESERVICE_NOT_PROVISIONED
  • The subscriber’s mobile service has been suspended by the operator.
  • 12 true EC_ILLEGAL_EQUIPMENT
  • Illegal Equipment.
  • 13 false EC_CALL_BARRED
  • The subscriber is set to DND (Do Not Disturb) service, opting out of receiving any service traffic to their number.
  • 21 false EC_FACILITY_NOT_SUPPORTED
  • Facility Not Supported.
  • 27 false EC_ABSENT_SUBSCRIBER
  • 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.
  • 31 false EC_SUBSCRIBER_BUSY_FOR_MT_SMS
  • Subscriber Busy For MT SMS.
  • 32 false EC_SM_DELIVERY_FAILURE
  • SM Delivery Failure.
  • 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
  • There has been a mobile subscriber equipment error, the handset memory has been exceeded.
  • 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 message submit request, or such error was reverted by the operator. The error also applies to similar errors on 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.
  • 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 network peer because of a network protocol error.
  • 1282 false EC_UA_USERRESOURCELIMITATION
  • Message was aborted by network peer because of a network protocol error.
  • 1283 false EC_UA_RESOURCEUNAVAILABLE
  • Message was aborted by network peer because of a network protocol error.
  • 1284 false EC_UA_APPLICATIONPROCEDURECANCELLATION
  • Message was aborted by 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) - general error codes

    User error occurred.

    Id Permanent Error
    2049 true EC_IMSI_BLACKLISTED
  • IMSI blacklisted.
  • 2052 true EC_BLACKLISTED_DESTINATIONADDRESS
  • The destination number has been blacklisted either at the operator’s 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.
  • 2053 true EC_BLACKLISTED_SENDERADDRESS
  • The sender number has been blacklisted either at the operator’s 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.
  • 2053 true EC_SOURCE_ADDRESS_BLACKLISTED
  • Source address is blacklisted on the Infobip account.
  • 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, please contact your Account Manager.
  • 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, and has expired with the appropriate error code EC_VALIDITYEXPIRED or the error code was reverted from the operator.
  • 4102 true EC_NOTSUBMITTEDTOSMPPCHANNEL
  • Inbound SMS can not be transferred via SMPP due the lack of SMPP connectivity.
  • 4103 true EC_DESTINATION_FLOODING
  • Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of messages sent to a single number.
  • 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) - general error codes

    The request has not been completed due to operator issues.

    Id Permanent Error
    10 true EC_BEARER_SERVICE_NOT_PROVISIONED
  • Bearer Service Not Provisioned.
  • 20 false EC_SS_INCOMPATIBILITY
  • SS Incompatibility.
  • 51 true EC_RESOURCE_LIMITATION
  • Indicates that the invoked MAP operation could not be finished due the network congestion - this is an SS7 network congestion error on the MAP protocol level.
  • 71 false EC_UNKNOWN_ALPHABET
  • Unknown Alphabet.
  • 501 false EC_INVALID_RESPONSE_RECEIVED
  • Invalid Response Received.
  • 2048 false EC_TIME_OUT
  • Time Out.
  • 2050 true EC_DEST_ADDRESS_BLACKLISTED
  • 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.
  • 2051 false EC_INVALIDMSCADDRESS
  • Text blacklisted.
  • 4097 false EC_NOTSUBMITTEDTOGMSC
  • Not Submitted To GMSC.
  • 4102 true EC_NOTSUBMITTEDTOSMPPCHANNEL
  • Not Submitted To Smpp Channel.
  • Voice error codes

    OK (group id: 0) - voice error codes

    The request has been completed successfully.

    Id Permanent Error
    5000 true VOICE_ANSWERED
  • The call has been received and answered.
  • 5001 true VOICE_ANSWERED_MACHINE
  • The call has been received and answered by a voice machine.
  • 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
  • Destination address is currently not available.
  • 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 end user is currently busy and can not receive the Voice call.
  • 5003 true EC_VOICE_NO_ANSWER
  • The end user received a call but didn’t answer it.
  • 5004 true EC_VOICE_ERROR_DOWNLOADING_FILE
  • The file specified in the HTTP request is inaccessible, and could not be downloaded.
  • 5005 true EC_VOICE_ERROR_UNSUPPORTED_AUDIO_FORMAT
  • Format of the file specified is not supported.
  • 5400 false EC_VOICE_ERROR_BAD_REQUEST
  • Received request was rejected because is wasn’t formatted correctly.
  • 5403 false EC_VOICE_ERROR_FORBIDDEN
  • Received request was rejected by the operator.
  • 5404 false EC_VOICE_ERROR_DESTINATION_NOT_FOUND
  • The server has definitive information that the user does not exist at the domain specified in the Request-URI.
  • 5407 false EC_VOICE_ERROR_PROXY_AUTHENTICATION_REQUIRED
  • The request requires user authentication on the operator’s end.
  • 5408 false EC_VOICE_ERROR_REQUEST_TIMEOUT
  • There was no coverage for a specific destination number or the end user couldn’t be found in time during the call.
  • 5410 false EC_VOICE_ERROR_GONE
  • The user existed once, but the operator doesn’t support the destination address anymore.
  • 5413 false EC_VOICE_ERROR_REQUEST_ENTITY_TOO_LARGE
  • Request entity-body is larger than the server is willing or able to process.
  • 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 file format is not supported.
  • 5484 false EC_VOICE_ERROR_ADDRESS_INCOMPLETE
  • Specified destination number is incomplete.
  • 5487 false EC_VOICE_ERROR_REQUEST_TERMINATED
  • Request was terminated by a cancel button and the end user refused to receive a voice call.
  • 5488 false EC_VOICE_ERROR_NOT_ACCEPTABLE_HERE
  • The format of the request is not acceptable on the operator’s end.
  • 5491 false EC_VOICE_ERROR_REQUEST_PENDING
  • Server has some pending request from the same dialog.
  • 5492 true EC_DUPLICATE_MESSAGE
  • The same voice message has already been sent to this destination address.
  • 5501 true EC_VOICE_NOT_IMPLEMENTED
  • Submitted request is not supported on the operator’s end.
  • 5503 true EC_VOICE_SERVICE_UNAVAILABLE
  • The service failed to complete the request.
  • 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
  • User has uninstalled the application on the device or device cloud token expired.
  • 8002 true EC_GCM_MISMATCH_SENDER_ID
  • FCM responded with MismatchSenderId in the 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.
  • 8003 true EC_NO_APPLICATION_FOUND
  • Application with the provided ApplicationCode is not found at Infobip Push service. Check your message target parameters.
  • 8004 true EC_NO_REGISTRATION_ID_FOUND
  • Registration with the 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 at Infobip Portal.
  • 8007 true EC_INVALID_APNS_CERT
  • Invalid certificate for APNS. Check your Application configuration for iOS at Infobip Portal.
  • 8008 true EC_APPLICATION_CLOUD_TYPE_DISABLED
  • Cloud type was disabled by the client for the application. Request is targeted to registration with the cloud type that was disabled by the client. Check your Application configuration at Infobip Portal.
  • 8009 true EC_PUSH_INTERNAL_REQUEST_ERROR
  • Internal error. Please try again later and if the problem persists, contact Support for further assistance.
  • 8010 true EC_INVALID_PUSH_PAYLOAD
  • Invalid push payload data. Please contact Support for further assistance.
  • 8011 true EC_PUSH_INTERNAL_GW_ERROR
  • Internal error. Please try again later and if the problem persists, contact Support for further assistance.
  • 8012 true EC_PUSH_CLOUD_TEMP_UNAVAILABLE
  • Push Cloud (FCM or APNS) is temporary unavailable. Message is pending in retry.
  • 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 at the end-user’s side.

    Id Permanent Error
    6001 true EC_EMAIL_BLACKLISTED
  • The sender name used is part of a real-time database which consists of forbidden domains/sender names/IPs that are categorized as spam-friendly.
  • 6002 true EC_EMAIL_SPAM_CONTENT
  • The email’s content/sender name/domain has been recognized/categorized as spam.
  • 6003 true EC_UNSUBSCRIBED_EMAIL_ADDRESS
  • End-user has unsubscribed from receiving emails from the domain/sender name used.
  • 6004 true EC_BOUNCED_EMAIL_ADDRESS
  • Confirmation that the email cannot be delivered as a bounce message was reverted on the previous attempt.
  • 6005 true EC_EMAIL_DROPPED
  • Recipient has previously bounced, unsubscribed, or complained of spam so we will not attempt delivery and the message will be dropped.
  • 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
  • Sender name is not a valid one - Either invalid characters or an invalid domain was used.
  • 6007 false EC_MAILBOX_TEMPORARILY_UNAVAILABLE
  • Server on which the end-user’s mailbox is hosted might be having intermittent issues or the smtp route/port is not available.
  • 6008 false EC_DEFERRED_DUE_TO_INSUFFICIENT_STORAGE
  • End-user’s mailbox is hosted on a server that does not have enough storage to process/store the email.
  • 6009 true EC_MAILBOX_UNAVAILABLE
  • End-user’s mailbox might have restricted access or simply does not exist on the server.
  • 6010 true EC_STORAGE_LIMIT_EXCEEDED
  • End-user’s mailbox has reached its full capacity as defined on the server.
  • 6011 false EC_SOFT_BOUNCE
  • We received a bounced message (Non-delivery receipt) - Possible reasons: Mailbox is full (over quota); Recipient email server is down or offline; Email message is too large.
  • 6012 true EC_HARD_BOUNCE
  • We received a 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.
  • 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
  • Possible throttling on end-user’s side due to server configuration (limited amount of emails within a certain period of time).
  • 6014 true EC_PERMANENT_SENDING_ERROR
  • Most commonly the issue lies within the domain used as sender as it probably was not registered yet.
  • 6015 true EC_GATEWAY_ERROR
  • Indicates that the email failed due to a configuration error or an error that is not recognized/defined.
  • 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 the client.

    Id Permanent Error
    7001 true EC_UNKNOWN_APPLICATION
  • 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.
  • 7002 true EC_UNKNOWN_USER
  • Receiving user does not exist. Check that the user has subscribed to the service and that you are using the correct user key.
  • 7003 true EC_BLOCKED_USER
  • Receiving user has blocked communication.
  • 7004 true EC_UNAUTHORIZED_ACCESS
  • Invalid or unrecognized service access credentials. Make sure that you are using the correct access credentials issued by the service provider.
  • 7005 true EC_FORBIDDEN_ACCESS
  • 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.
  • 7102 true EC_PHONE_MATCHING_DISABLED
  • 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.
  • 7201 true EC_UNSUPPORTED_DEVICE
  • Receiving user does not have a device that can receive this type of message.
  • 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
  • Internal service provider error.
  • 7051 false EC_PROVIDER_TIMEOUT
  • Connection to service provider timed out.
  • 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
  • Internal error in Infobip platform. Contact Support to resolve the issue.
  • 7081 true EC_CONFIGURATION_ERROR
  • Internal configuration error. Contact Support to resolve the issue.
  • 7083 true EC_SERVICE_NOT_ACTIVATED
  • Service not active. Contact Support to resolve the issue.
  • 7280 true EC_DUPLICATE_REQUEST
  • Identical message was already sent to the user recently.
  • 7281 true EC_BAD_ORIGIN
  • Request was sent from an unapproved origin. Contact Support to resolve the issue.