Interface (API)
Defined connection point between two systems through which data or signals are exchanged according to fixed rules.
An interface, in general terms, describes the point at which two systems or subsystems connect and exchange information. In the software world this connection point is usually called an API, an Application Programming Interface, a fixed set of rules through which programs can communicate with one another.
The purpose of an API is to hide a system's internal workings from the outside world and instead offer a clearly defined point of access. Another system does not need to know how a function is implemented internally; it only needs to know how to call it through the interface and what result it will get back.
Interfaces become especially valuable when they are standardised, meaning they work not just between two specific systems but across vendors under an open standard. In automation technology, for example, OPC UA has become a widely adopted standard that lets machines and software from different manufacturers communicate reliably with one another.
Practical Example
An online shop uses its shipping provider's API to automatically add tracking numbers to its own orders as soon as a package ships, without anyone having to enter the number by hand.
How Leanshift Helps
Clean interfaces are often the quiet difference between a process that runs smoothly and one that constantly needs manual rework. They form part of the technical foundation on which workflows can be improved end to end.
Frequently Asked Questions
Is an API the same thing as an interface?
An API is the software implementation of the broader concept of an interface; every API is an interface, but not every interface is necessarily an API, since physical or mechanical interfaces also exist.
Why are standardised interfaces worthwhile?
They save effort because a separate, custom connection no longer has to be developed for every combination of systems.