API integration · connecting existing systems
Connect your website to your systems: forms, customer accounts and live data without manual work
A website disconnected from your systems produces emails someone retypes. A connected website puts a request straight into the CRM as a lead, lets a customer log in and see their own orders, invoices or appointments, and shows prices and stock from the system where they really live. OmniTechs builds those integrations on the APIs of your CRM, accounting, ERP or planning, as a separate process next to your website, with a check on every transfer. Also for websites we did not build ourselves.
Door Sina Sadegh Esfahani · Practice page by OmniTechs in Groningen; amounts follow the current price contract · Beoordeeld op .
What does a website integration cost?
An integration between website and one other system with a documented API is agreed in advance as a fixed amount; the calculator on the API integration main page shows the starting price for your combination and number of data types. After that the quote is fixed, no hours afterwards.
If one of the systems is poorly documented, documents or emails have to be read first, or it is unclear which system leads, we start with a Solution Sprint of €1,250 excl. VAT: we test the connection for real and you receive a fixed build price. Recurring costs are limited to hosting of the integration layer and monitoring in a Care plan; licences for the systems themselves are paid directly to their vendors.
- 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
- First assessment free, within one working day
What can a website exchange with your systems?
From simple to far-reaching. Start with the flow that costs most time today.
| Data | Direction | Watch out for |
|---|---|---|
| Forms and requests | Website → CRM or planning | Pass source and page; record consent; queue during outages |
| Customer account with orders and invoices | Accounting or ERP → website | Login and permissions: a customer sees only their own data |
| Prices and stock | ERP → website | Price list per customer group; stock refreshed on schedule or live |
| Appointments and bookings | Website ↔ planning | Prevent double bookings; confirmation from one system |
| Documents and statuses | ERP → customer portal | Which status the customer sees and when |
Form integration, customer portal or full integration?
A form integration is small work and saves time immediately. A customer account that shows data from your accounting or ERP needs permissions, caching and a well-designed screen; that is the step towards a customer portal or web application. Showing prices and stock live needs a leading system and a plan for when that system does not answer. We advise the smallest step that solves your problem, and build it so the next step fits on top.
How a website integration works technically
The integration runs as a separate process next to your website, not as a plugin inside it: your site stays fast and a CMS update cannot break the integration. Towards your systems it uses their APIs with its own key and limited rights; towards the website it delivers only the data the logged-in visitor may see. Every message is recorded, retried on failure and reported to an agreed person after repeated failures.
What you prepare
Access to your website or CMS to set up forms and an integration endpoint, API access to the system being connected, a list of forms and fields, and a decision on which data a customer may see online. With the free mapping tool on the main page you line up the fields.
How it runs
Day 1: free assessment of website, systems and desired flows. Week 1: field mapping, permissions and consent. Weeks 2 to 4: build, tests with real requests and a test account, go-live. Then monitoring through a Care plan, also for websites we did not build.
What to expect
- First assessment within one working day, free
- Field mapping as a document you can check yourself, with the free mapping tool on the main page
- Tests with real data in a test administration before the integration goes live
- Error messages someone on your team understands, with an owner and a retry
- Code, mapping and documentation are yours; maintenance via Care or in-house
Frequently asked questions
Can you connect a website OmniTechs did not build?
Yes. We need access to the CMS or the hosting for an endpoint; the integration itself runs outside the website. For WordPress, WooCommerce and most modern CMSs that is routine.
How does this differ from Zapier or Make?
Zapier and Make are fine for simple flows without custom logic and with limited volume. Choose custom work for your own rules, customer accounts with permissions, higher volume or data that must not pass through a third party.
What about security and the GDPR?
Each integration gets its own key with only the rights it needs, data travels encrypted, logs contain no personal data and a processing agreement records what the integration stores and for how long.
What if my system has no API?
Then we look at scheduled export and import, a database connection or a managed middle layer. Sometimes a system without an API is a reason to reconsider that system; we say so honestly.
How long does a website integration take?
A form integration is often live within a week; a customer account with live data takes three to six weeks, depending on permissions and screens. The date is in the quote.
What must your website exchange with your systems?
Send the name of your website or CMS and of the system it must talk to, and which step is done by hand today. Within one working day you hear which integration fits and what it costs.