Twilio's API docs suck.

Why can't they just provide a simple API reference will all the endpoints and parameters instead of some hand-holding tutorial with a helper library.

Because they are progressive

(as in """forward thinking""")

Exactly! Don't give me a dependency to add to my project. Just list out the endpoints, request and response parameters and a clear explanation of what is what

I really wish all public apis were documented with Swagger. Would make our lives a little easier.

@asgs Exactly. Why would I want to use a bloated helper library and add a dependency for the 3 endpoints I want to call...

@asgs https://twilio.com/console/...

@albydarned I don't have a login, so I'm looking at the API Ref https://www.twilio.com/docs/api

Honestly, it looks more like an advertisement of how many sets of APIs they expose rather than a real developer portal

Because they don’t give a fuck as they don’t have any real competition I know about that can serve corporations ( google is just trying to start ).

Moreover they try to charge lots of 💰💰💰 for their own studio and are launching ( launched ) some workflows.

@vane Good alternatives:

plivo.com
bandwidth.com
nexmo.com

@vane Bandwidth may be the only one of these 3 that has the... bandwidth... to support similar scale as Twilio.

I haven't read Twilio's API docs but I can still say that Google's APIs are worse. The other day they sent me an email, because my Google account is used for an automated connector, telling me that I had 30 days to upgrade to the new version or the connector wouldnt work.

I looked at the docs and they say they deprecate versions and then eventually sunset them. I never got a notification of them deprecating it and this was them going straight to sunsetting the version before latest.

The docs also "show" you how to add the API as a dependency but it's 4 deprecated versions behind.

@cmarshall10450 classic