What is API?

An interface specifying how software components exchange requests and information.

This term should be understood in relation to the information, platforms, integrations, controls and operating requirements that support commercial work. In practice, API should be defined clearly enough that the people responsible for the relevant decisions can apply it consistently, recognise its limits and identify the evidence needed to evaluate it.

When this concept is unclear or disconnected from the wider revenue environment, teams can make locally reasonable decisions that create friction elsewhere. A useful application makes ownership, dependencies, expected outcomes and trade-offs more visible.

Consider how API affects the movement from strategy and demand through conversion, customer value, expansion and continuous improvement. The relevant people, processes, technology, data and governance should support the intended commercial outcome rather than operate as an isolated capability.

Commercial Architecture examines the relationships between strategy, people, process, technology, data and governance. API is one part of that wider design. It should not be treated as evidence of a complete Governed Revenue System by itself.

The practical meaning of API depends on the role using it. Executives need to understand its effect on direction, risk and investment; commercial leaders need to connect it to performance and accountability; and specialist teams need clear processes, information and decision rights for operating it.