Build on the same API Camping.care runs on
Every part of Camping.care runs on one documented REST API, and you get all of it: 583 endpoints across 43 APIs. Build your own booking engine, connect your hardware, or put your app straight into the screens campsite staff use every day.
curl "https://api.camping.care/v21/reservations?limit=2" \ -H "Accept: application/json" \ -H "Authorization: Bearer {secret_key}"HTTP/1.1 200 OK[ { "id": 1000, "reservation_id": 1, "accommodation_id": 3000, "status": "confirmed", "payment": "paid", "arrival": "2026-07-14 12:00:00", "departure": "2026-07-21 11:59:59", "total": 496 }, // …]- 583
- 43
- 400+
- 7
The screen is just one of the clients
In a classic setup the screens, the business logic and the database are one product, and everything else gets an export. In an API-first, headless platform the data and logic sit behind one documented API, and every screen, ours included, is a client of it. Front ends can be added, swapped or built by you, without anyone changing the core.
- Screens, logic and data are built as one block. The vendor's own screens are the only way in.
- Other systems get CSV exports, nightly syncs or a one-off plug-in, so they are always a few hours behind.
- A new connection is a feature request in someone else's queue.
- Data and logic sit behind one documented REST API. The Camping.care app itself is just a client of it.
- Your website, a kiosk, a channel or an AI agent talks to the same API in real time, and hears back through webhooks.
- A new connection is an afternoon of code (by us, by a partner, or by you).
Our app uses the same API you do
There is no private back door. The screens campsite owners use every day are built on the 583 endpoints in the public reference, so if our interface can do it, so can your code.
Bring your own front end
Build a booking engine in your website's own design, a kiosk flow or a guest app. The platform handles availability, pricing and payments; you decide what the guest sees.
Real time, not tonight
Webhooks tell your system the moment a reservation is made, a guest checks in, an invoice is finalised or a payment arrives, signed with HMAC-SHA256 and retried if your endpoint is down.
583 endpoints across 43 APIs
Everything the platform does is in the reference, from a single reservation to the electricity meter on pitch 42. Grouped here by what you are likely to be building.
Reservations and booking
Reservations API
58 endpointsAvailability API
4 endpointsPrice Calculation API
12 endpointsCache API
3 endpointsChannels API
5 endpointsiCals API
5 endpointsWidgets API
4 endpointsVouchers API
9 endpoints
Guests
Contacts API
20 endpointsReviews API
5 endpointsDocuments API
12 endpointsEmail API
6 endpointsLicense plates API
6 endpointsCode API
12 endpointsBalances API
12 endpoints
Accommodations and pricing
Accommodations API
54 endpointsTypes API
35 endpointsCategories API
10 endpointsRates API
18 endpointsProducts API
22 endpointsExchange rates API
2 endpoints
Money
Invoices API
23 endpointsPayments API
24 endpointsLedgers API
9 endpoints
Operations
Tasks API
23 endpointsWorkflows API
10 endpointsDevices API
11 endpointsKiosk API
9 endpointsEnergies API
6 endpointsNotifications API
2 endpoints
Platform
Administrations API
80 endpointsUsers API
9 endpointsApps API
14 endpointsOAuth 2 API
2 endpointsWebhooks API
8 endpointsFields API
19 endpointsTags API
5 endpointsMedia API
7 endpointsTranslations API
3 endpointsTimezones API
1 endpointAudit API
1 endpointLogs API
1 endpointAPI status
2 endpoints
Apps that live in the interface, not next to it
The App Store is where campsites install their integrations, and anyone can build for it. Your app runs sandboxed inside Camping.care, written in any language and hosted on your own domain, and registers widgets in the places staff already work.
Any language, your own hosting
An app is a URL. We load it in a sandboxed frame, so it can be Laravel, Vue or whatever you already run, on your own domain.
Installed with consent, signed in with OAuth 2.0
When a campsite installs your app, they approve the scopes you ask for. You receive an authtoken and swap it for API access, so nobody emails API keys around.
One campsite, a few, or all of them
Publish an app privately for a single park, for a group you choose, or to every campsite on the platform.
It talks back to the interface
Widgets send a message to set their own height, or to refresh the reservation or guest they sit on after your app has changed it through the API.
Seven places an app can appear
Each widget is loaded with the ID of the reservation or guest it sits on, the user's language, and an authtoken to call the API as the signed-in user.
- App page
- Dashboard
- Reservation
- Reservation tab
- Contact
- Contact tab
- Online booking form
// Size the widget to its content, and reload the// reservation your app just changed through the API.window.top.postMessage({ height: document.body.scrollHeight, refresh: true}, '*');Four ways to authenticate, one for each kind of client
Every key, app and token belongs to its own user with its own scopes, so every call can be traced back to who (or what) made it.
Public key
Safe to use in a browser. Reads what a guest may see (the park, its accommodations, availability and prices) and is what an online booking engine runs on.
Secret key
Server-to-server access, sent as a Bearer token. Create as many as you need; each one becomes a user with exactly the scopes you give it. Never ship it to a browser.
OAuth 2.0
The campsite approves your app's scopes at install. You swap the authtoken for a token that lasts an hour and refresh it as you go. One header picks which park you are working in.
Reservation based
Signs a guest in with their own reservation, and opens that one booking only. Built for my-reservation pages, online check-in and guest apps.
curl "https://api.camping.care/v21/users/me" \ -H "Accept: application/json" \ -H "Authorization: Bearer {secret_key}"Every endpoint has its own scope
There are more than 400 scopes, one for each thing the API can do. Give an app or a key exactly the rights its job needs, and it cannot reach any other data.
- Scopes are per endpoint. Reading one reservation, listing reservations and adding one are three separate rights.
- Set per API key, per app and per user. A door-lock integration never needs to see your invoices.
- Campsites see and approve the scopes an app asks for before they install it.
- The audit log records every action, whether a member of staff or the API made it.
Good to know before you start
- REST and JSON
- 120 calls a minute
- Signed webhooks
- HTTPS and UTC