We offer you flexibility, reliability, and most importantly, speed to market

What can you do with Programmable SMS?

  • Enable back-end systems to send SMS
  • Send OTPs & passwords
  • Marketing initiatives
  • Notifications & alerts

Features & benefits

Transactional SMSs

Send OTPs, login notifications, once-off messages etc.

Messaging Personalization

Send unique messages to individual recipients.

Reply Functionality

Receive and manage replies from recipients.

Custom Data

This feature enables replies to be linked to the original message for easy organization of data.

Message Scheduling

Schedule messages to be sent at predefined date and time.

Test Before Send

Make use of an HTTP tester to ensure your messages display correctly before you send.

Various APIs

A few of the interfaces we support include HTTP/S, SMTP, FTP, SMPP and MQ.

Reports

View the status of sent messages & statistics about your campaigns via the web-based reporting interface.

Pricing

Standard SMS rates apply.

A quick comparison of a few of the APIs we support:

HTTP FTP SMPP MQ SMTP
Description Simple & fast. Most frequently-used API Upload an XML file to an FTP server Simplifies integration of data apps with wireless mobile networks Queuing-based data exchange mechanism from IBM Send an email to our server to send SMSs
Ideal for real-time messaging Yes Yes Yes
Suited for high volume sending Yes Yes Yes
Ideal for preventing loss of data at all times Yes
Ideal for email to SMS Yes
Ideal for SMS from external system, app, or website Yes

HTTP/S APIs

HTTP to SMS

  • Enables corporate IT systems and applications to communicate via SMS including WAP Push.
  • Use it by posting XML data over HTTP/S.
  • Receipts and replies can automatically be sent back via HTTP/S to a specified URL.
  • Grapevine’s most frequently-used API.

SMS to HTTP

  • Receive SMSs from mobile phone users.
  • Typically the mobile user sends an SMS to an advertised 5-digit shortcode number.
  • Incoming SMSs are received and converted to XML, then posted via HTTP/S to a specified URL for processing.
  • An automated SMS response can immediately be sent back to the sender to acknowledge receipt of their message.

SOAP

  • Grapevine provides a SOAP Web Service for developers who prefer the ease and simplicity of submitting SOAP packets over HTTP/s for SMS delivery.
  • SOAP provides a great way to communicate between applications running on different operating systems, with different technologies and programming languages.

REST

  • A RESTful interface to the Grapevine messaging platform

FTP APIs

FTP to SMS

  • FTP to SMS enables any external system, application or website to send SMSs.
  • A text file containing mobile numbers and messages is posted using an FTP client to a specified FTP site. The file is picked up and converted to a bulk outbound SMS.

sFTP to SMS

  • sFTP to SMS enables any external system, application or website to send SMSs using SSH for secure file transfer between the company application and Grapevine.
  • A text file containing mobile numbers and messages is posted using an sFTP client to a specified sFTP site. The file is picked up and converted to a bulk outbound SMS.

SMPP APIs

  • The Short Message Peer to Peer (SMPP) protocol is designed to simplify integration of data applications with wireless mobile networks. Currently Grapevine supports SMPP 3.4.
  • Use our SMPP API for sending high volume, high priority SMSs directly from our messaging gateway via one or more binds or binary socket connections.
  • The standard SMPP protocol does not require a programming interface if you have SMPP software installed.
  • SMPP allows for transmitter only, receiver only or transmitter & receiver connections.
  • Please read the SMPP 3.4 specifications for further information.

MQ Series API

  • MQ Series / WebSphere MQ is IBM’s implementation of a queuing-based data exchange mechanism between systems.
  • This mechanism offers the most reliable and fault-tolerant protocol between mission-critical systems to ensure business continuity and prevent loss of data at all times.

SMTP APIs

SMTP to SMS

  • Easy for developers who are already using email messaging, to also send SMSs.
  • Receipts and replies are sent back via HTTP to a specified URL or via SMTP to specified email addresses.

SMS to SMTP

  • Receive SMSs from mobile phones as emails.
  • Incoming SMSs are received and converted to XML then sent via SMTP to specified email addresses.
  • Route the message to a particular email address based on the content in the message (i.e. a unique keyword) and automatically send an SMS response back to the sender acknowledging receipt of the message.
  • The incoming SMS is either a reply message or an SMS sent to an advertised 5-digit shortcode number that is converted into an email.

Find out how Programmable SMS can add value to your business

Contact us