SMS-MT Example of Sending Text Messages
Here is a complete example for a valid SMS-MT request using ValueFirst XML API.
Authorisation Method: Bearer Token
Request: POST
New parameter Templateinfo:
- New Parameter TEMPLATEINFO has been added for which will contain the template id and variables value to be replaced in template text. Template info parameter will have ~ separated values.
- If both TEXT and TEMPLATEINFO is given then priority will be given to Text.
- New error code i.e. INVALID_TEMPLATEINFO = 28694; has been created for error if occurred any , related to TEMPLATEINFO parameter, which include like invalid templateid is provided,variables count mismatch than the template Text variables count, template text not found for the given template id.
The following table describes the different elements of a SMS-MT request.
| Tag Name | Description |
| Users | |
| ENTITYID | DLT Principal Entity Id. This is an optional parameter. |
| SMS | |
| UDH | UDH is used for sending binary messages. For text message the value should be 0 |
| CODING | Extended type of messages. For text message the value should be 1. |
| PROPERTY | Unique property of message. Default value is 0. For sending Flash SMS the value should be 1. |
| ID | Unique ID of message. The client sends this value. In future communication, server sends this value back to the client. |
| TEXT | This field describes the message text to be sent to receiver. SMS can contain up to 160 characters in Message Text. API allows user to send message text of more than 160 characters. Credits will be deducted in the multiple of 160 characters according to the length of SMS |
| TEMPLATEINFO | This will contain the template id and variables value to be replaced in the template text. Template info parameter will have ~ separated values Format is
NOTE: This is a manual process, the template id will be provided by VF. |
| SEND_ON | It is now possible to schedule a message. To schedule message to go at a later time, user can specify “SEND_ON” date as attribute of SMS tag. Only absolute date is supported. The value should be given in “YYYY-MM-DD HH:MM:SS TIMEZONE” format. Time zone is difference w.r.t. to GMT. Please refer Scheduling Support for more information on this feature |
| DLTTEMPLATEID | DLT template id. This is an optional parameter |
| DLTCONTENTTYPE | DLT Content type. This is an optional parameter. Only numeric value is accepted. (1: Service Implicit, 2: Service Explicit, 3:Transactional, 4:Promotional) |
| ADDRESS Describe the Sender as well as Receiver address | |
| FROM | The Sender of the message. This field should conform to Sender Phone Number guidelines |
| TO | Person receiving the SMS, should confirm to Receiver Phone Number guidelines. |
| SEQ | SEQ uniquely identifies the ADDRESS packet. SEQ can be alphanumeric & its not mandatory to be unique & it is optional. |
| HEADERID | DLT Header Id. This is an optional parameter |
| TAG | A text that identify message. This is an optional parameter. |
| Tag1 | %TAG1 |
| Tag2 | %TAG2 |
| Tag3 | %TAG3 |
