Its a great list but what's the context?
Twilio's IPO just occurred.
Do you expect worse service because of the ipo?
Telephony, SMS, and MMS APIs
21–30 of 49 posts
Re: Telephony, SMS, and MMS APIs
#22I've done this before and HATED it. Outside the usa is a nightmare. I mostly used clickatell and tropo
Re: Telephony, SMS, and MMS APIs
#23If anyone is looking for an SMS REST API using a shared short code, check out: https://api.mobiniti.com/v1/docs
Re: Telephony, SMS, and MMS APIs
#24I 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.
Re: Telephony, SMS, and MMS APIs
#25I 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?
Re: Telephony, SMS, and MMS APIs
#26I'm currently using Nexmo for a side project, but am looking to move. I recently had to buy some more numbers and realized Nexmo had almost none available. Anyone have this issue with other providers?
Re: Telephony, SMS, and MMS APIs
#27I'm currently using Nexmo for a side project, but am looking to move. I recently had to buy some more numbers and realized Nexmo had almost none available. Anyone have this issue with other providers?
Nexmo's inventory especially for North America numbers has been an issue for a while. Are you using them for Voice, SMS, or both?
Re: Telephony, SMS, and MMS APIs
#28Since they're all pretty much the same, the main factor appears to be missing: price.
they don't all disclose price publicly and I'd probably get a takedown notice if I posted prices, b/c they can always change and that's misleading the consumers.
are you obligated to be accurate? I appreciate the list (thank you, or thank the curator) but I would imagine that if you are independent you have no obligation to be correct?
Re: Telephony, SMS, and MMS APIs
#29I've used both raw devices and 2 or 3 commercial SMS APIs to implement international SMS systems commercialy over the last 10 years: Middle East, Iran, Europe, East Asia, etc. IMHO the best are the ones that let you send raw SMS PDUs, which isn't that hard. If you want to do international SMS, and care about cost, then using non UCS2 encodings is a requirement. Without raw SMS PDU support, you are basically screwed. Swedish 42IT AB[0] was a good one though their capacity for and speed of detection of route failure was definitely not ideal. I've never needed inbound but did set it up with raw devices back in about 2005 and it worked fine. One technique few people use which I think is great is forwarding your service business' phone number to people as an SMS contact when people sign up to your website. This stuff is becoming a lost art.
Re: Telephony, SMS, and MMS APIs
#30I wish I had something like this sooner. I decided to go with Plivo for a side-project of mine and while my experience has been pleasant I really miss MMS support. I'm going to take some time going through this list evaluating different MMS providers. Anybody have any experience with a particular company on this list with MMS that they enjoy?
I'm actively looking for MMS support, US as well as international.
Twilio does MMS, both inbound and outbound. Pictures only for the US and Canada, though.