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
If you’ve been paying attention to the API space over the last year, you won’t be surprised to hear that there has been a lot of movement amongst companies that provide API-related solutions.
The most noteworthy example is Google’s $625 million acquisition of API platform provider, Apigee, in the fall of 2016. Read more
Designing and writing good API documentation can be a daunting task, but is critical for any API-driven or B2D (Business 2 Developer) company to ensure developer success. Your documentation is also your company’s marketing asset and may be the first few pages a new prospect visits to assess how difficult your integration is and how the product works. Read more
An API is only as good as it is known. Getting an API into a developer’s hands, demonstrating the power of your solution, and providing an environment in which they can test and manipulate data in a controlled, monitored way is perhaps one of the most important unsung heroes of API publication. Read more