It would be more useful if the list has inbound/2-way, raw PDU, long/shortcode, sender ID etc.
Telephony, SMS, and MMS APIs
31–40 of 49 posts
Re: Telephony, SMS, and MMS APIs
#32wow, i'm out of the loop. what is everyone building with these types of APIs?
Two factor authentication and notifications of any type would be the two things that come up in my mind first.
Re: Telephony, SMS, and MMS APIs
#33For those of you that don't want to code interactions (going beyond simple notifications) via SMS & especially Telephony/IVR calls - and also let your business team members build and manage these interaction flows via a browser instead, check us out: https://www.engageSPARK.com .
Developers use our Subscription API to trigger an interactive SMS or IVR call campaign (that they've built via our website first) - by simply sending us the campaign ID and the recipient's phone number. This saves them days/weeks of coding to Twilio/Plivo/etc's APIs and they offload all changes to the interaction flows to their business team members. We've been used in 80+ countries, including by Intel and UN WFP. :)
Re: Telephony, SMS, and MMS APIs
#34We have an API for sending bulk SMS and libraries written in PHP, NodeJS, Python, Ruby, Java, C#, Go and Rust. You can try out the API and send some test messages to your phone straight from your browser at: https://zensend.io/#demo .
We have the most experience in the UK market because this is where we do most of our premium sms/direct billing business under another company (http://www.fonix.com/) but we support bulk messaging to a lot of different countries (https://zensend.io/pricing).
Re: Telephony, SMS, and MMS APIs
#35Thanks for putting this list together!
Re: Telephony, SMS, and MMS APIs
#36Dev from ClockworkSMS here.
Just want to correct this list, as we definitely do support SSL, and we've just upgraded the certificate: https://www.clockworksms.com/blog/ssl-sha2/
If SSL isn't enough, we can also do VPNs directly to our (only UK based) datacentres.
Feel free to ask questions if you have them. We've got good links to the US and great coverage throughout the rest of the world
Re: Telephony, SMS, and MMS APIs
#37It would be good to know which of them support international numbers, or how many country it covers
Seconded. (I am targeting Asia and Africa.)
Re: Telephony, SMS, and MMS APIs
#38wow, i'm out of the loop. what is everyone building with these types of APIs?
Two factor authentication and notifications of any type would be the two things that come up in my mind first.
More: allowing contact from offline users (newspapers, tv, radio) and interacting with them, mobile payments.
Re: Telephony, SMS, and MMS APIs
#39The data appears to be culled from ProgrammableWeb.
correct. I had my outsourcer do it. not sure if they scraped it or used LinkKlipper.
Really fascinated of this kind of semi--outsourced work procedure. Outsource the manual data entry to somewhere else for a minimum cost and then focus on your core strengths alone.
Re: Telephony, SMS, and MMS APIs
#40I really wish people would more clearly distinguish library APIs from RPC APIs exposed by corporations' servers. I have no desire to deal with another company but I would love an open-source library implementing the client side of MMS, or at least some readable documentation about how the hell it works.
Do you have example of potential alternative naming schemes?
I would refer to these as "services" and "libraries"; referring to either as an "API" is conflating a tool with its interface.