API Overview
The CampOne API gives third-party systems read-mostly access to a tenant’s operational data over HTTPS, using REST conventions and JSON payloads.
What the API is
Section titled “What the API is”A versioned, authenticated REST interface for a single tenant’s data. You authenticate as a tenant (not as a user), you read most resources, and you can create bookings. All responses are JSON. All requests use the bearer-token scheme described in Authentication.
The current scope covers:
- Bookings — list, retrieve, create
- Sites — list
- Customers — list
- Invoices — list
Who it’s for
Section titled “Who it’s for”This API is designed for back-office and partner integrations:
- Channel managers syncing availability and reservations
- Accounting and ERP systems pulling invoices
- Partner tools that need a structured view of a tenant’s bookings or customer base
It is not a guest-facing API. Guests interact with the operator’s booking widget and guest portal, which are separate products. Do not build a public-facing reservation site directly on top of these endpoints.
Base URL
Section titled “Base URL”| Environment | Base URL |
|---|---|
| Production | https://api.campone.ch |
| Staging | https://api-staging.campone.ch |
All paths in this reference are relative to the base URL plus the version prefix (see below).
Versioning
Section titled “Versioning”The current version is v1. Every endpoint lives under:
/api/v1/public/...Within v1 only additive changes are made:
- New endpoints
- New optional query parameters
- New fields in JSON responses
Existing v1 fields are not renamed, removed, or retyped. Any change that would break a consumer goes into a future /api/v2/, with v1 continuing to run during a deprecation window.
Plan accordingly: ignore unknown fields you don’t recognise rather than rejecting them, and don’t depend on field ordering.
See the API changelog for the full history of versioned changes.
What is not in v1
Section titled “What is not in v1”These domains exist in the platform but are not exposed in the public API yet:
- POS transactions and daily-close reports
- Vouchers and gift cards
- Channel-manager push (only pull endpoints are exposed)
- Site infrastructure (sanitary blocks, power boxes, electricity meters)
- HESTA / guest registration data
- Loyalty program data
If you need any of these, contact your CampOne representative — they will be added in a later API version when the contract is stable enough to commit to.
Next steps
Section titled “Next steps”- Read Authentication to understand how API keys, scopes, and the bearer header work.
- Skim Errors and status codes and Pagination and filtering before you start coding — the conventions are the same on every endpoint.
- Then move on to the per-endpoint pages for bookings, sites, customers, and invoices.