Webhooks

Push booking, invoice, lease and customer events to your other systems automatically, within seconds of them happening.

When You'd Use Webhooks

Webhooks connect Camper BMS to systems that live outside it - a CRM, a staff chat, a spreadsheet, or a no-code tool like Zapier (which can pass events on to hundreds of other apps without any code). You don't need a developer, and if you don't connect anything, nothing depends on this feature.

Accessing Webhooks

Navigate to Integrations > Webhooks from the main navigation.

Adding an Endpoint

Click to add an endpoint and enter the secure (HTTPS) web address that should receive the events.
Choose which events it should receive, or leave them all selected to receive everything.
Tick the acceptance checkbox to confirm you accept responsibility for data sent to this endpoint.
Copy the signing secret so your receiving system can verify incoming messages.
Click Send test to fire a sample event and confirm the other end is receiving it.

You can pause, resume or delete a connection at any time.

Events You Can Listen For

Bookings - reserved, pending, confirmed, cancelled, or changed (a new check-in, check-out or site)
Arrivals and departures - checked in, checked out
Invoices - paid, refunded
Leases - created, activated, renewed, ended
Customers - a new guest record created

What's in the Data

Each message includes the event name, when it happened, and which campground it relates to, plus the details for that event (the guest and booking for a booking event, the invoice for an invoice event, the lease and its tenants for a lease event).

Consent travels with the data. Every guest in a payload carries a marketing-consent flag so your receiving system can respect it.
The IDs are safe to share. Identifiers in the payload are public reference codes, never internal database IDs.

Security and Reliability

HTTPS only - endpoints must be secure web addresses.
Every message is signed with HMAC-SHA256 using your endpoint's secret. Your receiving system can recompute the signature to confirm the message genuinely came from Camper BMS. The Webhooks page provides copy-ready PHP, Node and Python verification examples.
Automatic retries - if your endpoint doesn't respond, Camper BMS retries a couple of times over the next few minutes. Each connection shows its consecutive-failure count, and a persistently broken endpoint is automatically paused (and you're emailed) so it isn't hammered.
Destination checks - Camper BMS verifies the destination is a genuine external server, blocking attempts to point webhooks at internal addresses.

Delivery Log

Every delivery attempt is recorded - the event, where it went, whether it succeeded, the response, and the exact data sent. Each delivery has a Resend button to re-fire a payload if the other system was down. Delivery records are kept for 90 days, then automatically deleted.

Billing and Consent

Webhooks are included at no extra charge - not metered. Like the API, they're available on any paid plan and pause automatically while an account is restricted (for example, an unpaid invoice).
Webhooks are not gated behind marketing consent - they're operator-directed data flows, so the consent decision belongs to your receiving system (which is why the consent flag travels in every payload).

Developer Detail

For payload formats, signature verification and the complete event list, see your developer tools.