Chapter 6. Defining the value for your API
This chapter covers
- Business goals
- Metrics
- Use cases
Designing an API should always start with the process of determining business value and how you’ll measure it, followed by determining use cases to make sure you can build your design and strategy with confidence. Doing this for a web API brings it into line with other company products and helps you to both communicate your goals and success to your executive team and make sure your API is staying on track to success. Having these goals and metrics in place will also help you verify that the API is moving in the right direction, so you can determine whether you need to “pivot” your goals, metrics, or use cases to more directly match how client developers ...
Get Irresistible APIs now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
