Controlled data exchange

API integration: cost, approach and the systems we connect

Retyping orders, customer data or statuses costs time and creates errors. OmniTechs builds targeted integrations between your existing systems when a standard connector is not enough: fields mapped, rules recorded, errors visible, and maintenance after go-live. Send the names of both systems and the data that must move; the first assessment is free.

By Sina Esfahani · Practice page by OmniTechs in Groningen; amounts follow the current price contract · Reviewed .

What does an API integration cost?

An integration between two systems with standard APIs, such as a web shop to an accounting package, is usually a fixed amount agreed in advance on the number of data types, the direction and the checks. The calculator on this page gives the starting price for your combination; the quote is then fixed, no hours afterwards.

Uncertain cases, for example a system without documentation or with an outdated API, start with a Solution Sprint of €1,250 excl. VAT in which we test the connection for real before you commission the build. Recurring costs are limited to hosting of the integration layer and monitoring, agreed in a Care plan.

  • Standard integration: fixed price after the calculator and a short intake
  • Uncertain combination: Solution Sprint €1,250 excl. VAT, then a fixed quote
  • Recurring: hosting of the integration layer and monitoring via Care
  • Frequently requested: Exact Online, Moneybird, AFAS, Shopify, WooCommerce, HubSpot, Teamleader

API and API integration in plain language

An API is the controlled counter of a system. An integration uses that counter to move agreed information at the right time — with authentication, validation, duplicate-record rules and visible error handling.

Does your existing software lack a suitable API? Explore what is involved in having an API built.

Worth investigating when

  • the same data is repeatedly moved between two maintained systems
  • volume, timing or error impact makes manual transfer unreliable
  • ownership of each field and change is clear
  • documentation, suitable access and representative test data exist

Stabilise the basis first when

  • a controlled export/import already handles low volume
  • a maintained standard connector already covers the flow
  • a source has no reliable API or managed access
  • process definitions still change constantly

Relevant offer at a glance

Solution Sprint

Paid scope work

€1,250 excl. VAT

An organisation with a non-standard process or product problem that first needs to investigate users, dependencies, risks and scope.

Independent project work that clarifies the problem, users, dependencies, risks and scope before an implementation price is provided.

  • A 60–90-minute problem and process workshop
  • Current-state workflow map
  • User and stakeholder definition

Implementation not included

Annual plans for digital work

Part of a wider annual plan?

When software, automation and integrations add up to a year of work, COMPANY (from €5,000/year excl. VAT) can combine implementation and ongoing work. The proposal selects what is needed.

COMPANY

Build around how your company works.

From €5,000/year excl. VAT

A scoped technology plan for your website, specialist content and SEO, internal software, automation, mobile applications, AI and connected hardware.

The proposal selects the building blocks; not every capability is in the starting price.

  • A written proposal that selects the building blocks your company needs
  • Defined implementation for the plan year
  • Defined ongoing work: operation, maintenance and agreed improvements

COMPANY is not discovery only: the plan covers implementation and ongoing work. The Solution Session and Solution Sprint stay separate and optional.

Just this module?

That works. Request this module on its own, without an annual plan. A paid Solution Session or Sprint is optional.

Request this module on its own: API integrationCompare the plans

Our own implementation

See how our workspace connects a calculator, models and AI editing

The print flow connects file validation, our pinned slicer, approved pricing and an account-owned application. Each boundary has its own job: the calculator estimates; the customer provides delivery details; the workshop accepts or revises the production request. The API does not turn an estimate into an accepted order.

The Meshy adapter keeps provider credentials on the server, reserves prepaid balance and uses a durable attempt ID for retries. Completed model files are retained locally before download is reported ready. Smart Link MCP tools update a structured draft with limited permissions. These are inspectable integration choices; they do not establish a completed paid Meshy run or a delivered customer integration.

  • Inspect requests, fields, permissions and error responses in the API guide
  • Paid generation requires configured providers and funded acceptance; check availability in the panel
  • Website platform drafts can be saved; self-service provisioning is not available yet

Start with a bounded read-only trial

Choose one read operation, limited permissions and synthetic records with an expected result. Include missing data and a denied request before allowing business records to be changed. The Dutch trial guide helps separate access problems from a production integration scope.

What must be clear before pricing an integration?

Source of truth, direction, authentication, field mapping, duplicate rules, retry behaviour, monitoring and who owns failures. Without those, an implementation quote is a guess.

What drives API integration cost?

API quality and documentation, auth model, mapping complexity, error scenarios, volumes, sync timing and operational monitoring — not only “how many systems”.

Agree which system owns each field

Before transferring a customer record, map the source fields to the destination and choose which system controls conflicting values. Check whether the vendor actually permits the required access, how fresh the record must be and whether a scheduled exchange is enough. An Excel reading task may need less than a two-way integration.

A lost response must not become a duplicate order

If the connection fails after an order is sent, its destination may already have accepted it. Before retrying, establish how to recognize that same order, check its state and route an unresolved failure to its owner. Test rejected input and recovery with harmless data before enabling writes.

What to expect

  • First assessment within one working day, free
  • Field mapping as a document you can check yourself
  • Testing with real data before the integration goes live
  • Error messages someone on your team understands, with an owner
  • Maintenance and monitoring after delivery via a Care plan

Questions about API integration

Is a custom API integration always needed?

No. Prefer a maintained connector or a controlled export when it already covers the critical flow responsibly.

Who owns the data?

Business data stays with the client. Ownership of code, configuration and delivered artefacts is set in the written agreement.

How long does building an API integration take?

A standard integration between two documented systems is usually live within two to four weeks, including tests with real data. If documentation or access is missing, the Solution Sprint first establishes feasibility.

Which systems do you integrate most often?

Accounting (Exact Online, Moneybird, e-Boekhouden), web shops (Shopify, WooCommerce), CRM (HubSpot, Teamleader, Pipedrive), planning and work orders, and custom portals. A system without an API is connected through export and import or a managed middle layer.

Who owns the integration after delivery?

You do. You receive the code, the field mapping and the documentation. Maintenance can stay with OmniTechs in a Care plan or be done in-house.

What happens when one of the systems changes?

Monitoring flags a deviating field or a failed run within the agreed time. Under a Care plan we fix it on working days; without a plan you receive a quote for the change.

Which systems must work together reliably?