Today, most API endpoints aren’t versioned at a granular level, and for good reason. If you tried to version each endpoint individually—or worse, by HTTP method—it would lead to a chaotic and unsustainable mess. This is why APIs are typically versioned as a package: a set of endpoints grouped under a common “API Name” and “API Version.” However, this structure...
Chris Hood is a strategist, consultant, and public speaker, currently serving as the CMO at PolyAPI. With a background that includes leading API strategy at Apigee and Google, Chris has been immersed in the API world since 2009, helping some of the largest global companies shape their API designs, products, and monetization strategies. As a thought leader in the field, he has defined productization principles and digital ecosystems that are now standard across industries. This site reflects his insights, predictions, and musings on the future of APIs, as he works on his upcoming book, Application People Interfaces, a CEO's guide to understanding the value of APIs and the impact of AI on their future.