Difference between revisions of "MOIntro"
| Line 30: | Line 30: | ||
* Create HTTP-POST listener in your server. Make sure it is on a publicly accessible web server (i.e. external services can access your application) | * Create HTTP-POST listener in your server. Make sure it is on a publicly accessible web server (i.e. external services can access your application) | ||
* Login to your account and click on the Contact Us link. Paste the URL into the body of your message and request that we configure your account | * Login to your account and click on the Contact Us link. Paste the URL into the body of your message and request that we configure your account | ||
| − | * Once you receive confirmation of this completion, you will be able to receive messages in | + | * Once you receive confirmation of this completion, you will be able to receive messages in your application |
Latest revision as of 09:48, 5 October 2013
With our service you can collect incoming SMS messages from your customers and have these messages forwarded directly to your application using a common HTTP-POST protocol. Here a several examples:
- Voting
- VoIP Call origination
- Customer support
- Sales reporting
- Instant Messaging
- Telemetry and many more
To receive text messages, senders need a number to which they can send them. There are two options for you to receive incoming messages. You can use a
- Shared short or long code or
- Dedicated VirtualSMS or dedicated short code
Please contact us to discuss which option would work the best in your situation.
Incoming SMS messages are first directed into your account (Inbox). From there, these messages can be collected by your application in two ways: Push and Pull
1. Push
Messages received in your account are forwarded to you using email or HTTP-POST. This is the preferred method as you get messages immediately after they have been received. For this process to work you need to expose an HTTP-POST listener on your web server and let us know its URL. The downside of this method is in case your URL changes (for example you have dynamic IP address) forwarding to your application will stop as we will unable to locate the URL that was provided - for as long as you do not update the URL with new IP address. Also, this method is sensitive to firewall settings (you will need to expose the web server which may be behind the the firewall - make sure the port is open). See below links for details on using HTTP-POST:
PLEASE NOTE - YOUR APPLICATION MUST IMPLEMENT HTTP-POST processing NOT HTTP-GET
Step-By-Step Process to Get You Going
- We assume that you already created an account and have sending using API working
- Create HTTP-POST listener in your server. Make sure it is on a publicly accessible web server (i.e. external services can access your application)
- Login to your account and click on the Contact Us link. Paste the URL into the body of your message and request that we configure your account
- Once you receive confirmation of this completion, you will be able to receive messages in your application
2. Pull
Your application can also collect messages from your online account in periodic intervals. This is preferred if you do not have an application that can be exposed to the Internet or if your IP address changes often so that it is not practical to keep updating your IP/URL settings. The downside is that you need to poll for new messages every so often (no more than 2 minute intervals are allowed), which means that delivery to your application may be slightly delayed.
There are two methods for getting your messages.
Using SOAP method GetNewInboxMessages or using standard POP3 protocol.
