SMS Portal REST API

Cor Cronje

Active Member
Joined
Jul 21, 2010
Messages
56
Reaction score
3
Location
Bloemfontein
Anyone here worked with SMS Portal's REST API ?

I am upgrading an old project that employed the legacy web services API from SMS Portal to the their REST API. The old web services API allowed for multiple comma separated destination numbers to be specified when declaring a bulk SMS message. The REST API however doesn't seem to support comma, space or semicolon separated destination numbers, but instead an array of 100 messages.

My issue with this approach is that. previously I was able to fire-off a bulk SMS message with over 27000 destination numbers using a single HTTP POST request, but with the REST API it seems I'll have to build a collection of destination numbers, and fire-off a HTTP request for every 100 destination numbers, i.e. about 270 HTTP requests! o_0

Do you perhaps know if the REST API support a separation character? I don't want to revert to the legacy API or go SFTP or direct SQL.
 
Just an update should you come across this post,

After testing and debugging, I've concluded that the RESTful API only allow for one destination (recipient) per message object, it does allow for up to 100 message objects to be batched in a single HTTP request.

For large volumes of messages with the same message body to, use the SFTP interface. The interface also allow for templates and declaring variables that may be populated from another data source.

hope this helps!
 
I dont think the RESTful API is intended for bulk exchange of data. I may be wrong. We only use it for for single transaction processing. For larger feeds we also use SFTP. I doubt that strategy will change.

We had a situation where a service provider would only accept HTTPS using WDDX. But our processes where batch. What we did was break up the message into 32k batches. We would end up sending a few hundred batches at 1am every morning. It wasnt great. We recently terminated the agreement(not because of this), and I can tell you all of us in our dev team where glad to see the back of that one :)
 
Are you connecting via some WASP or do you have direct access to an SMSC?
 
It's a website called smsportal.
Sorry Darko. I think if i read correctly I would have picked that up.

Your application seems to be A2P if I am understanding correctly (no P2A leg). You might want to consider SMPP interface that they also support. It takes in source MSISDN, destination MSISDN, Message body. I've used SMPP to send messages to over 1 mill subs.
 
Top
Sign up to the MyBroadband newsletter
X