Endpoints

All paths are relative to https://api.unipage.eu/{business id} and need the Core API key in the X-API-Key header.

Sales: GET /pos-tickets-by-date/{Ymd}

The VAT receipts the till made on one day, for example /pos-tickets-by-date/20261028. The day runs from midnight to midnight in the restaurant’s timezone, by consumption date. Refund receipts are included (is_refund: true).

{
  "tickets": [
    {
      "id": "k3m9a",
      "business_id": "x94d3",
      "order_id": null,
      "customer_id": "p8q2r",
      "ticket_id": "...",
      "type": "VAT",
      "is_refund": false,
      "operator_name": "Eva",
      "terminal_name": "Kassa 1",
      "consumption_date": "2026-10-28 12:41:07",
      "ticket_date": "2026-10-28 12:41:09",
      "ticket_lines": [
        {
          "product": "Broodje kaas",
          "category_reference": "Broodjes",
          "amount": 2,
          "unit_price_with_vat": 4.5,
          "vat_rate": 6,
          "total_price_without_vat": 8.49,
          "total_vat": 0.51,
          "total_price_with_vat": 9
        }
      ],
      "payment_lines": [
        { "payment_method": "CASH", "payment_name": "Cash", "amount": 9, "rounding": 0 }
      ]
    }
  ]
}

The receipt fields

This shape is a contract: keys are added over time, never renamed or removed.

Orders: GET /orders/{Y-m-d}

The orders created on one day, for example /orders/2026-10-28, with a successful status: webshop, app, kiosk and delivery-platform (Uber Eats, Deliveroo) orders. Returned as an array.

The main keys: id, created_at and updated_at (Unix seconds), order_number_for_company, status, order_type, order_source, payment_method, is_paid, total_price, delivery_cost, service_cost, coupon_reduction, coupon_string, wallet_amount, customer fields (user_firstname, user_lastname, user_email, user_phone, user_id), delivery fields, takeout_delivery_timestamp, order_notes, platform fields (display_id, delivery_type, dropoff_notes, unmatched_items), and orderItems[] with their options.

Customers

GET /customers

Every customer of the restaurant’s organization, as {"data": [...]}. Deleted customers are included, with deleted_at set, so you can remove them on your side.

The list is cached for 15 seconds. Sync with updated_after instead of downloading every customer each time.

GET /customers/{id}

One customer, as {"data": {...}}.

The customer fields: id, user_id, firstname, lastname, full_name, email, phone, address fields, company_name, vat_number, notes, nfc_uid, profile_picture_url, last_ordered_at, did_give_marketing_consent, created_at, updated_at, memberships, wallet, loyalty_wallet, metadata, deleted_at.

POST /customers and POST /customers/{id}

Create or update a customer. Answers {"success": true, "customer": {...}}.

curl -X POST https://api.unipage.eu/x94d3/customers \
  -H "X-API-Key: $UNIPAGE_CORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "eva@example.com", "firstname": "Eva", "lastname": "Peeters"}'

Other locations: GET /linked-businesses

{"businesses": [{"id": "x94d3", "reference": "..."}]}: every location of the group, this one included. Each needs its own key.

Catalog

GET /generic/categories and GET /generic/products return the catalog as the till receives it, with prices, options and translations. GET /generic/products accepts updated_after (Unix seconds) to fetch only the products changed since your last sync, and category_id to limit it to one category.

Gift cards

A gift card has id, code, name, amount, balance, formatted_balance, is_valid, recipient_name, expires_at, redeemed_at and created_at.

Without a key: /public/{domain}

What the public webshop already shows is also available without a key, by the shop’s domain (for example myshop.unipage.eu):

For a custom ordering experience, use the Storefront API instead: it also quotes carts and places orders.