Have an API integration built
Have an API integration built that simply keeps working - even on the day a system slows down, an API changes or the network drops.
The trade-off
When an API integration is the right choice
Understand first, then build - we work alongside your people.
You know the challenge: orders retyped by hand from the webshop into the accounting system, customer records that are slightly different in three systems, and an integration from years ago running somewhere that nobody dares to touch. Every manual in-between step is waiting time - and a chance for errors.
We build API integrations designed for the day something fails: with error handling, retries, queues and monitoring. Simple at the front, complexity solved behind the scenes - as part of our services in data & integrations.
Every manual in-between step is waiting time - and a chance for errors.
The signals
- Orders are retyped by hand from the webshop into the accounting system
- Customer records are slightly different in three systems
- An integration from years ago is running somewhere that nobody dares to touch
Start here - Integration scan
From challenge to a concrete plan for your integrations in one week.
We map your systems, APIs and manual intermediate steps. What has to be real time, what can run in batch, where the risks are. You get a concrete plan, prioritised by impact.
1 week
fixed timeline
1 plan
prioritised by impact
1 estimate
no surprises afterwards
What you get when you have an API integration built
For Swishfund we connected three banking platforms - Rabobank Direct Connect, Plaid and Nordigen - to their microservices and client portal, in a collaboration now running for eight years. At Van Amerongen, an API links the office and the field service, so invoices are generated automatically from work in the field. And for Manufacturing in your pocket, MES, ERP and Excel integrations bring factory data together in real-time KPI dashboards.
An integration is more than connecting two systems. The real work is in the data mapping: which field belongs where, which system is the source of truth, and what happens to records that don’t validate. Think of orders flowing from your webshop straight into the ERP, bank transactions streaming into your own platform, or field-service hours landing on the invoice without anyone retyping them.
The difference between an integration that survives a demo and one that runs for years is what happens when things break. That is why we build in error handling as standard: failed messages go into a queue and are retried automatically, duplicate processing is prevented, and rate limits of external APIs are respected. Every exchange is logged, so you can trace what happened per message - and monitoring raises the alarm before your users notice anything.
Often the integration is the foundation for something bigger. Once data flows reliably, dashboards and reports become the obvious next step. Sometimes a data migration has to come first before systems can be usefully connected. And when a screen is needed too - for customers or colleagues - an integration grows into a web application or portal.
- Integrations between ERP, CRM, e-commerce, banks and custom systems
- Error handling with retries and queues - no silent failures
- Monitoring, logging and alerts on every integration
- Real-time or batch - synchronisation that fits the process
- Documentation and handover, so you are never locked in
Our approach
How we approach it
No months of preparation up front: every step delivers something you can steer on.
1 week
Integration scan
We map your systems, APIs and manual intermediate steps. What has to be real time, what can run in batch, where the risks are. You get a concrete plan, prioritised by impact.
design, build & test
Data mapping & proof on real data
We define which system is the source of truth, how fields map onto each other and what happens when a message fails: queues, retries and alerting are designed before the first line of code. The integration first runs in parallel on real data, without touching your live process. Only when the numbers match and the edge cases are covered does it go live.
ongoing
Monitoring & maintenance
After go-live we keep watching: logging, alerts and periodic checks. When an external API changes, we see it before your users do.
In practice
VAF Infra
One digital chain, from the office to the roadside
One digital workflow for planning and execution: materials and statuses are directly visible per branch and work in the field is processed into a correct administration without detours.
View case →
Soli Infratechnik GmbH
The digital backbone of the German fibre roll-out
Soli Infratechnik laid fibre in Germany with software that connected work in the field and the administration directly, so progress stayed visible and invoices came out of the same recorded work.
View case →
Rather get straight to it? Jasper Kums, partner at eenvoud, will happily think along with you about which integration solves your challenge - and whether that needs custom work. Or start with an Integration scan.
Frequently asked questions
What you want to know before you start.
What does it cost to have an API integration built?
That depends on the number of systems, the quality of their APIs and the reliability requirements. So we work scope-first: we start with an Integration scan with a fixed one-week timeline, then build in small, budget-controlled steps. After the first conversation you get a concrete estimate - no surprises afterwards.
Isn’t a no-code tool like Zapier or Make enough?
Sometimes it is - and then that is what we advise. For simple integrations between standard packages at low volumes, no-code is often the fastest route. Custom work pays off with high volumes, complex data mapping, sensitive data or hard requirements on error handling and logging. We draw that line honestly in the Integration scan.
What if a system has no API?
There is almost always a route: connecting directly to the database, automated file exchange, or export options the vendor does offer. Sometimes the honest conclusion is that a data migration to a system that can be integrated is the better investment. We map that out before we build anything.
What happens when the integration fails at night?
For us that is design question number one. Failed messages go into a queue and are retried automatically; nothing gets lost. Monitoring raises an alert when something fails structurally, and the logs show what happened per message. Most incidents are resolved by morning - without manual work.
Who maintains the integration after delivery?
That is something we agree together. Usually the same team that built the integration stays responsible for monitoring and maintenance. The code and documentation are yours, so your own team or another party can take over. You are never locked in - although most clients stay for years.
How long does building an API integration take?
An integration between two systems with decent APIs is usually a matter of weeks, not months. The timeline is mostly determined by the quality of the API documentation and the number of failure scenarios that need to be covered. After the Integration scan you know exactly what is realistic for your situation.
Which systems can you connect?
We connect to what the package itself provides, usually a REST API: a stable interface for moving data between systems in a controlled, traceable way. In production, we used this for Exact Online time registration at Van Amerongen, NetSuite and Optimy at Stichting DOEN, and PSD2 banking APIs, including Rabobank, at Swishfund. AFAS, Salesforce and HubSpot follow the same pattern: the same kind of API, the same approach. That lets your administration, CRM and banking data work together without manual retyping.