mfitzp
Make this an api
I would love to work with you on turning this list into an open API. I was looking for a free method of doing basic one-way messaging services. Stuff like text messaging users registration codes...or one way updates/notifications for specific things that users opt'd in for.
PM me if this is something you would like to do or work on or think we could get others to help contribute. Would sure beat the heck out of all the paid sms services for just simple <160 character messages.
@rolinger thanks for the suggestion — it's something I'm open to, and have thought about implementing in the past. There are a few issues though —
- There is no simple way to determine the correct network (and therefore email address) from a submitted phone number, since numbers can be moved between networks (happens in the US and UK at the very least). Sending to the original operator won't work.
- Spam — if you're suggesting providing an API to send the emails(?) — if you just want an API to return the email address for a given number that's not a problem.
- Running costs for providing the API (though it might be possible to run it on a free server if the number of requests are low, e.g. Heroku minimal install)
What are your thoughts on the above? You can [drop me an email](mailto: [email protected]) if you want to discuss privately.
HI Martin,
I can see an API working from multiple perspectives, each with their own challenges. My first take was from mobile apps. In the mobile environment the app developer can retrieve the carrier...that carrierName/Number could be passed to the API to determine an email solution - this would negate having to determine which phone number existed on which network. The API could either send the email on behalf of the requesting mobile App or return the proper email address to the App for the developer to use as they see fit - send an email from the App (not ideal because that typically requires more user interaction) or the App could send that down to their own server and the developer's server could send the email.
As far as a gateway is concerned to determine which number existed where, I am certain some solutions exist because I was able to find a free API that I was able to embed in my mobile app that doesn't require 'carrier' info...just number and a message. They only allow 75 messages per day (thats a lot) from any given IP address and only a max of 3 messages within any 3 minute period. (http://textbelt.com). If we were to create something similar we could provide an API that embeded into a mobile app or into a web page that initiated the API call from the client side (unique IP).
