Unipage runs ordering, POS and back office for restaurants. These docs are for developers who build on top of it: your own webshop or app, or an integration with the restaurant’s accounting, ERP or kitchen systems. Unipage stays the source of truth for the catalog, opening hours, order slots, prices, orders and sales.
Storefront API
Build a fully custom webshop or ordering app for a Unipage restaurant. Read the menu and schedule from the browser, place orders from your server.
Core API
The restaurant’s own back-office API, with a upg_capi_... key: till
sales, orders, customers, the catalog and gift cards.
Which API do I need?
| You are building | Use |
|---|---|
| Your own webshop or ordering app for a restaurant | the Storefront API |
| An accounting, ERP, BI or CRM integration that reads sales, orders or customers | the Core API endpoints |
| Your own POS or kitchen system that receives the restaurant’s online orders | the POS order integration |
| Something that reacts the moment a sale or an order happens | webhooks: pos.sale for till sales, order events for your storefront’s orders |
Start here
Request your keys
Ask Unipage for a public and a secret storefront key, and list every origin your shop is served from. See Keys and CORS.
Make your first call
curl https://api.unipage.eu/storefront/v1/store \ -H "X-Unipage-Key: upg_sf_pk_..."Build the checkout
Follow the quickstart from menu to paid order, with the API reference next to you.
Get a key from the restaurant
The restaurant creates a Core API key (
upg_capi_...) in its Unipage settings and gives it to you, with its business id. See Authentication.Make your first call
curl https://api.unipage.eu/x94d3/pos-tickets-by-date/20261028 \ -H "X-API-Key: upg_capi_..."Read, or get pushed
For agents
Every page is also available as Markdown: add index.md to its URL, or use
Copy as Markdown at the top of the page. /llms.txt indexes
the whole site, and /llms-full.txt holds all of it in one
file.