As briefly discussed in the Preface of this book, the name API Catalog suggests that OAC is a product whose main purpose is to help organizations create a catalog of all available APIs thereby unlocking functionality and information which would have been previously hidden. Web API catalogs allow app and/or mobile developers and architects to discover and reuse assets rather than recreating them from scratch. This, in turn, delivers benefits to the business and IT since cost and time to market can be significantly reduced.

How can OAC achieve this? How are APIs loaded into OAC? How is the product implemented? How rich is the functionality? Are there limitations and if so can I extend the functionality? These are some of the questions that a systems implementer needs to ask. This chapter aims to address these questions and go beyond just the theory by providing several hands-on examples on how OAC can be implemented to address real world business requirements...