Siloed Systems
Reservation, availability, pricing, and guest data live in separate platforms that can't talk to each other, forcing staff to re-enter information manually.
Manage.Camp
API & Data Connectivity
Connect booking engines, partner systems, and custom tools through a unified, documented API layer for reservations, availability, pricing, unit data, and webhooks.
Reservation, availability, pricing, and guest data live in separate platforms that can't talk to each other, forcing staff to re-enter information manually.
Overnight batch imports break silently, causing double bookings and stale availability across connected sales channels.
Every new partner integration requires bespoke development, straining IT budgets and delaying go-live timelines.
Ad-hoc file transfers and shared credentials expose sensitive guest data without audit trails or access controls.
A documented JSON API for reservations, availability checks, pricing quotes, and unit data — easy for developers to integrate and keep tenant-scoped.
Push events for reservation changes, check-ins, check-outs, and availability updates so partner systems react without constant polling.
Use reservation, availability, pricing, and webhook endpoints as a clean integration layer for channel manager, OTA, or partner projects.
Track every webhook delivery, inspect failures, and manually retry failed or dead-letter events from the built-in log viewer.
Issue per-integration API tokens with granular scopes, optional camp restrictions, expiry dates, and API access logs.
Every API call is authenticated with scoped tokens, encrypted in transit, and logged for traceability. Rate limiting, camp-scoped access, and signed webhooks help protect your integrations.
Q1
Most custom integrations need a developer or integration partner. We provide API docs, webhooks, scoped tokens, and delivery logs to keep implementation straightforward.
Q2
Create a scoped token, run test calls against the supported endpoints, and validate behaviour in the API access log and webhook delivery log before going live.
Q3
The API uses JSON and documented request/response schemas. Collection endpoints include pagination, and supported filters are documented per endpoint.
Q4
Failed deliveries are retried automatically up to 5 attempts and then moved to dead-letter status. You can inspect each attempt and manually retry failed deliveries.
Q5
Yes. Tokens can be limited to specific camp IDs and combined with granular scopes and optional expiry dates.
Talk to our team about API access, supported flows, and rollout planning.
We use cookies to ensure the application works correctly and to improve your experience. Cookie Policy
We use cookies to ensure the application works correctly and to improve your experience.