API Message Parameters
The page will give you all required parameters for sending MT messages via HTTP.
When sending text SMS MT messages, the following parameters should be sent as part of the HTTP GET request:
| Parameter | Required? | Description |
|---|---|---|
USER_NAME/Account_ID | Yes | Username / Account_ID are interchangeable and will be provided to you by Mobivate |
PASSWORD/API_Key | Yes | Password / API_Key are interchangeable and will be provided to you by Mobivate |
ORIGINATOR | Yes | Phone number of the Originator / Sender of the message. Valid originator strings are: • Numeric originators: Numbers starting with 614xxxxxxxx • Shortcode originators: Numbers starting with 13, 18 or 19 • Alphanumeric originators: Up to 11 characters, where at least one of the 11 must be a letter (Alpha) For example: • • • |
RECIPIENT | Yes | Phone number of the recipient (mobile phone) in international format (MSISDN) For example: |
MESSAGE_TEXT | Yes | The SMS message to be delivered to the recipient. This field must be URL Encoded to ensure accurate interpretation of the message. For example:
|
PROVIDER | No | Identifies the telco provider (Telstra/Optus…) for Premium SMS Messages only For standard SMS messages, the field value must set to DEFAULT or left blank. For example: |
VALUE | No | Specifies the value of a Premium SMS message, in cents (this applies to all currencies). To be used only in conjunction with the PROVIDER field. For example: |
REFERENCE | No | Used by the sender to identify sent messages. Setting this field allows senders to easily track their messages For example: |
URL | No | When specified, the message will be sent as WAP Push. A link will appear on the handset showing the MESSAGE_TEXT parameter, and upon clicking the handset will be forwarded to the specified URL. This field must be URL Encoded. For example: |
STARTED | Yes (In Kenya & South Africa) | Contains the date of when the Subscription first started ( |
KEYWORD | Yes (In Kenya, South Africa, Ghana and UK) | Contains the product id (on the network side) to which the subscriber was subscribed. See Keyword Requirements below. |
DR_ENDPOINT | No | The URL that the delivery notifications should be sent to for this message. We still suggest using a globaly defined DR endpoint. This one overrides it. |
MESSAGE_CLASS | Yes | Declare the Message class. For unsubscription MT's this class is required to send unsubscription messages, ie. |
Last updated