API ownership can be contentious given complexities regarding business context, accountability, shared systems, dependencies, and more.
As a guide for developing an ownership model that makes sense for your enterprise, it’s helpful to consider how the API will be used in a business context. This includes the degree to which the API is shared by multiple stakeholders across the organization, the proximity of the API to customer transactions and experiences, and the level of organizational support of DevOps cultural norms and processes inclusive of “You build it, you run it.”