It’s easy to become enveloped in “paradigm-shifting” technical dogma, to the point that API providers overlook personal qualities of the developers that consumer APIs and the end consumers affected by their implementations.
Thankfully, there is an “out”, so to speak, for this kind of behavior. Read more
Error codes are almost the last thing that you want to see in an API response. Generally speaking, it means one of two things — something was so wrong in your request or your handling that the API simply couldn’t parse the passed data, or the API itself has so many problems that even the most well-formed request is going to fail. Read more
The API economy has ushered in a new era of application integration, causing a sea change across enterprise IT and application providers alike. APIs are providing access to data securely across firewalls, enabling new business models and offering a platform that supports the development of new digital products. Read more
We’ve written plenty about different API monetization models and monetizing your API using a freemium model in the past, but just as important is envisioning how your API might fit into your business model as a whole.
Obviously, this is something that will differ hugely from company to company — in the case of a business like Twilio, the API is the core product. Read more
On the one hand, having proper API documentation can be a sign of early success for an API provider, allowing new users to effectively understand the functionalities and caveats behind an API solution.
On the other hand, extensive documentation could indicate an overly complex solution with far too many variables to navigate. Read more