Short answer
A custom API integration between two systems usually costs €500 to €2,000 excluding VAT, one-off. A simple one-way integration sits at the low end; a two-way integration with many fields, error handling or a system without a good API sits at the high end. On top of that, expect €10 to €50 a month for hosting and €150 to €500 a month if you want maintenance and monitoring. If a standard connector already exists, it is often cheaper.
What is an API integration?
An API (Application Programming Interface) is the digital entrance of a software package that lets other software request or send data. An API integration is a small piece of software that connects two of those entrances, so data moves from one system to another automatically.
Typical examples: web shop orders that land in the accounting package as invoices, new leads from a website form that appear in the CRM, or appointments from a scheduling tool pushed into a customer portal. Without an integration, someone retypes that data, with errors and delays as a result.
What does an API integration cost?
The amounts below are the indicative prices I use myself, excluding VAT. They give a realistic picture but are not a quote.
| Type of integration | One-off |
|---|---|
| One-way, few fields (e.g. form → CRM) | €500 – €900 |
| One-way with data mapping (e.g. web shop → accounting) | €800 – €1,500 |
| Two-way sync with conflict handling | €1,500 – €3,000 |
| System without a good API (exports, scraping, legacy database) | from €2,000 |
| Several systems with their own middle layer or dashboard | from €4,000 |
| Item | Indication |
|---|---|
| Hosting the integration (server or serverless) | €10 – €50 per month |
| Subscription or API fees of the connected packages | varies per vendor |
| Maintenance, monitoring and changes when an API changes | €150 – €500 per month, optional |
Always ask about recurring costs. An integration that is built cheaply but watched by nobody often stops silently when a vendor changes its API, and you only find out when the numbers are wrong.
What drives the price
- The quality of the APIs. Good documentation and a test environment save a lot of time. Some packages only offer a limited or paid API.
- One or two directions. Two-way sync needs rules for what happens when both sides change something at the same time.
- How much data needs mapping. VAT codes, product variants, currencies and addresses look different in every system.
- Real-time or periodic. Pushing changes instantly via webhooks is a bit more work than polling every fifteen minutes.
- Error handling. What should happen when a system is briefly unreachable or data is incomplete? Who gets notified?
- Volume and history. Thousands of records a day, or a one-off migration of old data, needs extra attention.
Standard connector, Zapier or custom?
Not every integration needs to be built. Pick the simplest route that works reliably.
| Route | Good fit when | Watch out for |
|---|---|---|
| Standard connector or vendor app | It does exactly what you need | Little room for exceptions, often a monthly fee |
| Zapier, Make or n8n | Simple flows, low volume | Costs grow with the number of tasks, limited error handling |
| Custom integration | Your own rules, high volume or no standard available | One-off build cost and someone to maintain it |
A good developer tells you honestly when a standard connector is enough. Start there, and only have something built when it does not fit or gets too expensive at your volume.
What to provide for a reliable price
- Which systems need connecting, and which subscription you have (not every plan includes API access).
- One complete example of the data flow: what happens, from start to finish, to one order, lead or appointment?
- Which fields need to move, and which side wins when data differs.
- How often it should run and how many records a day are involved.
- Who should be notified when something goes wrong.
- Access to a test environment or test account, if there is one.
How building an integration works
Map the data flow
Together we describe which data goes from where to where, and when.
Check the APIs
I verify that both systems can do what is needed before there is a price.
Scope and fixed price
Fields, rules, error handling and acceptance criteria on paper, with a price.
Build and test
First with test data, then with a small set of real data.
Go live with monitoring
Logging and alerts, so a failure is noticed before it shows up in the numbers.
Handover
Documentation, access and code, so you do not depend on one person.
Comparing quotes fairly
Two quotes are only comparable when they cover the same data flow and the same responsibilities. For each quote, check:
- Are one-off and recurring costs listed separately?
- Are error handling and monitoring included, or only the "happy path"?
- Who owns the code, and where does the integration run?
- What happens, and what does it cost, when a vendor changes its API?
- Is personal data processed, and if so, is there a data processing agreement?
Two systems that need to talk to each other?
Describe which systems they are and what should happen. You get questions and a price indication back within 24 hours on working days.