Integration
Custom API integration
When no standard connector exists for your systems, we build the API integration. With clear agreements on what is exchanged, what happens when something fails and who runs it.
When you need it
When do you need a custom API integration?
Usually only when a standard connector does not exist or does not fit. A proprietary package, an industry-specific system or a process that departs from the standard: that is where an API integration is the way to go.
For many combinations of ERP, webshop and shipping platform a standard connector already exists, and we look at that first. According to BizBloqs, systems outside its standard catalogue can be connected through an API or file exchange. We build a dedicated API integration where that is not enough.
Approach
How we approach an API integration
First we settle, for each piece of data, which system is the master and which messages travel in each direction: orders, articles, stock, invoices or customer data. Then we pick the technique that suits what the systems can do, such as a REST API, webhooks or file exchange.
The design covers what happens when a message fails: is it retried, who is notified, and how do you see what is still open. An integration that quietly loses messages is worse than no integration.
What we build is documented, so it does not depend on one person. After go-live we can take over the running of it.
What we need
What you need to bring
The API documentation of the systems involved, a test environment we may work in, and someone who knows the process and can make decisions. If a supplier has not documented its API well, we work that out together with the supplier.
Cost and lead time
What it costs and how long it takes
What an API integration costs and how long it takes depends on the systems involved and the number of data flows. After a free intake call, we give you a fixed quote.
Process
From first look to running it
01
Take stock
Which systems, which data, which direction. We check whether a standard connector fits before we build anything.
02
Design
Messages, field mapping and error handling on paper, agreed with you and the suppliers.
03
Build and test
Built on a test environment and run through real scenarios, including what happens on failure.
04
Go live and run
Go-live with monitored message flows, followed by ongoing running of the integration.
This is part of our Integration service, where we select, build and run integrations between ERP, WMS, webshop and CRM.
Questions
Frequently asked questions
What does a custom API integration cost?
It depends on the systems involved and the number of data flows. After a free intake call, we give you a fixed quote.
What if a supplier changes its API?
That is a reason to settle the running of the integration up front. When we run it, we adapt and retest it, so your team does not have to chase the change.
Can you take over an existing integration?
Often, yes, if there is documentation or access to the code. We first assess what is there and whether repairing or replacing it makes more sense.
What happens after go-live?
After go-live you get four weeks of aftercare. After that you can reach us on working days from 08:30 to 17:00, and we respond within 24 hours.
Need an API integration?
Tell us which systems need to be connected. We will assess whether a standard connector is enough or whether an API integration is needed.