Today I tried my hands on using Xoxzo API to send SMS and make calls, including text-to-speech and conference call, and trying out the telephony utility function, ie: carrier lookup. First of all, I signed up for a trial Xoxzo account, and was given 50 complimentary credits to try it out.


I created my first API User, and obtained my “API SID” and “Authentication Token” which will be used in the commands that follow.

apiexp2 apiexp3

Next, I downloaded CURL to my laptop. Since I am using an Intel processor with Windows OS, I chose the specific executable file that is compatible with my laptop specifications. Then I executed all the commands from the Windows Command Prompt in the directory (folder) where I store the CURL executable and library files.

For anyone familiar with the Command Prompt, all you need is the CD command to navigate, and everything else is CURL function. For the reader who has never used Command Prompt before, you may consider spending an hour or so checking out a user manual and figuring out how to use Command Prompt. You really only need to practice using the few commands for CD (change directory).

I decided to start with Voice API – Audio File Playback API. I found an MP3 audio file playing harpsichord music with a URL pointing to it, this is a pre-requisite to run the API. I modified the commands from the Xoxzo tutorial to suit my situation. Here’s the command I issued, followed by the screenshot from my Command Prompt:

curl -u <API SID>:<Auth Token> --data-urlencode "caller=+60xxxxxxx" --data-urlencode "recipient=+81yyyyyyyy" --data-urlencode "recording_url="


A Call ID was displayed on Command Prompt. Then my phone started to ring. I answered and heard the harpsichord music playing through my phone.

Immediately after the successful voice call, I checked the call status using the Check Call Status API, by specifying the Call ID displayed on Command Prompt. Here was the command I issued, followed by the screenshot:

curl -u <API SID>:<Auth Token>


I checked my Xoxzo account, my credits were deducted by 16, and I was left with 34 credits, here is the screenshot:


I no longer have enough credits to test out other Voice APIs, such as Text-to-Speech and Conference. The minimum required credits is 40. When I attempted to make a Text-to-Speech voice call, it failed.


So, I tried sending SMS next. This was the command I issued, followed by the screenshot of the Command Prompt:

curl -u <API SID>:<Auth Token> --data-urlencode "sender=XoxzoBlog" --data-urlencode "recipient=+81yyyyyyyy" --data-urlencode "message=Hello world, this is my first SMS sent over the Xoxzo."


The Message ID was displayed after my command. Subsequently I issued this command to check the SMS status.

curl -u :


Meanwhile the SMS notification ringtone was audible on my mobile phone. I received the SMS sent from the web:


With less than 50 credits, I was still able to try out Telephony Utilities API – Carrier Lookup API. I used a Japan mobile number and a Malaysia mobile number to try out this function. The commands I issued and the screenshot:

curl -u <API SID>:<Auth Token>  --data-urlencode "recipient=+81yyyyyyyy"


The Japan number I entered was subscribed from Asahi Net, an MVNO. The MVNO was not displayed, instead the actual infrastructure owner was displayed, in this case, NTT Docomo. The Malaysia number I entered had been ported to a different carrier (Celcom), in this case Maxis was displayed which was the carrier before porting. I am aware that the MNP (Mobile Number Portability) is supported on a best effort basis and is dependent on the end carrier, so in my case it is not reflected.

When I entered a fixed line number, all the parameters returned were ‘null’. This function is only meant for mobile numbers. This function can be used to check validity of a mobile number, whether it is still in use.


Mobile numbers from any country is supported, I tried out a few more mobile numbers in various continents from my phone book, they all returned results. Screenshots are omitted for brevity, clarity, and confidentiality purposes.

(to be continued)

Ai Sin Chan

Ai Sin Chan


Joined April 2018. Trained and grew with telco engineers in 16 countries spanned over 4 continents, and written more than 10 manuals in the process. Spent a decade specializing in mobile technology. Crafts her creation with passion.