Knowledge Base

SMS API 2.0

Sub-categories

  1. Broadcast
    The current (stable) version of our SMS API.
  2. Check_Balance
    The routine through which the GBP balance of an account can be queried.
  3. Check_Destination
    The routine through which the route availibility and delivery rate for a specific country can be queried.
  4. Check_Status
    The routine through which the delivery state of MT SMS can be queried.

 

Articles

Tutorials

  • How to upgrade from SMS API 1.0 to SMS API 2.0.

Tutorial

How to upgrade from SMS API 1.0 to SMS API 2.0.

Although there are many differences between the two versions of our SMS API, a simple modification to existing code can facilitate instant upgrades.

Previously, in SMS API 1.0, each Client-API routine had its own URL. However, with SMS API 2.0, only one url exists and the type of request is defined through the 'type' parameter.

Take, as an example, an HTTP request for an MT broadcast. With SMS API 1.0 it would look something like:

https://www.tm4b.com/client/api/send.php?username=abc etc.

However, the same request with SMS API 2.0 would now look like:

https://www.tm4b.com/client/api/http.php?type=broadcast&username=abc etc.

SMS API 2.0 is far more developed than its predecessor and the changes, including the possible definitions of the 'type' parameter, require its specifications to be read thoroughly.