Get started
All requests to the ancon platform APIs are authorized with an access token sent in the Access-Token header. A missing or invalid token returns 401 Unauthorized.
What do you want to do?
- You have, or represent, an existing customer (an ancon platform account with a restaurant or chain) and want an API key for it: existing customer.
- You want to integrate as a partner and open the integration to many restaurants now and in the future: partner integrations.
Existing customer
- In the backoffice (cloud.ancon.io), open the integration menu and create an access token. Decide whether it is an outlet-level or tenant-level token (see below).
- Follow the API reference to implement your integration.
Token levels
| Level | Access | | --- | --- | | Tenant | Read and write on all endpoints. | | Outlet | Read on tenant-level data; read and write on outlet-level data for the outlet the token was created for. |
First requests
- Get tenant details needs no input and returns the tenant your token belongs to. The
tenantIdis required in many other URLs. - Get outlet list returns every outlet under the tenant (an outlet-level token only sees its own outlet).
curl "https://core-api.ancon.io/api/v1/Tenants" \
-H "Access-Token: $ANCON_TOKEN"
Every response includes
X-Rate-Limit-*headers, see rate limits.- A correlation id. Include it in any support question or bug report. You can also send your own as
x-correlation-id(a UUID is best) to correlate logs on both sides.
Choose a service
- Core API: tenants, outlets, products, menus, checks, orders, payments.
- Voucher API: bookkeeping, voucher bases and settlement reports.
- User API: customers, companies, guest groups, tenant users.
Working with AI agents
Every reference page has a markdown twin (add .md to the URL), the raw OpenAPI specs are at /specs/core.json, /specs/voucher.json and /specs/user.json, and llms.txt indexes everything. To let an AI assistant act on ancon platform data directly instead, see MCP and OAuth.