v2.00 Release Notes - 19/09/05
SMS API v2.0 has been released in "beta". Its direct predecessor is SMS API v1.0 and these are the direct changes/developments which it has been benefitted by:
General
- Technical Manual received much improvement to provide maximum clarity and assist programmers and developers with minimal expertise.
- Removed the need for each Client-API having its own unique URL to the provision of only one generic URL (i.e. www.tm4b.com/client/api/http.php), defining the routine type by means of the ‘type’ parameter:
- ‘check_balance’ to check the current balance of your TM4B account.
- ‘check_destination’ to check the availability and delivery cost of a specific destination on a specified route.
- ‘broadcast’ to send single/bulk sms.
- ‘check_status’ to check the delivery status of a mobile terminated sms.
- Added a new routine called "check_destination" that checks the route availability for a specified destination and provides the cost of message delivery if applicable.
Broadcast
- Added the ‘custom’ parameter that allows 3rd party applications to associate their own data to an individual sms message that will then be provided along with the delivery reports as they are received. This allows applications to match delivery reports using their own specified data.
- Removed the case-sensitivity of the ‘sim’ parameter.
- Added the requirement for messaging routes to be named in full (i.e. “first & business”, not “frst & busi”).
- Named the combination of broadcastID & messageID as smsID.
- Removed ^ as a forbidden character.
Check_Status
- Added the ability to query the delivery status of mobile terminated sms by means of the ‘custom’ field.