Controlled data exchange
An API is a controlled technical interface. An API integration uses that interface to read or write authorised data with authentication, validation, duplicate rules and visible failure handling.
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.
€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.
Implementation not included
Annual plans for digital work
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.
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.
COMPANY is not discovery only: the plan covers implementation and ongoing work. The Solution Session and Solution Sprint stay separate and optional.
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
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.
Source of truth, direction, authentication, field mapping, duplicate rules, retry behaviour, monitoring and who owns failures. Without those, an implementation quote is a guess.
API quality and documentation, auth model, mapping complexity, error scenarios, volumes, sync timing and operational monitoring — not only “how many systems”.
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.
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.
No. Prefer a maintained connector or a controlled export when it already covers the critical flow responsibly.
Business data stays with the client. Ownership of code, configuration and delivered artefacts is set in the written agreement.
