Developer API Reference
Complete HTTP(s) API reference for Third Party Integrations
Rich set of REST Compatible APIs
SMS Handover offers amazing selection of APIs for messaging, credit check and delivery reports. Our API supports push-callback or the webhook method for instant DLR push. These APIs are high performance with support upto 50,000 message per request via HTTP POST. Create an account with us to explore full API offerings.
API ENDPOINT (GET and POST)
Send SMS API
https://console.smshandover.com/smsapi/index
Parameters | Meaning | Description |
---|---|---|
key= | API Key (required) |
An API Key assigned to your account |
&campaign= |
as defined in description (optional) |
Campaigns are for organizing your messages. Enter ID of campaign as shown below. You can use 0 (zero) or skip it for the default campaign. |
&routeid= |
ID of the route as defined in description (optional) |
For account with multiple marketing channels (or Routes), supply route ID here. It will be displayed in API details within your portal. |
&type= | SMS Type (optional) |
text, unicode, flash etc. Default is text |
&contacts= | Contact Numbers (required) |
Contact numbers separated by ‘ , ‘ (comma) sign e.g. 919887XXXXXX,919567XXXXXX For accurate routing, supply mobile numbers including the country prefix. |
&senderid= | Sender ID (required) |
Any Approved Sender ID from your account |
&msg= | SMS Text (required) |
Url-encoded SMS text. Must be limited to 720 characters |
&time= | Schedule Time (optional) |
Enter the time in the format YYYY-MM-DD H:I e.g. enter 2013-03-19 14:30 for 19th March 2013, 2:30 pm. Leave BLANK to send the SMS instantly. |
&bulk_campaigm= |
Optional for multiple submission (optional) |
For personalized campaign supply the values like shown below:.
|
&dlr_url= |
Optional URL to post DLR (optional) |
You can provide a URL where our system will post delivery reports. |
Responses
API Response | Description |
---|---|
|
An error occurred while submitting the API call request. The source of error would be explained in the braces {}, for instance, “ERR: INVALID API KEY” means the API key entered is expired or does not belong to any user. The error messages are not ciphered and pretty much intuitive. |
|
This means SMS was submitted successfully, and it returns the shoot-id of the submission. You could use this ID to pull out delivery reports. |
Sample URL & Sample API Codes |
Simple SMS
|
Scheduled SMS
|
Sample Codes
|
API ENDPOINT (GET)
BALANCE CHECK API
https://console.smshandover.com/miscapi/< api-key >/getBalance/true/
Parameters | Meaning | Description |
---|---|---|
api-key | API Key (required) |
An API Key assigned to your account |
Responses
API Response | Description |
---|---|
|
An error occurred while submitting the API call request. The source of error would be explained in the braces {}, for instance, “ERR: INVALID API KEY” means the API key entered is expired or does not belong to any user. The error messages are not ciphered and pretty much intuitive. |
|
This will return a JSON Array with specified values |
Sample URL & Sample API Codes |
Simple Call
|
Sample Codes
|
dlr
API ENDPOINT (GET and POST)
Send OTP API
https://console.smshandover.com/send-otp/index
Parameters | Meaning | Description |
---|---|---|
key= | API Key (required) |
An API Key assigned to your account |
channel_id= | as defined in description | Mandatory. Enter the channel ID to be used for OTP. |
mobile= | phone number to verify | mobile number with country code e.g. 919887XXXXXX |
Responses
API Response | Description |
---|---|
|
API call was successful and a reference will be provided. Use this in next API call to verify OTP |
|
An error occurred while submitting the API call request. The source of error would be explained in the braces {}, for instance, "ERR: MISSING CHANNEL ID" means tere was no channel ID supplied. The error messages are not ciphered and pretty much intuitive. |
Sample URL & Sample API Codes |
Simple Call
|
Sample Codes
|
API ENDPOINT (GET and POST)
Verify OTP API
https://console.smshandover.com/verify-otp/index
Parameters | Meaning | Description |
---|---|---|
key= | API Key (required) |
An API Key assigned to your account |
reference= | as defined in description | Mandatory. Supply the reference received during Send OTP API call. |
otp= | one-time password to match | supply the OTP entered by user here |
Responses
API Response | Description |
---|---|
|
API call was successful and OTP was matched |
|
API call was successful BUT OTP entered was wrong. |
|
API call was successful BUT OTP is expired or too many attempts |
|
An error occurred while submitting the API call request. The source of error would be explained in the braces {}, for instance, "ERR: MISSING REFERENCE" means tere was supplied reference was empty. The error messages are not ciphered and pretty much intuitive. |
Sample URL & Sample API Codes |
Simple Call
|
Sample Codes
|