Difference between revisions of "MT HTTP"

From SMS Wiki
Jump to: navigation, search
(New page: == Sending an SMS via SOAP, HTTP POST or HTTP GET == 1. Get your token and signature 2. Send message To get your token visit or make a call to: http://api.upsidewireless.com/soap/Authen...)
 
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
== Sending an SMS via SOAP (HTTP) ==
  
== Sending an SMS via SOAP, HTTP POST or HTTP GET ==
+
EnterpriseSMS API uses SOAP to authenticate requests and send SMS messages.  Sending of SMS messages is done in two steps:
 +
* [[Authentication | Get your token and signature]]
 +
* [http://api.upsidewireless.com/soap/SMS.asmx  Invoke a function to send message]
  
1. Get your token and signature
 
2. Send message
 
  
To get your token visit or make a call to: http://api.upsidewireless.com/soap/Authentication.asmx?op=GetParameters
+
----
To send your message visit or make a call to: http://api.upsidewireless.com/soap/SMS.asmx?op=Send_Plain
+
== Notes ==
 +
* 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
 +
* NEVER use IP address to make API calls as it may change without notice. Always use domain name
  
Sending VIA SOAP is the recommended 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 be fiercely avoided as it is fraught with problems (string length, encoding issues).
 
  
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.
+
----
 
+
[[APIs | back]]
To see a full set of functions that are available for sending SMS, please visit http://api.upsidewireless.com/soap/SMS.asmx
+

Latest revision as of 15:31, 2 March 2011

Sending an SMS via SOAP (HTTP)

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



Notes

  • 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
  • NEVER use IP address to make API calls as it may change without notice. Always use domain name



back