Glossary
API
An API is a defined way for one piece of software to request something from another (retrieving data, creating a record, triggering an action) through a documented contract rather than through a human interface.
Glossary
An API is a defined way for one piece of software to request something from another (retrieving data, creating a record, triggering an action) through a documented contract rather than through a human interface.
An API states what can be asked, in what format, what comes back, and what happens when something fails. Because that contract is explicit, two systems built by different teams at different times can work together reliably.

An interface changes when a vendor redesigns a screen; a published API is versioned, with deprecation notice, precisely because other systems depend on it. This is the difference between an integration that survives and one that breaks at the next update.
Payments, messaging, mapping, document generation and AI models are all consumed this way, which is why 'can it integrate' is now a procurement question rather than a technical detail.
A system that fails those is a system that will be expensive to connect later.
Because it decides how expensive that system is to connect to anything else. Without one, integration means driving screens or exporting files, both fragile. With one, the connection is a documented contract that survives updates.
An API is something you call when you want data. A webhook is something that calls you when an event happens. Most integrations use both: webhooks to learn that something changed, APIs to fetch the detail.
An API is a defined way for one piece of software to request something from another (retrieving data, creating a record, triggering an action) through a documented contract rather than through a human interface.