Skip to content

API Changelog

This page lists every change to the CampOne public API, newest first. The list is exhaustive — anything not on this page has not changed.

Initial public release of the v1 API.

Added:

  • GET /api/v1/public/bookings/ — list bookings (scope bookings:read)
  • POST /api/v1/public/bookings/ — create a pending booking (scope bookings:write)
  • GET /api/v1/public/bookings/{id}/ — booking detail (scope bookings:read)
  • GET /api/v1/public/sites/ — list sites (scope sites:read)
  • GET /api/v1/public/customers/ — list customers (scope customers:read)
  • GET /api/v1/public/invoices/ — list invoices (scope invoices:read)

The API follows the rules below within a major version. They are guarantees that integrators can rely on:

  • Additive changes are allowed within v1. New endpoints, new optional query parameters, and new fields on existing JSON responses can ship at any time, in any minor release.
  • No removed fields, no renamed fields, no changed types within v1. A field that exists today on a v1 response will continue to exist with the same name and type for the lifetime of v1.
  • No new required request parameters within v1. Existing POST calls that worked yesterday will keep working tomorrow without changes to the caller.
  • Breaking changes ship as v2. When a v2 is announced, v1 continues to run for at least 12 months afterwards. Migration windows and deprecation timelines are communicated in advance through this changelog and through tenant-facing channels.

Each release entry uses the same headings:

  • Added — new endpoints, new optional parameters, new response fields
  • Changed — non-breaking adjustments to existing behaviour (e.g. relaxed validation, expanded enum values)
  • Fixed — bug fixes that bring the implementation in line with this documentation
  • Deprecated — features still functional but scheduled for removal in a future major version
  • Removed — only ever appears in a v2+ entry, never within a stable major version

If a heading is absent from a release entry, there are no changes of that kind in that release.