Ask HN: What do you want out of a SMS gateway and API?
Hi, everyone!
We're thinking of putting together a new SMS API specifically catered to application developers and hackers. Our platform can handle two-way messaging, advanced routing, subscriptions and keywords, etc., but we've found that most of you don't really need all that additional "stuff". So we want to know what it is that you _do_ want out of an API.
Is the major determining factor the features of the API? Is it the price? Deliverability & reliability? Simplicity?
Is it something in between our platform with SMPP binds <http://privatelabelsms.com/api/> and PennySMS with SMTP connectivity <http://pennysms.com/docs>?
We'll take your feedback into account as we move forward.
(
4 comments
| 4 points
| on HN
)
2) give me my own dedicated number. i don't care if its 10 digits
3) price and simplicity are my two major decision factors, with price far and away #1.
Our API http://privatelabelsms.com/api/
Penny SMS http://pennysms.com/docs