What does an API connection cost?
A link is usually the cheapest automation project there is: and sometimes the most unwise.
An API connection between two systems starts at around €950 when both packages have a modern API and the data is easily connected. More complex connections with many field translations, two-way traffic or outdated software can cost up to €3,000 or more. The quality of the API determines the price more than the amount of data.
PRICE RANGE
What you get in which class
Indicative and excluding VAT. We will only tell you what your situation costs after a conversation - then it is also a fixed price.
| SITUATION | INDICATION | WHAT YOU GET |
|---|---|---|
| One-way link, modern APIs | from €950 | Data from A to B, for example order to invoice, with error handling. |
| Link with field translation | €1,500: €3,000 | Fields do not correspond one-to-one; rules for conversion and exceptions. |
| Two-way coupling | from €3,000 | Both systems modify data; conflict resolution required. |
| Link with outdated software | on request | No usable API; file sharing or an intermediate solution. |
WHAT DETERMINES THE PRICE
What determines the price
The most important factor is whether both sides have a decent API. Modern packages have good documentation and then the work is predictable. With older software, most of the time is spent figuring out what is even possible.
The second is error handling, and that's the part that's missing from cheap quotes. What happens if the other system is down for a while? Without a queue and repeat attempts, you quietly lose data, and you only notice this at the year-end closing.
- Quality of both APIs — the determining factor for price.
- One or two directions — two-way traffic requires conflict resolution.
- Number of fields and translation rules — one-on-one is cheap, exceptions are not.
- Error handling — queue and retries; never leave out.
- Volume — a thousand messages a day has different requirements than ten.
- Testing with real data — requires a test environment on both sides.
WHAT YOU SHOULD PAY ATTENTION TO
When a link doesn't pay off
We regularly advise against links. An action that happens twice a year will never pay for itself: no matter how annoying that action is.
Even if one of the two packages is replaced within a year, it is wiser to wait. A link to a system that disappears is a waste of money.
- Low frequency — retyping twice a year does not justify a connection.
- Package will be replaced soon — wait until the new system is in place.
- No usable API — the detour costs more than it yields.
- The process is still changing — do not connect until the method has been established.
- Calculate it — hours per week times hourly rate times weeks; that is the payback period.
FREQUENTLY ASKED QUESTIONS
More about the costs of an API connection
How quickly does a connection pay for itself?
With daily retyping, usually within a few months. Do the math yourself: hours per week times your hourly rate times 46 weeks. If the result is less than the construction price, then it is not a good idea and we will say so.
Can you connect with any package?
With almost every modern package. Sometimes not with older or highly specialized software, and then only file exchange remains: slower and more fragile. We will find that out in advance.
What if the supplier changes its API?
Serious vendors keep their API stable and announce changes. If something breaks, you will see it in the error messages. With a service contract from €49 per month, we can solve this without you noticing.
Is maintenance included in the price?
The construction is a one-off. There is the service contract for continuous monitoring and adjustments; without a contract, we work on an hourly basis whenever there is an issue.
CONTINUE READING
Of course, continue reading about this subject.
Stop retype?
Tell us which two systems are involved. We find out whether it is possible and calculate the payback period.