Twilio Sent Me Here!
cloudwi.re is a certified Twilio partner and Twilio hosts the cloudwi.re short codes. You will not use the Twilio API to work with us. For developers referred to us from Twilio, there are some key differences between the Twilio API and the cloudwi.re SMS API to be aware of before you begin. They include:
The SMS API is built with compliance logic baked in. Mobile subscribers are assigned an opt-in status. If the mobile subscriber is opted-out or in pending status, you cannot send text messages to that mobile subscriber with the cloudwi.re SMS API. Only mobile subscribers that are opted-in to receive text messages from your store will get your content. In most cases, cloudwi.re blocks messages to subscribers in the opt-out or pending status, except for responder keywords, which send one text message to the mobile subscriber regardless of opt-in status.
The Twilio API will allow you to attach a callback URL to each message sent. The cloudwi.re SMS API is built on the store concept and allows one unique callback URL per store for which we will post ALL incoming messages too. You cannot assign a callback URL to the outbound message.
Twilio does not allow batch uploads of messsaging. To simplify tasks for the developer and improve message delivery speeds, cloudwi.re will accept batch uploads in a supported JSON array for SMS campaigns.
Twilio has a lot more money then we do, which means the infrastructure we are built on top of is well supported and comes with amazing uptime.
Yes, you can still use Twilio products while a customer of cloudwi.re. And you should. Twilio rocks! For example, if message deliverability is of the utmost importance, you can write an application that uses Twilio to call the Customer with a text 2 voice message after receiving a message failed error from the cloudwi.re SMS API.