The Core API gives a restaurant’s own systems access to its Unipage data: sales from the till, webshop and kiosk orders, customers, the catalog and gift cards. Typical users are an accounting or ERP integration, a loyalty or CRM system, or a reporting dashboard.
It is the same API the Unipage till (Unipos PLUS) uses to sync, so what you read is what the restaurant sees.
How it works
- The restaurant creates the key. In its Unipage management settings
(Instellingen > Api > API Keys) the restaurant creates a Core API key
(
upg_capi_...) and hands it to you. It is shown once. - One key, one restaurant. A key belongs to a single business (location) and has full access to it. A group with several locations needs one key per location. Keep the key on your server: never ship it to a browser or an app.
- Base URL:
https://api.unipage.eu/{business id}/.... The business id is the short id shown as “ID” on the same settings page (for examplex94d3). - Poll or get pushed. Read sales with the endpoints, or let Unipage push every new sale to you with a webhook.
curl https://api.unipage.eu/x94d3/pos-tickets-by-date/20261028 \
-H "X-API-Key: $UNIPAGE_CORE_API_KEY"Authentication
The key, where to send it, and revoking it.
Endpoints
Sales, orders, customers, catalog and gift cards.
POS order integration
Pull online orders into your own POS or kitchen system.
Webhooks
Get every new sale pushed to your system, signed.
Errors and limits
Rate limits, error bodies and how a client should behave.