Our own servers in Europe · GDPR · Support in your language

Integrations

We connect to any system, not just your ERP

Beyond the ERP, Kimobox connects to any open or API-based system: a CRM, an online store, a government portal, an in-house build. The connection is bidirectional, and how each piece of data gets processed is tailored to your case, not a generic template.

What can be connected

A closed platform ends up as another silo, however good it is. Kimobox exposes a documented REST API for reading and writing any data in the system, and supports webhooks to notify other systems when something happens. With that, connectivity is not limited to the ERP: a CRM, an online shop, a SCADA system, a government portal or an in-house application can all take part in the same processes.

Content reviewed on

Interface style
REST over HTTPS With token authentication and scope-based permissions
Direction
Read and write The API is not a read-only dump
Events
Outbound webhooks The external system finds out immediately, without polling every minute
Format
JSON Described with an OpenAPI specification
Traceability
Every call is logged With origin, scope, outcome and response time

Two-way API

Data flows both ways: Kimobox reads from your system and also writes back to it.

Any system with an API

CRM, e-commerce, banking, government portals or an in-house build: if it exposes an API or a database, it connects.

Custom processing

Every integration is built to spec: what data it transforms, what rules it applies and in what format it delivers it.

A log of every exchange

Searchable log, automatic retries and alerts if something fails.

Your system stays closed to third parties

The connection runs through credentials you control and can revoke.

One-off migrations and imports

Initial or one-time loads from Excel, files or any other source.

What usually gets connected


Systems we've already worked with

  • CRM and sales tools
  • Online stores and marketplaces
  • Banks and payment gateways
  • Government portals
  • Custom systems with their own API
  • Spreadsheets and flat files
KIMOBOX CRM ECOMMERCE BANKING AND PAYMENTS PUBLIC ADMIN. IN-HOUSE DEVELOPMENT TWO-WAY API · CUSTOM PROCESSING PER SYSTEM

Real examples


Connections that are not the ERP

E-commerce

Order issues raised from the shop

Before The complaint arrives in the customer service inbox and somebody copies it into the quality system, when they remember.

After The shop raises the nonconformity by API with the order number and the photos. The handling circuit starts immediately.

Manufacturing · SCADA

Process alarms that leave no record

Before The alarm sounds in the control room and gets written in a notebook if the operator has time.

After The SCADA sends the alarm to Kimobox, which opens the record with its exact time and value. The monthly review runs on complete data.

Services · government portal

Filings with the public administration

Before Somebody logs into the electronic office, files, and saves the receipt in a folder, if they remember.

After The case is prepared in Kimobox, filed through the relevant interface, and the receipt returns to the case file automatically.

Vocabulary


Interoperability terms

REST API
An HTTP-based interface with standard operations on URL-identified resources. Its practical advantage is that every language can consume it without special libraries.
Webhook
A call the source system makes to the destination when an event occurs. It inverts the polling model: instead of asking every minute, you get told.
OpenAPI
A standard specification for describing an API in machine-readable form. It allows clients and documentation to be generated rather than hand-written.
Scope
A specific permission attached to an access token. Limiting scope is what stops a read-only integration deleting something by mistake.
Rate limit
A cap on requests per unit of time. It protects the system from a badly written integration and forces batch design when volume demands it.

Frequently asked questions


What people ask us before getting started

What if my system has no API?

If it exposes a database, files or some other access point, there is almost always a way in. We assess it case by case.

Who builds the integration?

Our team, based on what you need to transform and the rules that apply.

Can I have several integrations at once?

Yes, each one is independent and monitored separately.

What can be done with the API?

Read and write practically any data in the system: create records, advance a flow, query the state of a case, download documents. It is not a read-only extract.

How does authentication work?

With access tokens assigned a specific scope. Limiting the scope is what stops an integration meant for queries from deleting something by accident.

What are webhooks for?

They are notifications Kimobox sends to the external system when an event occurs. They save the other system from asking every minute whether there is news, and make integrations react immediately.

Is it documented?

Yes, with an OpenAPI specification, so clients and documentation can be generated automatically rather than hand-written.

Is there a call limit?

Yes, to protect the service from a badly written integration. Where volume requires it, synchronisation is designed in batches rather than record by record.

Tell us what system you want to connect

We'll show you the module running with data similar to yours.

Request a demo

Sources


Where each figure comes from

References to the official text in force. If a standard is revised, this page is updated and the review date says so.

  1. OpenAPI Specification OpenAPI Initiative · Current specification
  2. RFC 9110 — HTTP Semantics IETF · June 2022
  3. Regulation (EU) 2023/2854 (Data Act), on access and interoperability EUR-Lex · 13 December 2023

Open connectivity: integrate Kimobox with any API-based system

Kimobox offers open connectivity through a bidirectional REST API, letting you integrate any system that exposes an API or an accessible database: CRM, e-commerce, banking, government portals or custom builds, beyond the ERP.

Every integration is processed according to the client's own business rules, with every sync logged, automatic retries and alerts on failure, without exposing the source system to third parties.