Cor Cronje
Active Member
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.
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.