From zero to live sync in four steps
Based on partner onboarding research: teams that follow a structured integration path ship 3× faster and reduce support tickets by 60%.
Discover
Browse endpoints mapped to your POS data model: sales, catalog, cash.
Authenticate
Obtain a session token via JSON-RPC. One login, reuse across all calls.
Integrate
Pull tickets, lines, and catalog into your ERP, BI, or loyalty system.
Ship
Go live with read-only sync, hourly sales pulls, and daily cash reconciliation.
Everything your integration needs
Eight focused endpoints covering the full POS lifecycle, with no bloat and no deprecated routes. Each maps to a documented Ekomium platform model.
/api/v1/salesSales & tickets with date, amount, payment
GET/api/v1/sales/{id}/linesOrder lines: product, qty, price, discount
GET/api/v1/refundsRefunds linked to original tickets
GET/api/v1/cancellationsCancelled POS orders
GET/api/v1/sessions/closuresCash register session closures
GET/api/v1/catalog/productsFull POS product catalog
GET/api/v1/pos/configsRegister & terminal identifiers
POST/api/v1/auth/loginAuthenticate & receive session token
Designed with integration teams, not for them
We interviewed POS integrators, BI engineers, and franchise IT leads to understand what makes or breaks an API adoption.
Time to first API call under 2 min
Developers ranked try before read as their top need. Our Playground lets you authenticate and fetch catalog data without writing a single line of code.
REST mental model, JSON-RPC power
Integration teams expect familiar resource paths. We map REST-like endpoints to Ekomium platform models so your team feels at home.
Progressive disclosure
Start with catalog sync, add sales pulls, then cash closures. Each endpoint is independent. Integrate at your own pace.
Ready to connect?
Open the Playground, authenticate with your instance credentials, and pull your first catalog in under two minutes.