developer docs
REST APIs, webhooks and an MCP server for the ancon platform. One token, three services, 124 endpoints.
GET /api/v1/Tenants
curl -X GET "https://core-api.ancon.io/api/v1/Tenants" \
-H "Access-Token: $ANCON_TOKEN"Quickstart
- Create an access tokenIn the backoffice at cloud.ancon.io, open the integration menu. Tenant tokens can write everything; outlet tokens write only their own outlet.
- Find your tenantGet tenant details needs no input and returns the
tenantIdmost other paths use. - List your outletsGet outlet list returns the
outletIds for checks, orders and menus. More in Get started.
APIs
Core API
General purpose: tenants, outlets, products, menus, checks, orders, payments, webhooks.
AddOnGroups, Checkouts, Checks, Discounts, Fees, Ingredients and 22 more
Voucher API
Bookkeeping: voucher bases and settlement reports.
User API
Users and companies: customers, companies, guest groups, tenant users.
Guides
- Get startedAccess tokens, token levels, first requests
- FilteringQuery-parameter filtering on list endpoints
- WebhooksEvents, payloads, headers and retries
- Rate limitsLimits and X-Rate-Limit headers
- DeprecationHow endpoints are retired
- MCP and OAuthConnect AI assistants to ancon platform data
Machine-readable
- llms.txtIndex of guides and resources
- llms-full.txtGuides and every endpoint index in one file
.mdAppend to any URL, or sendAccept: text/markdown- core.json · voucher.json · user.jsonOpenAPI specs, synced on every build