What is a booking webhook?
On this page
How does a booking webhook reach another application?
A booking webhook sends a message after a booking event, so your application can react to a change without repeatedly requesting the latest booking list. The sender needs a destination endpoint, and the receiver needs code that validates the message and decides what action to take.
Start with one event. For example, one confirmed appointment could create one task in your own application after its receiver accepts the booking-created notification.
- Register an endpoint and choose the booking events it should receive.
- Accept the HTTP request and preserve its raw body for signature verification.
- Verify the signature and timestamp before processing the event.
- Record the event ID and carry out the downstream action once.
The booking webhook meaning is about notification, not a promise that a CRM integration already exists. You still need a receiving system or connector that understands the payload.
What does a signed booking webhook prove?
A correctly verified signature lets the receiver check that a message was generated using the shared secret and hasn't changed since signing. It doesn't prove that the receiving application's own business action succeeded, and it doesn't remove the need to reject old messages.
Keep the secret private. A receiver should compare the expected signature safely and apply a timestamp tolerance before accepting the request as a current event.
| Mechanism | What it answers |
|---|---|
| Signature verification | Was this payload signed with the expected secret? |
| Timestamp check | Is this signed request recent enough to accept? |
| Duplicate-event check | Has this event already produced its action? |
These checks serve different purposes. Calling a booking webhook "an automatic integration" skips part of the work, because sending a message and safely processing it are separate jobs.
Why might one booking produce repeated deliveries?
One booking can produce repeated deliveries when the sender doesn't receive a successful response and retries. For example, if a receiver stores a task but its response is lost, the next delivery must find that processed event instead of storing a second task.
Duplicates need a plan. In that example there are two delivery attempts, one event ID and one intended task; the count of HTTP requests isn't the count of appointments.
Store the ID alongside your processing result. Return a successful response after safely accepting responsibility for the work, and avoid making a slow downstream action the only record that the message arrived.
What does Barq Meet send in booking webhooks?
Barq Meet sends JSON event notifications for booking changes and signs its requests using HMAC-SHA256. The payload includes an event ID, event name and booking data, so a receiving application can distinguish the event from the appointment it describes.
Keep the original bytes. We sign the timestamp together with the raw JSON body. Preserve those original bytes when verifying; parsing and serialising the object again can change the content being checked.
We retry unsuccessful deliveries with backoff. Our delivery history lets hosts inspect attempts, but your application still needs duplicate protection and a process for failures in its own downstream systems.
We expose booking events through the API and webhook controls. A webhook alone won't create a native CRM connector; build or configure the receiving integration for the fields and actions you need.
Use the glossary of scheduling terms for related concepts. Check what developer access includes, then create an account for booking event notifications.
Frequently asked questions
Is a webhook endpoint the same as my booking page?
No. The endpoint receives machine-readable event messages; the booking page lets a guest choose and confirm a time. Your receiving application processes the notification after a booking change instead of asking the guest to visit that address. Point the webhook at a receiver you control, with the public booking address kept as the screen where guests arrange appointments.
Should a webhook handler trust the booking details immediately?
No. Verify the signature and timestamp before acting on the payload, then validate the event structure. A URL that receives requests can receive unauthorised requests too; possession of its address doesn't prove who sent a message. Verify the signature and process the event through your receiver's own validation before using it to change an internal customer record.
Can the same booking notification arrive twice?
Yes. A failed or uncertain delivery can be retried, so your handler should recognize a previously processed event. Use the payload's event ID to prevent a repeated notification from creating another copy of the same downstream action. Store the delivery identity and make processing repeatable, so a retry doesn't create a second internal record for the same notification.
Related pages
- Booking API and webhooks for your own application
Build with REST, OpenAPI and signed webhooks. Browser keys require allowed origins; server keys stay private. Default API access is 600 requests/minute.
- Scheduling glossary: booking and calendar terms explained
Understand booking pages, events, free/busy and time-zone terms. Follow one 30-minute appointment through the scheduling vocabulary.
- Free scheduling, with every feature included
Get booking pages, Google Calendar and Meet, reminders, branding controls, embeds and API access for $0. No card or paid plan.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link