Webhooks

Webhooks are automated messages sent from Bilberry to another system when certain events happen — can be thought as setting up a “notification” system between two applications.

Whenever a specific event occurs (like a booking being confirmed or cancelled), Bilberry sends a message with details about the event (called a POST request) to a specified URL.

💡

Through Zapier, or similar no-code tools, you can connect Bilberry webhooks with over 8000+ apps, enabling powerful workflows without needing a developer.


Add a Webhook

  1. In the left main menu, navigate to the Administrator settings → Settings → Webhooks.

  2. Fill inn your Payload URL: This is the destination URL where Bilberry will send the webhook data.

    Example: https://example-system.com/webhooks/

  3. Add your preferred Secret. This is a shared secret used to verify the authenticity of the webhook request. Bilberry includes this value in the request header, and you can use it to validate that the message really comes from Bilberry. The secret itself can be anything.

  4. Add the desired webhook Event → See description of these below.

  5. Make the webhook active by toggle it on Toggle On - 2025-03-18.png

  6. Click Add webhook.

You can activate or deactivate a webhook at any time using the toggle.

For the connection to work, make sure your system is ready to receive and process the JSON data which Bilberry sends through the webhook.

Webhook Events

These are the current webhook events you can subscribe to:

Event

Description

booking.online.confirmed

Triggered when an online booking is successfully confirmed in Bilberry.

booking.cancelled

Triggered when a booking is cancelled in Bilberry.

booking.refunded

Triggered when a booking is refunded in Bilberry.

marked.as.paid

Triggered when a booking is manually marked as paid in Bilberry.

Example Use Cases

1️⃣ Customer Books Online
→ This triggers Bilberry to send a webhook to your system and your system reacts. In this case the reaction can be to grant access or updates a status.

2️⃣ Booking is Cancelled
→ This triggers Bilberry to send a webhook and your system is notified instantly and can react by trigger actions on your end, like freeing up a resource.

3️⃣ Booking is Marked as Paid
→ This triggers Bilberry to send a webhook to your system and your system reacts. In this case it could be to issue an invoice or update internal records.