View .md

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?

Existing customer

  1. 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).
  2. 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

  1. Get tenant details needs no input and returns the tenant your token belongs to. The tenantId is required in many other URLs.
  2. 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

Choose a service

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.

Next