You should read this book if you are remotely interested in the following:
1. Why your company needs to have an API
2. How to design, secure and manage the API
3. What API strategies your company should adopt, including legal and operational considerations
4. How to measure the success of the API
5. How to drive API engagement
The authors have years of experience in the API space and I think they did a pretty good job distilling their collective wisdom and learned best practices in this “short and sweet” booklet (134-pages!) I think it is important for the success of any API initiative that *all* stakeholders read this book to get on the same page of what needs to take place to ensure the success of the initiative. It’s hard to argue with the “tried and true” practices of which this book is rife.
If you’re interested in getting into the nitty gritty technical details of how to build an API, I highly recommend RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity as a technical companion read to this book. Read this book first, and then delve into the technical details with Subbu’s book.
If you’re an executive who’s on the fence regarding APIs, you must read this book to get educated on the subject. It’s important for your team to get your full support which they won’t unless you fully understand the whats, hows and whys of APIs.
You need to learn how to speak API and this book will get you fluent in no time.