Difference between revisions of "MT HTTP"
From SMS Wiki
| Line 3: | Line 3: | ||
EnterpriseSMS API uses SOAP to authenticate requests and send SMS messages. Sending of SMS messages is done in two steps: | EnterpriseSMS API uses SOAP to authenticate requests and send SMS messages. Sending of SMS messages is done in two steps: | ||
* [http://api.upsidewireless.com/soap/Authentication.asmx?op=GetParameters Get your token and signature] ''(this is done once, or after account password is changed)'' | * [http://api.upsidewireless.com/soap/Authentication.asmx?op=GetParameters Get your token and signature] ''(this is done once, or after account password is changed)'' | ||
| − | |||
* [http://api.upsidewireless.com/soap/SMS.asmx?op=Send_Plain Send message] | * [http://api.upsidewireless.com/soap/SMS.asmx?op=Send_Plain Send message] | ||
| Line 10: | Line 9: | ||
== Notes == | == 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). | * 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. | * 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 | * 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. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | [[APIs | back]] | ||
Revision as of 21:43, 8 May 2008
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:
- Get your token and signature (this is done once, or after account password is changed)
- Send message
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
- 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.
