movil developer zone offer an Application Programming Interface,
movilAPI, that opens movil messaging to be used from another sites.
We would like to innovate in the mobile community area bringing useful messaging tools.
For now on only the pro-users will have API access since they can send more than 1 sms a day and they will have priority access to our gateway interface.
The API access is simple to use, it is accessible as an http-based web service through HTTP protocol, so you the implementation is very fast. To send a message you need to invoke a specially formatted URL or send the variables through a web form.
This is what we offer in the initial release (0.8) :
POST / GET method . GET is not recommended because you need to pass the API key in a visible way, but you can use it to send a fast Sms from your browser or from the command line.
Scheduling is not enabled at the moment. You send the POST data and the message is delivered instantly.
To send there will be two *required items:
APIKEY *
32 characters key that you will get on movil
MESSAGEBODY *
140 characters maximum the SMS body
DESTINATION (If it's not set your mobile will be the destination)
if it's a valid number (Ccode+GSM number) it will be send to that number with the originator number defined at movil.
With this three fields, without passing anything else to the url we provide, the system will resolve your account and post the message
maintaining your Originator number (in most operators).
We wanted to make clear that movil is currently
not sending SMS's for US/Canada. If you would like to use an SMS api there we reccomend checking out
vazu.com (We didn't tested ourselves, but we read good comments about them)
The request
In order to send a request to the
movilAPI you need to send variables through GET/POST to this url:
http://movil.be/http
For example, if you want to try it directly in your browser, you will write in the location bar:
http://movil.be/gadget/api/?name=#username&hpass=yourAPIkey
Note that it must be all together, it's separated with linebreaks so it's easier to read, and
variables should be in smallcase. If you don't urlencode your message most browsers will do it for you sending by GET. But sending from your applications you need to urlencode it before.
The response
After sending your variables through GET/POST to the API url, you will receive a response from the gateway.
Successful response:
nº of credits left,OK
Your message was send.
Error response:
ERROR, error description.
As you can see there is no personal information or numbers in the response. You just get "OK sended" or "ERROR, something happened" that's it.
There are some extra links with more information:
Priority gateway test in European countries
API design planning. Part one
This is the HTTP version of the Api in it's beta release. It's not planned to build a bulk-sending service so please avoid calling the API more than 10 /15 times per second. However, you can try if you like, our server will just ask you to charge a lot of credits.
In the near future we plan to accept also REST type calls and to be able to send to multiple destinations in the same call. We would like to hear
your opinion about it.
