Developers have 3 options to integrate our API:
One simple API request (URL/endpoint) and you are live. Perfect for quick integration to send SMS messages
The perfect API to send/receive SMS messages and have access to many system features (like opt-out management)
Access every feature we have. Detailed and meticulous API for advanced integrations
For this, Mobivate recommends you use our Simple API.
- Mobivate recommends using "mglobal", but other Route IDs are available upon request
- 11 alpha-numeric sender name or 15 digit number
- international formatted mobile/cell number
- Text message (160 characters, 70 if containing Unicode (2 bytes) characters)
- Your username
- Your password
NOTE: Please don't forget to URL Encode parameters if using the HTTP GET method. URL Encoding is NOT required when using HTTP POST!
If your service provider is already integrated with Mobivate SMS, you should be able to configure your
API Key on their platform and this should enable you to send SMS directly from the 3rd Party software.
The API Key, you can find on our portal under User Profile section.
If your service provider is not already integrated, you can ask them to do so. It should only take them few minutes to complete the integration using this simple API:
Post Data (raw)
- (required) Mobivate recommends using "mglobal", but other Route IDs are available upon request
- (required) 11 alpha-numeric sender name or 15 digit number
- (required) international formatted mobile/cell number
- (required) Text message (160 characters, 70 if containing Unicode (2 bytes) characters)
- (optional) Campaign ID. Requires an existing Campaign
- (optional) Your internal reference
Mobivate is integrated with more than 1'500 apps via Zapier
If you wish to connect your software with Mobivate and automate SMS sending, click here to create your ZAP
To verify if the number is valid (active on any network), you can request a Home Location Register (HLR) lookup.
On success, we will return JSON
You can add or remove your contacts from multiple Mobivate applications in one go by using our proxy API. In this case the MSISDN is used as identifier. Supplied reference is for your identification only.
You can create or remove the contacts by its msisdn. You can use these parameters:
||yes||The username used to login to Mobivate|
||yes||The password used to login to Mobivate|
||yes||Phone number in international format|
||yes||Comma separated list of applications to subscribe to / remove from (see below)|
||no||The contacts name to use|
||no||Optional custom reference for the contact, used as callcentre reference id or custom 1 field|
Applications are denoted as a comma "," separated list, with colon ":" as the separator between the app name and identification token of the contact group/recurring campaign
- The appointment booking app
- The periodic reminder app
- The main contacts app
- The Callcentre app
sms / call
- Generic optouts
Finding the Identification Tokens
CampaignId can be obtained as the last numeric parameter of the url while editing the campaign details
ContactGroupId is shown on the group details at the bottom of the right column
SetupId is shown on the setup details at the bottom of the right column
The identification is either
sms for sms optouts or
calls for robocall optouts
Connect via SMPP
Mobivate is one of the few bulk SMS companies that offer SMPP to its customers. SMPP is best used for large organisations that wish to send large volumes of SMS messages on a continuous basis.
What is SMPP?
SMPP or short message peer to peer is a standard open industry protocol in the telecommunications industry for exchanging SMS messages between Short Message Service Centers (SMSC) and/or External Short Messaging Entities (ESME).
It caters for large volumes of transactions, is fast and extremely flexible as a data transfer and communications interface.
Please contact us directly to arrange SMPP details for you. We will have your SMPP client set up within 24 hours.
SMPP Server Features
|7Bit SMS (standard port)||YES|
|7Bit SMS ( non-standard port)||NO|
|Concatenated 7Bit SMS||YES|
|UCS2 (16-Bits Unicode) SMS||YES|
|Concatenated UCS2 SMS||YES|
|8-Bits binaries SMS||NO|
|Concatenated binaries SMS||NO|
|Alphabetic Originating Address||YES|
|Numeric Originating Address||YES|
FAQ's for SMPP Connectivity
|2. Type of bind: TX/RX or TRX?||Either|
|4. Number of binds allowed?||3|
|5. Throughput per bind||20|
Mobivate Security and Encryption
Two areas where data security needs to be assessed
Access to our database servers is secured using network Access Control Lists (ACLs) which only allow access from our application server.
Access to our application servers is double layered - a VPN connection is required to access the internal network, and servers are accessible using 1024bit public/private key encryption. We are always improving security and always use best servers on the market.
A company you can trust
On 1 July 2015 we celebrated our 11th year of business and we have NEVER (not once) had any issues with security, data integrity, technical or server security breaches. We have clients like Dominos, Mercedes Benz, Kitty Bingo, top pay day lenders etc. We have access to all of their data but it is 100% secure and will never be shared with anyone. Ever!
We offer support 24 hours a day 7 days a week. If you have any questions or need any help do not hesitate to contact us. Our expert software engineers are here to help you every step of the way. We will even write the code for you and assist you with your very own scripting.