Knowledge Base

SMS API 2.1

Sub-categories

  1. Broadcast
    The routine used to submit MT SMS.
  2. Check_Balance
    The routine used to query credit balances.
  3. Check_Destination
    The routine used to query the availability and delivery rate for individual countries.
  4. Check_Keyword
    The Client-API routines through which the avilibility of keywords on shared numbers can be queried.
  5. Check_Status
    The routine used to query the delivery state of MT SMS.
  6. Respond
    The routine used to simplify the MO response process.

 

Articles

Frequently Asked Questions


Article

v2.10 Release Notes 26/06/06

SMS API v2.1 has been released in "beta". Its direct predecessor is SMS API v2.03 and these are the direct changes/developments which it has been benefitted by:

General

  1. The "version" parameter has become mandatory on all routines.
  2. The way in which our response is made now uses XML. This has allowed us to simplify routines and provide more detailed results.
  3. Support has been introduced for the new USD credit balances as well as forward compatibility for further currencies.
  4. Support has been introduced for our new direct connections with US network operators.
  5. The case-sensitivity of parameters has been removed.
  6. The documentation has been moved from PDF format to the Knowledge Base to allow for additions, especially the frequently asked questions of other users.
  7. The use of Processing Error Codes has been introduced.

Broadcast

  1. Support for binary data & UDH has been introduced.
  2. Support for Unicode characters has been introduced.
  3. Support for long messaging has been introduced.
  4. Support for expiry dates has been included.
  5. Support for subscription services has been included.
  6. The API response now provides the broadcastID, the total number of recipients in the broadcast, the type of balance used, the number of credits remainng in the balance and the messageID's for those messages which were neglected. Furthermore, even though these useful values have been introduced the average total size of the response has decreased significantly.
  7. The use of old-style route names/codes has been discontinued; "busi" is now "GD02" and "frst" is now "GD01".
  8. The prohibition from using pipe characters within custom data and message bodies has been discontinued. However, in order to use pipe characters, they must be escaped.

Check_Balance

  1. The API response now provides the balances for the different balance types.

Check_Route

  1. The need to specifiy an individual route has been removed.
  2. The API's response now provides details for each possible route.
  3. The 'msisdn' parameter has been renamed 'to' as it is more relevant and accounts for the querying of international dialling codes and other non-MSISDN numbers.

Check_Status

  1. The 'id' parameter has been renamed 'smsid'.