Difference between revisions of "MTIntro"
From SMS Wiki
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | 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)'' | ||
| + | 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. | ||
| + | * [http://api.upsidewireless.com/soap/SMS.asmx?op=Send_Plain Send message] | ||
| − | |||
| − | + | ---- | |
| − | * [[MT SMTP]] | + | |
| + | == 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 | ||
| + | |||
| + | * [[MT HTTP]] | ||
| + | |||
| + | * [[MT SMTP]] ''(note: as of Jan 1, 2008 new customers can no longer use this method. Old customers are encouraged to switch to MT HTTP method)'' | ||
| + | Since some customers may opt for the latter all API calls use token and signature as proxies for username and password. | ||
Latest revision as of 21:27, 8 May 2008
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)
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.
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
- MT SMTP (note: as of Jan 1, 2008 new customers can no longer use this method. Old customers are encouraged to switch to MT HTTP method)
Since some customers may opt for the latter all API calls use token and signature as proxies for username and password.
