Difference between revisions of "Main Page"
From SMS Wiki
| Line 11: | Line 11: | ||
* Full transaction auditing | * Full transaction auditing | ||
| − | This document explains integration methods for sending (Mobile Terminated SMS or MT) and receiving messages (Mobile Originated SMS or MO). You can find full documentation and coding examples of the API [[APIs | '''on the pages that follow.''']] | + | This document explains integration methods for sending (Mobile Terminated SMS or MT) and receiving messages (Mobile Originated SMS or MO). You can find full documentation and coding examples of the API [[APIs | '''on the pages that follow.''']] ''(WARNING - the following pages may not be suitable for non-technical audience. Viewer discretion is advised.)'' |
---- | ---- | ||
[http://www.upsidewireless.com back] to Upside Wireless home | [http://www.upsidewireless.com back] to Upside Wireless home | ||
Revision as of 09:22, 9 May 2008
EnterpriseSMS API was built for the purpose of easy integration of business applications with the global text messaging network. This API hides the complexity of telecom networks through the use of common application programming interfaces. In most cases, full integration can be completed within few hours.
Upside's EnterpriseSMS API offers:
- Simple and quick integration
- Two-way capability (MT/MO)
- Global network coverage
- High throughput (up to 100 messages per second)
- Full transaction auditing
This document explains integration methods for sending (Mobile Terminated SMS or MT) and receiving messages (Mobile Originated SMS or MO). You can find full documentation and coding examples of the API on the pages that follow. (WARNING - the following pages may not be suitable for non-technical audience. Viewer discretion is advised.)
back to Upside Wireless home
