API
Application programming interface
Two programmes that need to work together cannot read each other's screens. They need a fixed set of requests one can send and answers the other gives back: "give me the stock of item 4711", "here is a new order". That agreed set of requests and answers is called an API, short for application programming interface.
An API sits behind most connections between business systems. A webshop sends an order through the warehouse system's API, a carrier returns a tracking number through its own, and an accounting package reads invoices through a third. Each API has its own documentation: which requests exist, what data each one needs, what comes back and what the errors mean.
A connector or integration is often built on top of an API. The API is the door; the connector is the agreed route through it, with the mapping of fields and the rules for what happens when a message fails. When people say two systems are "linked", there is almost always an API underneath.
In practice
A customer orders three boxes of tea on a webshop. The webshop calls the warehouse system's API with the order, the warehouse system answers that the order is received, and later the webshop asks the same API for the status and gets back "shipped" with a tracking number. Nobody copies anything between the two screens.
Ready to see BizBloqs on your own process?
Book a demo and we will walk your warehouse and order flow end to end — inbound, storage, picking, shipping, returns — and tell you honestly what BizBloqs would change.
Two questions about your own operation
How many of your articles sit in a pick location they empty less than once a month?
Part one: Laying out a warehouse does not start with the racking
After your last integration, how many systems hold a stock quantity for the same item? Name them.