SMS Enable any business application in minutes
Sendmode’s SMS API Gateway will SMS-enable any site or application. In a few simple lines of code you can connect your application to the mobile world. You can do this using any programming language (.NET, PHP, Java etc) and you will be up and running in minutes.
Our sms gateway is fast, secure and reliable ; we provide full documentation with technical support 24/7. We also provide all Delivery Reports which can be sent to a URL of your choice or you can pol the service to retrieve your reports.
Access to our Developer SMS API Gateway is completely free, you only pay for the SMS you send. Also when you sign up we will give you 25 free credits to get you started.
There are a number of ways to use the SendMode SMS API Gateway;
HTTP
HTTP is the method most commonly used by developers to SMS-enable their new and existing applications. A standard HTTP GET or PUT request can be used to transmit one or many text messages.
Outbound messages are sent by calling a specific URI, containing parameters relating to the message. The response to this call is a an XML string containgin True if message was accepted or False, with an error message if it was not. Issues such as missing parameters, innsufficient credits and authentication errors will result in a message being rejected. Once accepted, the message is processed and either sent immediately or at the time specified in the request.
DLRs (receipts) are provided indicating successful or failed delivery of the message. These are generated, in most cases, by the handset, which acknowledges receipt of the message from its local network. This acknowledgement is than passed back through the network as a delivery receipt. Within the SendMode API call which was used to send the message, the application can provide a URI to which the receipt should be sent. This URI can contain custom parameters to allow the application marry incoming receipts with the relevant out bound message.
All outbound messages and receipt status can also be accessed via the SendMode outbox, either through the SendMode website, or programmatically through an enhanced HTTP API call.
Inbound messages/replies can be routed in accordance with a per-account setting, to a specific URL on the client’s server, to an email address, to a cell phone number, or simply to the SendMode inbox, for later retrieval by the client/application.
SMTP
Email to SMS works very well in legacy environments, or on systems with limited networking capabilities. Any application capable of sending email can take advantage of our Email to SMS Gateway. Outbound messages can be sent as email to @SendMode.com and provided relevant security requirements are met, an email sent in this manner will be converted to SMS and delivered to the specified. Account-level settings can be used to control such things as whether or not the subject line is parsed or ignored, and what the maximum length of the payload can be on such a message.
Delivery Receipts (DLRs) can be sent back to the sending application, also via SMTP. Some form of handling function would be required on the application-side to parse these receipts.
SMPP
The Short Message Peer to Peer (SMPP) protocol is an open industry standard messaging protocol, and is one of only a few standard methods for the transmission and receipt of SMS text messages. SMPP is generally used for high volume applications, where low overhead provides high throughput. Where traffic levels are expected to consistently exceed 4-5 messages per second, and where specific functionality not available in the HTTP API is required then SMPP can be considered.
