SMSified is a simple API for sending and receiving text messages using regular phone numbers or short codes. SMSified uses a simple REST interface based on the GSMA OneAPI standard and is backed by Tropo, Inc - the worlds largest communications cloud.
In order to send and receive text messages, SMSified utilizes three standard HTTP methods and works with two data formats:
POST is used in SMSified for three things:
1. To send text messages - you post the message and destination to us, we deliver the message to the destination.
2. To receive delivery notifications - you post the URL you want to receive notifications at, creating an outbound subscription, and we post the notifications back to you.
3. To receive text messages - you post the URL you want to receive messages at, creating an inbound subscription, and we post messages that come in back to you.
GET is used primarily with SMSified’s reporting. You can retrieve information about a particular SMS or multiple SMS messages, as well as filter the results. GET is also used to retrieve information about subscriptions.
DELETE is only used to remove a subscription.
When making a request to SMSfied, use form-encoded requests (just like submitting an HTML form). All responses will be in JSON with an application/json content-type; callbacks sent to your server for incoming messages or delivery notifications will also be JSON.
SMSified utilizes an abbreviated list of HTTP Response Codes to report the success or failure of a POST or GET request; this includes 200 OK & 201 Created for success, as well as a few others to indicate problems like an invalid request body or incorrect headers. Click here to view the complete list.
When reporting on delivery status, the API response contains a code element that will indicate 0 for success or the reason for the message failure; click here to view the complete list of possible code values.
SMSified supports either HTTP or HTTPS, completely up to you. Using HTTPS to encrypt all requests through SSL isrecommended, but if you're using a client and tool that's not set up to make SSL requests, you can use HTTP. All requests are secured through BASIC authentication.
SMS short codes are available and require approximately 90 days to register with the SMS carrier networks; there's an application process that we'll help you through. Costs include a $3000 USD setup fee and $750/month (prepaid in 3 month increments). Our $0.01 per message rate applies to short codes, same as it does for 10-digit numbers. The short code you receive will be randomly assigned by the carriers; if you have a specific short code in mind, the monthly cost would be a bit higher.
Standard 10-digit numbers are restricted by the carriers to 1 message per second (60 per minute) per originating phone number; this cannot be increased. Short codes, however, can send up to 40 messages per second (2400 per minute). In all cases, if your outbound traffic exceeds these restrictions, the messages that exceed the limit will be queued and retried up to five minutes before the messages are dropped. If the provider network is down instead, SMSified will retry your message up to four hours before giving up. Assigning a callback URL - either through the use of an outbound subscription or on a case by case basis using the notifyURL parameter - will ensure you're aware if a message gets dropped.Duplicate messages sent within one minute will also be filtered, for both long codes and short codes. A "duplicate message" is defined as the same destination address, sender address and message body.