As we make the shift towards treating APIs more like bonafide products, Developer Experience (DX) is only becoming a more prominent topic. Over the last few years, you’ve probably noticed a growing amount of literature, tooling, and discussion on the subject of DX. Read more
People develop APIs for all sorts of reasons. They might be trying to create a tool to facilitate internal processes where they work, they could be building an external product for customers, or they might be building a third party tool designed to mash-up other services. 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
While most organizations have matured in developing the glue between their information and application systems via APIs, many often overlook how to deliver and expose those APIs to their respective consumers.
Reusability and adoption are the driving factors for a healthy ROI from an API, but they are harder to obtain than you may think. 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
