API automation: the sturdiest link between two systems
Connects systems directly, through their official data interfaces
Data moves between systems without anyone copying it across
When a system has an API, every other way of integrating is a choice you regret at the first update.
What you get
It survives updates
Unlike interface automation, an API does not break because a button moved.
Fast, and in real time
Data moves in seconds, not on a nightly sync that discovers the problem in the morning.
Errors are explicit
The other system says exactly what it rejected and why. We do not guess from what appeared on screen.
It works both ways
We do not only read from your systems — we write back, which is the half usually missing.
How it works
1. Authentication
We connect with dedicated credentials holding minimum rights. We never use somebody's personal account.
- OAuth 2.0
2. Mapping
We establish which field in system A matches which in B, including where nothing matches.
3. Transfer
Data is sent and the reply checked. An empty 200 is not taken as confirmation.
- REST
- n8n
4. Reconciliation
We check periodically that what should exist in both systems actually exists in both.
- PostgreSQL
Where it works well
- Modern systems with a documented API
- Frequent, high-volume synchronisation
- Flows where you need confirmation the data arrived
- Integrations that must last years, not months
Where it does not
- Legacy software with no API — there we automate the interface, with more upkeep
- APIs with hard rate limits set the pace, however much we optimise
- Vendors who change their API without notice need monitoring, not just integration
What we use
- n8n
- e-Factura
- PostgreSQL
Where we use it
Frequently asked questions
- Our system is old and has no API. What then?
- We automate the interface — it works, but needs more upkeep. We tell you the cost difference upfront, not afterwards.
- Who holds the credentials?
- You do. You create them with the minimum rights needed, and can revoke them at any time without asking us.
- What if the vendor changes their API?
- Monitoring catches it on the first failed call, not a week later. The repair falls under the managed service or the warranty.
- Does our data pass through your servers?
- It depends where the flow is hosted. It can run entirely on your side. Either way, we tell you exactly what passes where.
- How long does one integration take?
- A simple one, a few days. One with two-way reconciliation, one to two weeks. The vendor's documentation decides more than the complexity does.