Code
Partner API v1, the shop contract on @delieta/shop-runtime and the refresh signal — start your integration here.
This section is for someone connecting Delieta to a shop, a till or their own backend. The company panel is described in Features.
What is here
Each of the three pages answers one question.
| Question | Page |
|---|---|
| How do I read the menu, take an order from the shop, create an order from a till, take a reservation or a catering inquiry? | Partner API |
How do I build a shop on @delieta/shop-runtime that never exposes a secret? | Storefront contract |
| Will Delieta notify my server when a status changes? | Webhooks — no, check the status with a GET. The shop only receives a signed refresh signal. |
The same contract in machine-readable form: GET /api/v1/openapi (no key, rate-limited by IP). These pages are checked against that document.
Rules shared by all pages
The key identifies the company. The tenantSlug and companyId fields in the body are ignored.
Money is integer grosze. 3200 is 32.00 zł. v1 has no currency other than PLN.
Errors are RFC 9457 application/problem+json. Identify the error by the code field, never on title.
A publishable key has exactly catalog:read and checkout:create: it reads the menu and shop settings and accepts a shop order, a reservation and an inquiry. A secret key creates till orders and quotes ETA. Keep both keys on the server, never in the browser — the storefront contract helps you get this right.
First integration, step by step: For developers.