API
ReachUmobile offers 2 interfaces and a .NET SDK. Documentation and test applications can be found under the download section
here.
Web Services (SOAP/XML) interface (Developer Edition)
The ReachUmobile Developer Edition offers a fully documented Web Services API Those developers who prefer not to use the ReachUmobile pre-built library for Microsoft platform environments can create their own service using the published Web Service WSDL. The ReachUmobile WDSL can be viewed here.
SDK for Visual Studio .NET (Developer Edition)
The ReachUmobile SDK provides developers with a messaging component that they can simply drag and drop into Microsoft's Visual Studio integrated development environment. Developers can design and code an application as usual, but then connect it to the messaging services that the ReachUmobile component offers. From there, it is a simple step to send messages to the ReachUmobile platform from within their application.
Developers enjoy all the features and benefits of the Visual Studio environment including:
- A consistent interface for all languages
- A choice of languages, including Microsoft Visual Basic .NET, Microsoft Visual C++ .NET, Microsoft Visual C# .NET and Microsoft J# .NET
- Robust code creation by re-using common logic
- Drag and drop functionality with Component Designer
- Rapid development using Windows Forms
- Seamless access to databases, message queues and event logs
Using the skills they already have, developers can use Visual Studio .NET 2005 to create XML Web services and rapidly build mobile applications.
HTTP interface (Web Edition)
The ReachUmobile Web Edition enables enterprises to send SMS text messages directly to the ReachUmobile platform using a simple HTTP Post. The API has no platform dependencies and therefore offers simple, efficient and fast integration with the ReachUmobile platform, it is the preferred choice for developers who need to get up and running rapidly without the need for detailed integration. One limitation of the HTTP interface for example is that message status is not supported. Instead all message statuses can be monitored through the portal Web interface.