0
Bulk SMS Services - HTTP Gateway Integration
Jun 21 2011 12:24 PM | AWS in Source Code
HTTP API to submit messages on SMPP:
:/bulksms/bulksms?username=XXXX&password=YYYYY&type=Y&dlr=Z&destination=QQQQQQQQQ&source=RRRR&message=SSSSSSSS<&url=KKKK>
: smpp1.kapsystem.com.com
: 8080 or 8000
Parameters are explained below, please note that all the parameters (especially message and url) should be URL-UTF-8 encoded.
Username: User name of the SMPP Account
Password: Password of the SMPP Account
Type: Indicates the type of message.
DLR: Indicates whether the client wants delivery report for this message.
Destination: Mobile Number to which to Send message to (may or may not include a ‘+’ sign), multiple mobile numbers can be separated by commas (note the comma (',') should be URL encoded).
Source: The sender address that should appear in the message
Message: The message to send
URL: If sending a WAP Push message (type=4), this holds the link that you wish to send, for any other type of message, no value needs to be supplied for this field (if specified will be ignored) . Just like “message” field, this field should also be URL encoded with UTF-8 character encoding (even for sending non-ASCII domain names).
:/bulksms/bulksms?username=XXXX&password=YYYYY&type=Y&dlr=Z&destination=QQQQQQQQQ&source=RRRR&message=SSSSSSSS<&url=KKKK>
: smpp1.kapsystem.com.com
: 8080 or 8000
Parameters are explained below, please note that all the parameters (especially message and url) should be URL-UTF-8 encoded.
Username: User name of the SMPP Account
Password: Password of the SMPP Account
Type: Indicates the type of message.
DLR: Indicates whether the client wants delivery report for this message.
Destination: Mobile Number to which to Send message to (may or may not include a ‘+’ sign), multiple mobile numbers can be separated by commas (note the comma (',') should be URL encoded).
Source: The sender address that should appear in the message
Message: The message to send
URL: If sending a WAP Push message (type=4), this holds the link that you wish to send, for any other type of message, no value needs to be supplied for this field (if specified will be ignored) . Just like “message” field, this field should also be URL encoded with UTF-8 character encoding (even for sending non-ASCII domain names).
0 Comments