API Errors

Messages API

CodeInformation
1000

Throttled - You have exceeded the submission capacity allowed on this account. Please wait and retry

1010

Missing params - Your request is incomplete and missing some mandatory parameters.

1020

Invalid params - The value of one or more parameters is invalid.

1021

Invalid tag - The tag value is invalid.

1022

Invalid template - Invalid template or template parameters

1030

Internal error - There was an error processing your request in the Platform.

1040

Invalid message - The Platform was unable to process your request. For example, due to an unrecognised prefix for the phone number.

1050

Number barred - The number you are trying to submit to is blacklisted and may not receive messages.

1060

Partner account barred - The api_key you supplied is for an account that has been barred from submitting messages.

1070

Provider quota exceeded - your allocated quota may have been exceeded.

1080

Account not enabled for REST - This account is not provisioned for REST submission, you should use SMPP on the SMS API.

1090

Message too long - The length of udh and body was greater than 140 octets for a binary type SMS request.

1100

Communication Failed - Message was not submitted because there was a communication failure.

1120

Illegal Sender Address - rejected - Due to local regulations, the SenderID you set in from in the request was not accepted. Please check the Global messaging section.

1130

Invalid TTL - The value of ttl in your request was invalid.

1140

Facility not allowed - Your request makes use of a facility that is not enabled on your account.

1150

Invalid Message class - The value of message-class in your request was out of range. See https://en.wikipedia.org/wiki/Data_Coding_Scheme.

1160

Non White-listed Destination - The phone number you set in to is not in your pre-approved destination list. To send messages to this phone number, add it using Dashboard.

1170

Invalid recipient - The to parameter is missing or contains an invalid address or identifier.

1180

Destination temporarily unavailable - The destination cannot currently receive messages. Retry later.

1190

Absent Subscriber Permanent - to is no longer active, You should remove this phone number from your database.

1200

Portability Error - There is an issue after the user has changed carrier for to. If the user wants to receive messages from you, they need to contact their carrier directly.

1210

Anti-Spam Rejection - Carriers often apply restrictions that block messages following different criteria. For example on SenderID or message content.

1220

Handset Busy - The handset associated with to was not available when this message was sent. If status is rejected, this is a temporary failure; retry later for a positive result. If status is submitted, this message has is in the retry scheme and will be resent until it expires in 24-48 hours.

1230

Temporary network failure - The message could not be delivered due to a network issue. Retry later.

1240

Illegal Number - You tried to send a message to a blacklisted phone number. That is, the user has already sent a STOP opt-out message and no longer wishes to receive messages from you.

1241

Too many send requests - Too many send requests to phone numbers.

1242

Number pool does not exists - check that the number pool has been configured for your account

1250

Unroutable - The chosen route to send your message is not available. This is because the phone number is either currently on an unsupported network or on a pre-paid or reseller account that could not receive a message.

1251

Unable to route traffic to a destination - This may be due to the routing rules applied for your destination network.

1260

Destination unreachable - The message could not be delivered to the phone number. If using Viber Business Messages your account might not be enabled for this country.

1270

Subscriber Age Restriction - The carrier blocked this message because the content is not suitable for to based on age restrictions.

1280

Number Blocked by Carrier - The carrier blocked this message. This could be due to several reasons. For example, to's plan does not include SMS or the account is suspended.

1282

Message rejected by provider - The provider blocked the message may be due to policy or content restrictions.

1290

Pre-Paid - Insufficient funds - to's pre-paid account does not have enough credit to receive the message.

1300

Not part of the provider network - The number or ID is not a user in the provider network.

1310

Not suitable device - The user's device can't receive the message.

1320

Message already sent - The message was already sent.

1330

Delivery failed - The provider returned an unknown permanent failure. Verify the destination and retry if appropriate.

1331

Provider error - The provider is not responding or unable to process the request. Please try sending your message in a few minutes time.

1340

Outside of the allowed window - This message is sent outside of allowed response window.

1350

Phone matching fee not paid - Requires phone matching access fee to be paid by the Facebook Page.

1360

TTL was activated, or message expired before delivered.

1370

Expired access Token - Please reauthenticate your Facebook Page with Vonage.

1380

Invalid resource - Please check that the URL your provided to your resource is accessible and valid.

1381

Resource size is too large - Please try sending a smaller media file.

1382

Unsupported resource type - The attached resource type is not supported or invalid.

1400

Unsupported channel - The channel specified in the request is not supported.

1410

Invalid channel parameters - The value of one or more parameters is invalid.

1420

Invalid sender - The from parameter is invalid for the given channel.

1430

Invalid recipient - The to parameter is invalid for the given channel.

1431

Multiple recipients error - Multiple recipients not supported.

1440

Invalid message type - The message type specified in the request is not supported for the given channel.

1450

Invalid client reference - The client reference can be a string of up to 100 characters.

1451

Invalid context - the reference to the original message could not be found because it is invalid or no longer available.

1460

Daily message limit exceeded - Check compliance with regulations such as 10DLC.

1461

Auto-limiting of messages by Provider - This message was not delivered by Provider to avoid excessive messages to the end user. For details please see this knowledgebase article.

1470

Fraud Defender Traffic Rule - Rejected due to Fraud Defender traffic rules block.

1472

Fraud Defender SMS Burst Protection - Traffic limit has been reached

1473

AIT Protection - The message has been rejected by Fraud Defender AIT Protection

1474

Fraud Defender Traffic Rule - Rejected due to Fraud Defender country block.

1475

Fraud Defender Traffic Rule - Rejected due to Fraud Defender network block.

1476

Do Not Originate (DNO) - Originating number is on a DNO list.

1480

Entity Filter - The message failed due to entity_id being incorrect or not provided. More information on country specific regulations.

1481

Header Filter - The message failed because the header ID (from phone number) was incorrect or missing. More information on country specific regulations.

1482

Content Filter - The message failed due to content_id being incorrect or not provided. More information on country specific regulations.

1483

Consent Filter - The message failed due to consent not being authorized. More information on country specific regulations.

1484

Authentication or compliance failure - The message failed authentication or regulatory checks. Verify sender configuration or contact support.

2001

Fraud protection triggered - The message was blocked by fraud or abuse protection rules at the provider side.

2002

Email size exceeded - The message or payload exceeds the allowed size limit. Reduce the payload and retry.

2003

Destination unavailable - Recipient email address is in the suppression list, which may be due to an earlier email being hard bounced or marked as spam by the user.