| WAP Push Advanced without Web Form |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through November 14, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8071 Registered: 10-2002 |
A recent tech support e-mail asked how to directly submit WAP Push messages via HTTP instead of using the "Send WAP Push Advanced" web form (http://www.nowsms.com/doc/web-menu-interface/send-wap-push-message). The "Send WAP Push Advanced" form builds an HTTP GET (POST also allowed using Content-Type application/x-www-form-urlencoded) and submits the following HTTP variables. PhoneNumber - Recipient phone number or distribution list name. This field can contain a comma delimited list of recipient phone numbers and/or distribution list names. WAPPUSHADV_CONTENT_TYPE - MIME content type of the content to be pushed. WAPPUSHADV_CONTENT - The content of the push. The content can either be encoded as plain text, or for binary content types the content can be represented as a string of hexadecimal characters. WAPPUSHADV_CONTENT_ENCODING (Values are Text, Hex or XML) - Specifies whether the content is plain text or a string of hexadecimal characters. If you are sending one of the content types supported by “Send XML Settings”, but wish to include extra headers, it is also possible for NowSMS to perform XML to WBXML conversion for any of the XML content types supported by “Send XML Settings”. If you wish to have NowSMS perform XML to WBXML conversion, select this conversion option for “Content Encoding”. WAPPUSHADV_XWAPAPPID - Optional, can contain a numeric identifier or text string to indicate a destination WAP Push application id. WAPPUSHADV_HEADERS - Optional, can contain a list of additional headers to be included in the WAP Push WSP header. Each header should be on a separate line, with a format of Header-Name: Header-Value. As an alternative to text encoding, WSP headers can be specified directly using with hex string encoding. When NowSMS encounters a line of hex characters in the “Additional Headers” field, it assumes that this a pre-encoded WSP header value, and the binary equivalent of the hex string is included in the WSP header without any validation. OTAPIN and OTAPINTYPE - Optional parameters defined at http://www.nowsms.com/doc/submitting-sms-messages/url-parameters | |||
