APIs are often used as a way to decrease coupling and enable an evolving ecosystem of business capabilities. However, when confined to a concrete “API Platform”, many of the possible degrees of freedom can be inhibited, stifling the decoupling and innovation that was one of the initial driving factors to start an API strategy and program. One important aspect of API strategy therefore is to make conscious choices where to allow and make decisions for individual APIs and services, and the overall ecosystem. Distilling patterns and practices from the evolving ecosystem of APIs into recommendations and conventions becomes an essential part of moving from static platforms to constantly evolving ecosystems. The goal is to find the optimal balance between complete autonomy for each API design and implementation, and a supporting ecosystem that both constrains and supports APIs as a way to improve the overall ecosystem value.