Difference between revisions of "MT HTTP"

Revision as of 00:55, 9 May 2008

EnterpriseSMS API uses SOAP to authenticate requests and send SMS messages. Sending of SMS messages is done in two steps:

We strongly recommend SOAP method as the input and output variables are strongly typed, however at times using HTTP POST or GET is the only option. HTTP GET should, however be avoided as it is fraught with problems (string length, encoding issues, etc).
When using HTTP POST, be certain to retrieve the result of the request as it will contain valuable data that will assist in determining the message state.
To see a full set of functions that are available for sending SMS, please visit http://api.upsidewireless.com/soap/SMS.asmx
Customers that prefer SSL connection please use the following base URL: https://secureapi.upsidewireless.com . All other features and examples are identical

@@ Line 11: / Line 11: @@
 * When using HTTP POST, be certain to retrieve the result of the request as it will contain valuable data that will assist in determining the message state.
 * To see a full set of functions that are available for sending SMS, please visit http://api.upsidewireless.com/soap/SMS.asmx
-* Since some customers prefer to use non-SSL method to connect to EnterpriseSMS API, token and signature as proxies for username and password so that you do not need to send them unencrypted over the Internet.
+* Customers that prefer SSL connection please use the following base URL: https://secureapi.upsidewireless.com . All other features and examples are identical
 ----
 [[APIs | back]]