Why APIs do not automatically create interoperability
LeanSignal technical brief · Enterprise data & systems architecture.
An API can move data between two systems while leaving the harder interoperability problem untouched: whether both sides understand, govern and act on that data in the same way.
Connectivity answers “can it move?”
Interoperability also asks whether the receiving system understands the semantics, provenance, authority, lifecycle and policy attached to the information.
Four layers must align
Technical
Protocols, schemas, transport and interface behaviour must be compatible.
Semantic
The meaning of entities, states, units and relationships must survive the exchange.
Governance
Ownership, usage rights, retention and accountability must remain clear.
Operational
The receiving system must know what to do when data is late, incomplete, conflicting or unavailable.
A connected enterprise can still be operationally non-interoperable.
Architecture principle
Design interfaces as contracts that carry meaning and control context, not only payloads.
General architecture guidance. Specific environments require adaptation to their security, regulatory, operational and technology constraints.