API
Also known as: application programming interface · programming interface
An API is a defined interface through which two software systems exchange data automatically, without anyone transferring it by hand.
An API defines what data and functions one system exposes to another, and the exact shape of the requests and responses. Instead of a person reading data out of System A and typing it into System B, one piece of software calls the other's API directly and gets structured data back. That only works if both sides speak the same interface format, which today usually means HTTP with JSON.
In practice, you notice an API when two otherwise separate systems, say an online shop and inventory management, show the same up-to-date data without a manual export-import step. Software vendors usually publish documentation describing what their API offers and how to authenticate against it. Not every piece of software has an open API; some can only be connected through workarounds, or not at all.
A common misunderstanding: having an API doesn't automatically mean two systems are compatible. Both sides need to use the same data fields with the same meaning, and changes to an API can break existing connections if nobody keeps track of the version.
What it means in practice
In practice, a missing or unused API connection usually shows up as staff typing orders, stock levels, or customer data into two systems by hand. NDVDL checks first what APIs the involved programs actually offer before planning any integration.
Is this handled properly at your site?
We look at how it actually stands with you — and say honestly whether anything needs doing.
Related terms
All termsA term from your quote missing here?
Send us the passage you do not follow. We will explain it — with no obligation to order anything.