Almost every company uses multiple systems that know nothing about each other. An API connection is the bridge between them.
An API connection is an automatic connection between two software systems, with which they exchange data without anyone retyping anything. An order in your webshop automatically becomes an invoice in your accounting. API stands for application programming interface: the agreed language in which two programs talk to each other.
IN COMMON LANGUAGE
How a link works in practice
Suppose a customer orders in your webshop. Without a link, someone then opens the accounting system, types in the customer data, creates an invoice and manually adjusts the stock. Three systems, same data, three chances for a typo.
With a coupling this is done in one movement. The webshop reports the order to accounting, which creates the invoice and returns the invoice number. The stock is updated and the customer receives a confirmation. Nobody types anything.
A connection is therefore not a new system. It's an agreement between systems you already have: and that's exactly why it's often cheaper than replacing something.
WHY IT MATTERS
When a link pays off
The calculation is simple: how much time does retyping take, and how often does it go wrong? For an action that occurs every day, a connection is usually recouped within a few months. For something that happens twice a year, almost never.
Let's be honest about the other side: not every package has a usable API. Older software sometimes only has an export button. Then a connection is more expensive than it yields, and we prefer to say that in advance.
- Daily recurring work — the more often the action, the faster the payback.
- Same data in two places — double entry is where errors occur.
- Customers asking about the status — connected systems can answer that themselves.
- A package with a modern API — determines whether it is technically possible at all.
- Work that is now left behind — because no one gets around to it.
FREQUENTLY ASKED QUESTIONS
More about an API connection
Can every system be linked?
Almost, but not all. Modern packages almost always have an API. Older or highly specialized software sometimes does not: then only file exchange remains, which is slower and more fragile. We find this out in advance, so that you do not pay for an investigation that results in a no.
What happens if the coupling breaks?
A good connection assumes that something will go wrong at some point. Failed messages are queued and retried; If that still doesn't work, you will receive a notification instead of silent data loss. That error handling part is the most boring and important part.
Will the link continue to work if my package updates?
Usually yes. Serious vendors keep their API stable and announce changes. If something does happen, we will notice it in the error messages and not in a customer who calls.
CONTINUE READING
Of course, continue reading about this subject.
Systems that collaborate?
Tell us which packages you use. We find out whether a connection is possible, what it yields and what it costs.