Skip to main content
Building on Camping.care?

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.

GET /v21/reservations
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  },  // …]
documented endpoints
583
APIs, from reservations to energy
43
scopes, one per endpoint
400+
places an app can appear
7
What does API-first actually mean?

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.

Classic cloud setup
  • 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.
API-first, headless
  • 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.

What can you reach?

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 endpoints

    Read, create and change bookings (guests, places, options, nights, status and payment terms) plus PDFs and reports.

  • Availability API

    4 endpoints

    Check which places and categories are free for a period, before you create the reservation.

  • Price Calculation API

    12 endpoints

    Work out the exact price of a stay, with extra guests, required options, promo codes, discount cards and tax.

  • Cache API

    3 endpoints

    Pull availability and prices for a date range in bulk, so an online travel agent can price from its own database.

  • Channels API

    5 endpoints

    The source of every booking: direct, Booking.com, Airbnb and the rest.

  • iCals API

    5 endpoints

    Sync bookings from external calendars, such as Airbnb and Booking.com, through iCal feeds.

  • Widgets API

    4 endpoints

    Manage the booking widgets embedded on your website.

  • Vouchers API

    9 endpoints

    Discount vouchers guests can redeem while they book.

Guests

  • Contacts API

    20 endpoints

    Guest records, kept unique by email address, with tags, custom fields and mappings.

  • Reviews API

    5 endpoints

    The reviews guests leave after their stay.

  • Documents API

    12 endpoints

    Document templates and documents guests sign, such as contracts and terms and conditions.

  • Email API

    6 endpoints

    Email templates, and transactional emails sent to guests.

  • License plates API

    6 endpoints

    Vehicle registrations linked to guests and reservations, for barriers and number-plate cameras.

  • Code API

    12 endpoints

    Access codes for the gate, WiFi, locks and check-in.

  • Balances API

    12 endpoints

    Prepaid accounts guests top up and spend on site.

Accommodations and pricing

  • Accommodations API

    54 endpoints

    Everything you rent out: descriptions, media, places, add-ons, tags and the rates linked to it.

  • Types API

    35 endpoints

    Place types, from tent pitch and caravan pitch to glamping pod and chalet, and the objects behind them.

  • Categories API

    10 endpoints

    Groups of place types, used by availability search and the booking widgets.

  • Rates API

    18 endpoints

    Per-night prices with date-based periods.

  • Products API

    22 endpoints

    Billable extras on a reservation (tourist tax, linen, breakfast) with add-ons and deals.

  • Exchange rates API

    2 endpoints

    Currency exchange rates, for pricing in more than one currency.

Money

  • Invoices API

    23 endpoints

    Invoices with their rows and tags, as PDF, with a payment QR code or as UBL for your accountant.

  • Payments API

    24 endpoints

    Payments, the payment providers and methods behind them, and PDF receipts.

  • Ledgers API

    9 endpoints

    Ledger accounts and mappings, so bookkeeping happens automatically.

Operations

  • Tasks API

    23 endpoints

    Housekeeping and maintenance tasks, created from templates, assigned to staff and tracked until done.

  • Workflows API

    10 endpoints

    Automations that run when something happens, like an arrival or a payment.

  • Devices API

    11 endpoints

    The hardware on site: kiosk terminals, gate scanners and cloud connectors.

  • Kiosk API

    9 endpoints

    Self-service check-in kiosks on your campsite.

  • Energies API

    6 endpoints

    Electricity meter readings on electric pitches, and the energy invoice that follows.

  • Notifications API

    2 endpoints

    In-app notifications for your staff.

Platform

  • Administrations API

    80 endpoints

    Your parks and their settings: users, roles, age and VAT tables, places, cards, API keys, media and partners.

  • Users API

    9 endpoints

    Staff accounts and their rights.

  • Apps API

    14 endpoints

    Apps in the App Store, their versions, and the administrations they are installed in.

  • OAuth 2 API

    2 endpoints

    Swap an app's authtoken for an access token, and refresh it.

  • Webhooks API

    8 endpoints

    Real-time event notifications sent to your HTTPS endpoint, signed with HMAC-SHA256.

  • Fields API

    19 endpoints

    Custom fields and forms for guests and reservations.

  • Tags API

    5 endpoints

    Colour-coded labels for reservations, guests and payments.

  • Media API

    7 endpoints

    Upload images and files, and attach them where they belong.

  • Translations API

    3 endpoints

    Interface text in every supported language.

  • Timezones API

    1 endpoint

    The time zones the platform supports.

  • Audit API

    1 endpoint

    The audit log of every action, by staff or by the API.

  • Logs API

    1 endpoint

    Write your own log entries from an integration.

  • API status

    2 endpoints

    The API version and a health check.

Counted from the public Postman reference (V2.1) in November 2026. The Articles and Search APIs are deprecated and left out of the count.

Open the full API referenceOpens in a new tab.
Want your app inside Camping.care?

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 pageYour app's own full page, opened from the App Store.
  • DashboardA tile on the dashboard staff see when they log in.
  • ReservationA block inside the reservation window.
  • Reservation tabA whole tab on the reservation, when you need more room.
  • ContactA block inside the guest window.
  • Contact tabA whole tab on the guest record.
  • Online booking formA step in the booking engine, with the cart and price draft it belongs to.
Widget → Camping.care
// 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}, '*');
Read the App Store documentationOpens in a new tab.
How does your code sign in?

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

    For booking engines and websites

    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

    For your own servers

    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

    For App Store apps

    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

    For guest-facing pages

    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.

Secret key, from your server
curl "https://api.camping.care/v21/users/me" \  -H "Accept: application/json" \  -H "Authorization: Bearer {secret_key}"
Read the authentication docsOpens in a new tab.
What can an app see?

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.
How rights and scopes workOpens in a new tab.

Good to know before you start

Predictable resource URLs, standard HTTP verbs and status codes.
REST and JSON
The rate limit, with X-Ratelimit headers on every response.
120 calls a minute
HMAC-SHA256, retried after 5 seconds, 30 seconds and 5 minutes.
Signed webhooks
Every call over HTTPS, every date and time in UTC.
HTTPS and UTC
DemoStart free