API-first recreation park software: Tillor as headless PMS
Build on headless PMS camping infrastructure with OpenAPI, webhooks and realtime events. Full CRUD on core entities; we extend the API where your integration needs it.

An API is how another program talks to Tillor: your website, accounting package or custom app can read reservations and invoices without opening the Tillor desk. OpenAPI is the official list of what is available; webhooks are automatic signals when something happens, e.g. invoice paid.
Recreation parks rarely run on a single off-the-shelf package. You have a CRM, accounting software, your own website, sometimes on-site hardware. As recreation park software, Tillor must serve as the backend for that stack - the web app is one client on the same API integrators use.
We want you to build workflows without workarounds. Every org endpoint is published in OpenAPI, we ship webhooks and SSE for events, and support MQTT where pub/sub fits better. Missing something for a serious integration? Talk to us: full CRUD on core entities is the baseline, and we can extend endpoints where your use case justifies it.
🔌 OpenAPI is the source of truth
Every org endpoint lives in the OpenAPI spec and can be tried in the API reference. List, read, create, update and delete for customers, occupations, invoices, products, meters and tasks are available today; the spec shows exactly which methods are live per resource.
Copy link to this sectionIntegrator scenarios
Your own booking widget. Your site posts reservations straight to Tillor, reads availability via list endpoints and sends confirmation mail from your stack. Tillor stays the source for occupations and invoicing.
Data warehouse or BI. Overnight jobs pull customers, open invoices and meter readings via paginated list calls. No stale CSV export; you read the same fields as reception.
Event-driven coupling. On invoice paid or customer created, a webhook triggers your middleware. Prefer an open stream? SSE delivers the same event keys live.
On-site hardware. Barriers, printers and identity readers talk locally through the Connector; your cloud integration stays on HTTP and events.
Copy link to this sectionCRUD on core entities
For every base entity in Tillor the goal is clear: you should be able to list, read, create, update and delete records over HTTP without opening the UI.
In practice, per org path under /api/orgs/{orgId}/...:
| Action | Typical HTTP method |
|---|---|
| List (pagination and filters) | GET on the collection |
| Read | GET on {id} |
| Create | POST |
| Update | PATCH or PUT (partial vs full replace, per entity in OpenAPI) |
| Delete | DELETE |
Today customers, occupations, invoices, products, meters and tasks follow that pattern. Reservations and terrains follow the same direction; check OpenAPI for the current method set per resource.
Workflow actions (check-in, post invoice, extend stay) get an explicit endpoint instead of a hidden screen action. Your integration stays stable as the UI evolves.
Copy link to this sectionFlexibility and extension
Tillor is not a closed island. We want partners to slot Tillor into existing landscapes:
- Standard REST with Zod-schematised input and output in OpenAPI
- Org-scoped URLs and headers (
x-api-key,X-Tillor-Org-Id) as documented in HTTP API - Rate limits you can plan for (5000 requests per 60 seconds per key)
- The same events via webhook, SSE or MQTT, whichever your stack handles best
Need an extra list filter, bulk action or missing delete for a coupling? On request we agree API extensions when they fit the data model and benefit other customers. No secret one-offs: new endpoints land in OpenAPI so everyone can use them.
Copy link to this sectionBenefits for your project
- One contract: OpenAPI + API reference, no reverse-engineering the UI
- Headless PMS: Tillor as backend for your front-end, portal or mobile app
- Events out of the box: skip polling when webhook or SSE is enough
- Local + cloud: Connector for on-prem hardware, API for central systems
- Docs for AI and codegen: developer docs and
llms-full.txtfor tooling
Copy link to this sectionWhat it looks like for integrators
Every integration starts with an API key: open the user menu (highlight 1) and go to API keys (highlight 2).
Authentication, org headers, rate limits, webhooks and code examples live in HTTP API, Webhooks and Examples. Try endpoints in the API reference or via OpenAPI.
Building on Tillor? Request a demo and we will review OpenAPI, events and your use case together.
More from the blog

✨ Camping Vlasaard chose recreation park software: from paper to one PMS
How Vlasaard NV chose campsite management software to replace paper, spreadsheets and separate tools with one PMS for KC80 barriers, LoRa meters, ICY electricity and Mollie payments.

Prepaid shower system for campsites: shower and door with one NFC tag
A prepaid shower system for your campsite: shower and open the door with an NFC wristband or key fob, start washing machines with a QR code.

Custom fields in campsite software: extra data per guest or pitch
Record what your park needs to track, from the trailer's licence plate to the number of the electricity cabinet, with custom fields in your campsite management software.