Introduction
What the Hatcel API is and how it works
The Hatcel API lets your own software read a Hatcel workspace - its venues, customers, bookings, orders, products, events and gift cards - and keep its customers, tags and lists up to date.
Base URL
Every request goes to https://api.hatcel.com, over HTTPS. Requests and answers are JSON; a refusal is application/problem+json.
Base URL
The API answers on that host only: hatcel.com/api/rest is a 404. Every answer carries X-Robots-Tag: noindex, so no response ever ends up in a search engine.
Server to server only
A key reads a whole workspace, so it belongs on your server and never in a browser, an app or a page somebody can view source on. The API sends no CORS headers, so a browser's request is refused before it is made.
What you can do
Machine-readable docs
- openapi.json - the whole API as an OpenAPI 3.1 document, for code generators and API clients.
- llms.txt and llms-full.txt - these docs as plain text, for AI agents.
Next steps
- Quickstart: make a key and send your first request.
- Authentication: how a key is sent and kept.
- API reference: every object and endpoint.