Errors Table
Note: If a user submitted more than one message and at least one was rejected, HTTP 207 is returned indicating that message-level responses must be looked at. This condition overrides the codes listed below.
|
Error Code |
HTTP Status Code |
Error Message |
Global Level |
Message Level |
|
1 |
401 |
Invalid or missing integration API Key |
x |
|
|
2 |
400 |
Account is not active |
x |
|
|
3 |
400 |
Integration is not active |
x |
|
|
7 |
401 |
Originating IP address is not approved in your account |
x |
|
|
18 |
500 |
Internal error |
x |
x |
|
19 |
503 |
Internal error, please retry |
x |
x |
|
Generic errors (shared by all channels) |
||||
|
20 |
402 |
Insufficient account balance |
|
x |
|
21 |
400 |
Payload data is malformed |
x |
|
|
22 |
400 |
Maximum messages per request payload exceeded |
x |
|
|
23 |
400 |
Invalid or missing parameter: (parameter name) |
|
x |
|
24 |
400 |
Maximum message content size exceeded |
|
x |
|
25 |
400 |
Invalid recipient address: (MSISDN) |
|
x |
|
26 |
400 |
Recipient opted out |
|
x |
|
27 |
400 |
Recipient not available on channel |
|
x |
|
28 |
400 |
Recipient not available on sandbox |
|
x |
|
29 |
|
Reserved |
|
|
|
30 |
400 |
Content type not supported |
|
x |
|
31 |
400 |
Media file size exceeds limit of xx MB |
|
x |
|
32 |
400 |
Media payload size exceeds limit of xx MB |
|
x |
|
33 |
400 |
Media item not found |
|
x |
|
34 to 37 |
|
Reserved |
|
|
|
38 |
400 |
Channel/feature is not active on integration |
|
x |
|
39 |
400 |
Channel is not available on integration |
|
x |
|
40 |
400 |
Character set is not supported: (charset) |
|
x |
|
41 |
400 |
Resource does not exist |
x |
|
|
42 |
400 |
HTTP method is not supported on this resource |
x |
|
|
43 |
400 |
Rate limit |
x |
x |
|
44 |
400 |
FROM number is suspended |
|
x |
|
45 |
400 |
FROM number is not related to integration |
|
x |
|
46 |
400 |
Demo access has expired |
|
x |
|
Channel-specific errors: SMS |
||||
|
100 |
400 |
Maximum message parts exceeded |
|
x |
|
101 |
400 |
Destination does not support two-way messaging |
|
x |
|
110 |
400 |
USA country limit: must use two-way integration |
|
x |
|
111 |
400 |
USA country limit: must enable STOP/SUBSCRIBE commands on integration |
|
x |
Channels
Find the most up-to-date information about the channels available to communicate with your clients.
SMS
Enable any application, website or system to facilitate local or international one- or two-way SMS communication via an easy one-step integration with our HTTP API.
Documentation
One API
Communicate with your mobile customers via multiple communication channels with a single integration. You can send and receive messages on both WhatsApp and SMS without the overhead of programming individual channels.
Documentation
As an authorized WhatsApp Business Solution Provider, we assist you in applying for a WhatsApp Business account and number. Integrate with other powerful features available on our platform via our One API.
Documentation
Products
Find the most up-to-date information about the products we offer and how to elevate your engagement with customers.
Chat 2 Pay
Send payment requests to customers via chat for secure, contactless payment experiences.
Documentation
Chat Desk
An easy-to-use web-based application that enables real-time communication with your customers via a single web interface.
Documentation
Chat Flow
A web-based application that allows you to quickly and collaboratively design and deploy conversational experiences across multiple chat applications and connect it to your organization's core functional APIs.
Documentation
Campaign Manager
An online tool that allows you to create a custom SMS campaign within minutes - no coding or developers required.
Documentation
Marketplace
Find the most up-to-date information about Clickatell's Marketplace and how you can utilize it for the distribution and payment acceptance of digital products.
Bank Interfaces API
An explanation of the way Clickatell and banks interact with one another when dealing with purchases.
Documentation
Transact Result API
Initiates the delivery of the transaction result for a purchase that was made through Clickatell after Clickatell facilitated the dispensing of the product.
Documentation
Reserve and Transact API
Initiates a purchase and fund reservation request to Clickatell.
Documentation
Security Service API
Request authentication tokens to use in all other Clickatell API calls.
Documentation
Transact
A cloud-based platform that allows for the distribution and payment acceptance of multiple digital products.
Documentation
In-Flight Transaction Check API
Used prior to a purchase instruction to confirm that no similar transaction is in progress.
Documentation
User Transaction Lookup API
Identify if a new transaction is similar to one of the user's recent transactions so the response details can be used to pre-emptively complete the current transaction details.
Documentation
Customer Account Validation API
Validate a customer's bill payment account number prior to submitting the bill payment purchase request to the vendor.
Documentation
MNO Lookup API
Derive the specific mobile network operator (MNO) for the specified MSISDN.
Documentation
Token Lookup API
Look up tokens/vouchers to present back to the buyer/customer who purchased token-related products via Clickatell's platform.
Documentation
Notifications API
Send notifications to buyer/recipient using different channels.
Documentation
Transaction Lookup API
Used after a purchase to confirm the transaction status.
Documentation
Financial Terms Lookup API
Display the correct fee and settlement amounts as per the contractual agreement for the SKU being purchased.
Documentation
Other Resources
Ask the Community
Visit Stack Overflow to join our community of developers and find the answer you need
Contact Support
Contact our support team and one of our agents will be in touch with you to answer any questions you have