The promise of APIs is to decrease coupling between IT components, thereby allowing IT landscapes to evolve more dynamically and evolutionary. This helps components to be more adaptive to serve today’s fast-changing business world. However, there is a crucial difference between working on individual APIs, and overseeing continuously evolving API landscapes. The latter is best served by an approach of continuous architecting, where the goal of the landscape is to observe how it is being used, to identify and promote emerging patterns and practices, and to support these as a way to make API product teams more effective. In this presentation we look at the path from individual APIs to API landscapes, and at the ways in which continuous architecting and supporting organizational structures help to deliver the promise of APIs as a good approach to manage IT complexity and velocity in modern organizations.