Knowledge Base

Specifications

• Client Request
• API Response

Examples

• Example 1: A plain text message without any optional parameters.
• Example 2: A plain text message being sent to 6 recipients (one of which is not supported by the chosen route) with many optional parameters being used
• Example 3: Two different messages being sent to two different recipients.
• Example 4: A vCard being sent to a Nokia phone.
• Example 5: A Unicode message.
• Example 6: A plain text message without any optional parameters being sent via USA Direct.

If the routine was executed successfully, the body of our response will be in XML containing several pieces of information, as described here:

The messageID allocated to an individual recipient is the sequential position in which the recipient came. smsID's are made by combining broadcastID's and messageID's and so applications that need to allocated smsID's to individual messages should pair the broadcastID, e.g. MT0017295001, with the sequential position of the SMS. For example, if there were three recipients for a message, the smsID's would be MT0017295001-1 for the first one, MT0017295001-2 for the second and MT0017295001-3 for the third.

However, this does not apply to messages which exceed that maximum length and must therefore be split up as part of a long messaging procedure. Although we will aim to solve this issue in future releases, the only way to know the messageID for the different segments of a long message is to split them up before sending them.