Assistance Needed: SMS Integration Issue

Dear Members,
I’m currently facing an issue with SMS integration, and I could use your expertise and experience on this matter. I’ve followed the integration tutorial provided in the KB article (4.35. How to Apply SMS Sending Implementation on SambaPOS? – SambaPOS Knowledgebase).

The required API URL format from the KB tutorial is:

However, the URL provided by the operator works in both the browser and the software:

When I remove the message and phone number parameters, the SMS fails to work. The operator mentioned that “message=&destination=&source=” are standard variables for all regions and can be changed, but we need to verify this from our end.

I would greatly appreciate any assistance or insights you can provide to resolve this issue.

In the latest version of Sambapos we have simplified this with Twillio. We have an action for using twillio. Would this be something you are interested in using?

Hi Jesse,

I’m currently exploring our options for SMS API providers in the Dubai region. We have a reseller contract with Route Mobile LTD, and I’m curious to know if the Twilio API is compatible with this region. I’d appreciate your insights on this matter and any suggestions you may have regarding the best option for us.

Thank you for your assistance.

I am not sure if it is you can definitely check in their website. We built an action so you can easily integrate it. Twillio is popular all over the world.

I will check with them what will be the prices structure and get back to you

Thank you😊

Is it possible that we can make the action for the route mobile API also?

Anything is possible but we have limited resources so we need to make sure a lot of people all over the world can use it. We definitely do specific integrations for countries if demand is there and it makes sense.

I can tell you honestly though unless it’s a very large immediate demand I would not expect it any time soon. The twilio integration should cover what you need.

You don’t understand the concept of what you are supposed to be doing here. You need to follow the format of the API you are using, you can’t just copy and paste the code from the tutorial, change the domain name and then use the same parameters as the tutorial, you need to adapt it for the new API. The example given uses text for the message, recipients for the number, whereas your API uses message for the message, destination for the number. It is a pretty simple process to do that, but if you don’t understand, I would suggest you just use the Twilio integration


I have tried the following URL format provided by you:

However, it is not working. I checked with the operator, and they informed me that they have already made adjustments to the API as follows:

  1. Updated the special character to “@” instead of “%40”.
  2. Reordered the parameters in the API.

Below is the working API for your reference:

Please note that we cannot change the headers of the parameters in the API, you have to do the changes at your end, instead of “Sender” you need to replace it with “Source”.

I have tried the updated URL with these changes:

Please let me know where I might be going wrong.


1 Like