Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Building an API Product

You're reading from   Building an API Product Design, implement, release, and maintain API products that meet user needs

Arrow left icon
Product type Paperback
Published in Jan 2024
Last Updated in Jan 2024
Publisher Packt
ISBN-13 9781837630448
Length 278 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Bruno Pedro Bruno Pedro
Author Profile Icon Bruno Pedro
Bruno Pedro
Arrow right icon
View More author details
Toc

Table of Contents (26) Chapters Close

Preface 1. Part 1:The API Product
2. Chapter 1: What Are APIs? FREE CHAPTER 3. Chapter 2: API User Experience 4. Chapter 3: API-as-a-Product 5. Chapter 4: API Life Cycle 6. Part 2:Designing an API Product
7. Chapter 5: Elements of API Product Design 8. Chapter 6: Identifying an API Strategy 9. Chapter 7: Defining and Validating an API Design 10. Chapter 8: Specifying an API 11. Part 3:Implementing an API Product
12. Chapter 9: Development Techniques 13. Chapter 10: API Security 14. Chapter 11: API Testing 15. Chapter 12: API Quality Assurance 16. Part 4:Releasing an API Product
17. Chapter 13: Deploying the API 18. Chapter 14: Observing API Behavior 19. Chapter 15: Distribution Channels 20. Part 5:Maintaining an API Product
21. Chapter 16: User Support 22. Chapter 17: API Versioning 23. Chapter 18: Planning for API Retirement 24. Index 25. Other Books You May Enjoy

Validation

As introduced in Chapter 4, validation is one of the steps in the API design stage. Its goal is to confirm assumptions and make sure that the API product is designed according to what stakeholders expect. You engage in the validation process and make any necessary changes until you reach a point where you can confirm that your API design is solid. The idea is to involve stakeholders, including potential API consumers, so that they can give you feedback early on. You start with a high-level approach where you attempt to validate the architectural style and the API capabilities. Once you have positive feedback, you go deeper and perform a low-level validation where you gather information on how potential users interact with your API. Let’s start by exploring the high-level validation approach.

The goal of high-level validation is to obtain feedback from stakeholders about abstract concepts that define how your API will behave. The feedback you get helps you understand...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime