The guide

This guide describes API management as a discipline, not as a product. It depends on no vendor: what it names are functions to deliver and decisions to take, and they stay true when the installed platform changes.

It serves three purposes. Assessing an offer without letting its brochure lead the way. Diagnosing a platform already in place, by naming what is missing. And giving teams who work together a shared vocabulary, because some of the disagreements on the subject are disagreements about words.

If the subject is new to you, start with what API management is: the definition, the five functions and the three components, in one page and one diagram.