The SMS Push API is used by our system to notify your system when a message arrives. In the same way that your system interacts with EMS through a known interface to send a message, EMS interacts with your system to push a received message to it.
To set up this service, you will need to implement an Internet accessible service that conforms to our Account Event Handler specification. There are both HTTP Form Post and XML Web Service (SOAP specifications for this service. Instructions and examples are contained in the SMS SDK for your development environment.
Once set up, you then need to configure your account to use the service via the API section of the Options page in Web SMS. In here you specify the URL of you service and the version of API you have implemented.
Retry
In the event our system is not able to access your system, a retry and notification strategy is employed. The message remains in your accounts Inbox until you explicitly delete it. It is recommended that your system deletes the message from the Inbox once received, in effect completing the delivery transaction. If this procedure is followed, it is thn very easy for your system to assess any messages it has missed should it experience a planned, or unplanned, outage.
Details of the retry strategy can be found in Retry Process.
Security
EMS is able to support SSL encrypted communication between EMS and your system through use of a certificate certified by one of the well know Root Authorities, eg Verisign, Thawte, etc. The API configuration section on your account also allows you to specify a username and password EMS is to use whenever communicating with you system.
The SMS Push API pattern is the most performant and robust approach to message receipt and is the recommended approach for any interactive messaging applications.