Skip to content

Terminology

Term What it means
POS The system in the restaurant that takes and manages orders. In this documentation, “you”.
Integration middleware The system described here, sitting between the ordering platform and your POS.
Portal The web interface where you manage your account, stores, keys and endpoints.
Brand The top-level grouping. A brand holds one or more locations.
Location / store A physical outlet with its own address. Receives orders independently.
Marketplace A store where the restaurant delivers, not a platform courier.
POS endpoint A URL of yours, registered in the portal, where we send notifications.
API key The value sent on Authorization, in both directions of the integration.

The name of your POS solution, assigned when the account is registered. You use a single partner_name per POS solution, even if you serve many clients.

Letters and digits only.

Uniquely identifies a location. The full format is:

partner_name__store_id
│ │
│ └── you choose it when creating the location in the portal
└──────────────── we assign it at registration

Example: with partner_name = gi20 and a store you name 001, the full identifier is gi20__001. The separator is two underscore characters.

You receive it in every order, on the store_id field, and you send it in every store operation.

The order’s alphanumeric code, also printed on the receipt. This is the identifier you search by in order lookup and the one you quote when writing to us about a case.

The order’s internal numeric identifier. Useful for lifecycle operations, but not the lookup key.

Convention Detail
Amounts Always integers, in the currency subunit. 5700 means 57.00 RON.
Dates in orders yyyy-MM-dd HH:mm:ss, in the store’s local time.
Dates in traces Moments recorded by us are UTC, displayed converted to Romanian time.
Dates in temporary closing ISO-8601 with offset, for example 2026-12-20T10:00:00+02:00.