Using the SOAP API
SMS messages are sent by making SOAP requests via
HTTPS to the API. You can loop through your list of mobile numbers and make HTTP/S requests to send SMS messages to them. Generally, this API should allow you to submit up to about 100 messages per second on average to our platform (or faster if required).
Clickatell offers two SOAP servers – you can use whichever is compatible with your software.
1) Document/Literal SOAP Server (most popular)
- This server supports optional gzip compression.
2) RPC/Encoded SOAP Server
- In order to utilize the bypass_dnc_check parameter, this new version WSDL endpoint must be used: http://api.clickatell.com/soap/rpc_encoded/v1.1/webservice?wsdl
Tip: If you are using .Net, make sure your connection URL does not have ?wsdl at the end of the URL. That is only needed when getting the schema.
More information about this API
HTTP(port 80) and
- You can send to multiple handsets in one single request (up to 300 numbers) – this is useful if you are sending the same message text to all the handsets.
- Supports persistent connections (keep-alive) and the use of multiple concurrent connections.
- Supports sending of flash messages.
- Supports sending of binary message content.
- Supports sending of Unicode messages.
Send your first message
To send your first message you will need:
- Your API username and API password
- API ID
- A SOAP client
- Import one of the above-listed WSDLs using your SOAP software.
- Use the
- Set the
api_idfield. If you do not yet have an API ID, read the Account Setup section.
- Set the
passwordfield (this is your API username and API password).
- Set the
tofield to your mobile number. Format the mobile number that you want to send to in international format.
- The mobile number needs to start with the correct country code.
- There must be no spaces or other non-numeric characters.
- If the mobile number starts with zero, remove the zero before typing the rest of the number.
- Perform the SOAP request to send your first message.
Also view the send message page.
Note: until you make a purchase, we will populate your messages with pre-defined content.
For additional security you can choose to:
HTTPSfor all API requests
- Enable IP lockdown on your API connection
- Use session ID for authentication instead of passing username and password for each request
You can authenticate your requests in one of two ways:
- Send your API username, API password and API ID with each request.
- Send a session ID with each request. A session ID can be obtained with the Authentication command.
Submit a Comment
Ask the Community
Visit Stack Overflow to join our community of developers and find the answer you need
Contact our support team and one of our agents will be in touch with you to answer any questions you have