Open your Mikro data to EQLEM, your own apps and your partners from a single connection hub.
EQLEM Connect is the integration hub that runs inside the customer network. It connects to several Mikro databases at once, builds a two-way data flow with EQLEM, and opens the door to outside systems through a standard REST API and webhooks. You do not have to retire Mikro.
Who is it for?
- Customer IT / integration owner: setup, connections, logs and retries on one screen.
- EQLEM administrator: you decide which user reaches which Mikro database and where each document is posted.
- Field and office users: the document you issue lands in the right Mikro database; Mikro documents and data arrive in EQLEM.
- External developer: reaches Mikro data through a standard data model over REST API and webhooks.
What it offers
Multiple Mikro databases (v16 and v17)
Define several Mikro databases in one Connect; v16 and v17 can be mixed. Each connection has its own queue: jobs on the same connection run in order, jobs on different connections run in parallel. Each connection maps to one EQLEM company, so the same account code arriving from two databases becomes two separate records in two companies.
Two-way sync between EQLEM and Mikro
- 22 master data types from Mikro to EQLEM: accounts, account addresses and bank details, account risk summary, stock, barcodes, batch/lot, color and size definitions, sales prices and price lists, stock quantity summary, services, expenses, warehouses, multi-codes, projects, responsibility centers, salespeople, cash registers, banks and fixed assets.
- Initial full load: types load in dependency order, progress is tracked per type, and an interrupted load resumes where it stopped. After that only changes arrive (incremental).
- Commercial and finance documents: sales/purchase invoices, delivery notes, orders, receipts and payments, cheque/note in and out, bank transfers, journal transfers and opening entries. Pulled automatically or manually.
- Manual pull: in EQLEM web choose the connection, document type and date range; after a preview, the selected documents are imported and a result summary (imported/skipped/failed) is shown.
- EQLEM to Mikro: documents created in web, mobile or B2B are written to the right Mikro database according to your rules. If automatic transfer is off, send it by hand with "Transfer to ERP" on the document detail. Failed transfers retry automatically; the error message shows on the document detail.
- Rules are yours: routing rules (document type, branch, warehouse, user, series), direction per master data type, frequency and scope are set in EQLEM web.
- No duplicates, no loops: a record that arrives again is updated. A document written from EQLEM to Mikro does not come back to EQLEM.
- Deleted records are deactivated, not deleted: a record deleted or passive in Mikro becomes passive in EQLEM.
- Live data: on account and stock detail, information such as risk and balance is queried from Mikro at that moment, if you are authorized.
- Per-user permissions: a user or role gets view, transfer, live query and rule management rights per connection.
Public REST API and webhooks
A REST API (api/v1) that serves Mikro data in a standard data model. Access is limited by scope and by connection, and rate limits apply. A request with the same Idempotency-Key does not create a duplicate. Events are pushed to your system through signed (HMAC) webhooks. You can use Connect on its own even without EQLEM.
Free TLS certificate
EQLEM opens a subdomain of the form label.eqlem-connect.net for you and manages the DNS record automatically (updated when your IP changes). The certificate is free, renews automatically and takes effect without a restart. In the default mode the private key stays with you and only port 443 is needed. You can also use your own domain or your own PFX certificate.
Local and SaaS web access
Connect Web runs locally in your office network without opening ports. Optionally, sign in at connect.eqlem.com with your username and password; the session is routed to your own Connect. After sign-in you see settings, ERP connection status and transfer logs.
Prerequisites and scope notes
- Mikro v17: writes go through Mikro's official API; a Mikro API license is a prerequisite. v16 uses SQL access.
- Pilot: Mikro v17 API write flows are being validated with a pilot customer; scope and dates are confirmed in the discovery call. Mikro version and modules in use are checked for every installation.
- Non-Mikro ERPs (Logo) and portless (relay) cloud access are outside this release.
- Connect is managed through the EQLEM licensing infrastructure; contact us for commercial terms.
Security
Passwords are stored with a strong algorithm; two-step verification (TOTP) is optional. Mikro connection details stay in the customer environment. Your private TLS key stays with you.
How to get started
- Technical discovery: Mikro versions, number of databases, which data flows in which direction.
- Setup: we install Connect on your server and define the Mikro connections.
- Pairing: we pair it with EQLEM and set the company mapping and rules.
- Initial full load and reconciliation, then incremental sync.
FAQ
I do not use EQLEM. Can I still get Connect? Yes. The Public REST API and webhooks can be used on their own.
Does Mikro v17 need an extra license? Yes, writes require a Mikro API license.
Are multiple Mikro databases supported? Yes, v16 and v17 can be mixed.
Is there a fee for the certificate? The TLS certificate under eqlem-connect.net is free.
Next step
Request a technical discovery call for a plan that fits your Mikro setup.
Related pages: Module: EQLEM Connect, Solution: EQLEM Connect, Connect AI Assistant.