APIs and integrations that keep systems in step
We build REST APIs and connect the systems a business already has, such as an ERP, a CRM, payment providers and carriers. Data is entered once and reaches every system that needs it.
What we build
-
REST APIs
Documented and versioned interfaces for portals, mobile apps and partners. The description of the API is published, so the other side can build against it without asking us.
-
Integrations
Links to ERP and accounting systems, CRM, payment providers, carriers and parcel lockers, and data exchange with partners.
-
Gateways
One entry point in front of several internal systems, with a single place for access rules, limits and logging.
-
Security
Authentication, permissions by role, request limits, an audit log and a web application firewall in front of public interfaces.
Work
-
Sils
Regular import of products, prices and stock from the ERP, bank links, leasing partners, parcel lockers and product feeds.
Read the case study: Sils -
Lasi.lv
A CRM, online payments, subscription exchange with the postal service and exports to accounting systems on one platform.
Read the case study: Lasi.lv -
Livonia Print
Staff data kept in sync between the ERP and the request portal.
Read the case study: Livonia Print
What makes an integration reliable
A link between two systems usually works on the first day. Problems come later, when one of them is down, slow or sends the same message twice, so we design for those cases from the start.
-
An adapter for every outside system
Each outside system is reached through an interface of our own. When a provider is replaced, we write a new adapter and the rest of the system does not change.
-
Queues and retries
Calls to outside systems go through a queue. A failed call is repeated, and one that keeps failing is set aside for a person to look at.
-
No double processing
Every operation has an identifier, so a repeated message does not create a second order or a second payment.
-
Reconciliation
The state on both sides is compared on a schedule, and differences are reported before a customer finds them.
-
Logs
What was sent, what came back and how long it took is recorded, so a dispute between two systems can be settled with facts.
One source for every piece of data
Before we connect anything, we agree which system owns which data. In a shop, prices and stock belong to the ERP and product descriptions to the PIM. Every other system reads them and does not keep a copy of its own to edit.
With one owner for each piece of data, prices on the web and in dealers' orders stay the same as in the ERP.
- ERP
- Import
- PIM
- API
- Webshop and ordering platform
APIs for mobile apps and partners
A mobile app, a portal and a partner's system can all use the same API. We version it, so an old app keeps working while a new one uses new features.
Related services
Integrations usually come with a system on our side that uses the data.
Do your systems need to exchange data?
Tell us which systems you have and which data is typed in twice today.