Change is inevitable and growth is a good thing. When your API has reached the point of expanding beyond it’s original intent and capacity, it’s time to consider the next version.
Whether that next iteration is a whole number version bump or just a feature expansion, it’s important to consider the pros and cons of how you let your developers know about it. Read more
Build it and they will come. That might work for ghosts and baseball fields but, sadly, it’s not true for APIs. There’s nothing worse than spending months developing an API, or any other product for that matter, only to see it flounder after launch. 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
What is a consistent attribute across successful API programs? They all have awesome developer portals. Good API documentation is easy to navigate and understand, but the best, shining developer center pushes onboarding and actual implementation to new levels of usability, to the point where integrating the API becomes as simple as cake — well, at least as simple as technically possible. Read more