Migrated from Redmine #1473 | Author: Wout B Status: New | Priority: Normal | Created: 2025-09-29
Hello,
We’re actively using the booking webhook to keep our CRM synchronized with SimplyBook. However, we’ve discovered that when client details are updated on an existing booking, this does not count as a “Booking Update” trigger.
This creates a synchronization gap: post-booking changes to client data (e.g., phone, email, or other contact details) are not pushed to our system, leaving our CRM out of sync with SimplyBook.
At present, the only workaround would be to perform nightly full syncs of clients/bookings. Given daily rate limits, this approach is inefficient, increases API load, and risks introducing further problems instead of solving them.
Feature Request
Add webhook triggers for:
When client information on an existing booking is updated.
(Ideally) when any client record is modified, even outside of a booking context.
Impact
Ensures external systems remain aligned with SimplyBook in real time.
Reduces reliance on heavy sync processes, preserving API limits.
Improves data accuracy and integrity across integrated platforms.
This small extension of webhook functionality would make a big difference for integrations like ours, which depend on SimplyBook as the authoritative source of truth.
Can you please give us more information about your use case?
We have 2 types of client entity in the system: client with booking when no client login is enabled (no way to edit client without editing a booking then) and client profile if client login is enabled. The question is what exactly you need to sync and why?
Hi,
Appreciate the follow-up; we’re indeed working with no client login - this is to reduce the “difficulty” to order bookings.
Introducing it would cause a lot of changes in the current workflow.
The use-case for this would be to make sure the CRM behind SB is up to date, so right now when a booking comes into the CRM system, the client info is saved. But when the client info is then changed afterwards in SB, it does not reflect in the CRM since this doesn’t trigger a webhook update on the booking itself. Having webhooks available for customer info updates, be it with or without client login, would solve this.
Hello,
we currently neither have ‘change client’ webhook nor call booking webhook for client data changes.
We can consider adding your case, but pay attention one client can have several bookings even in case client_login is disabled. Do you really want to receive several notifications in this case?
Another option is to send you notification about client data changes, since you must already have client_id in your booking details - you could just refetch that client data
Yes we’re currently setting up a consolidation on the CRM to combine multiple identical customer profiles into one. So an update coming from Simplybook for one clientId will affect the “main” object, but that’s something we’d need to handle on our end.
Ideally the webhook as it stands; the “booking created, updated, deleted” case, remains as it is. But another webhook for client updates is added, separate from the existing one.
This would make sure that when a client with 100 bookings is changed, it doesn’t fire an update for 100 bookings, but rather 1 webhook “client changed”. (in our case it would almost always be 1 client 1 booking since we don’t use client login)
So yes, the later option you present is ideal in this/our scenario, and I think for other SB users, using or not using client login, this is the most relevant setup for them too.
Hi,
Unfortunately I can’t give any release date for this feature at the moment. We have some developments that are a higher priority at the moment. I’ll come back and let you know when I have more information.
I see the API documentation has been updated; it now mentions the creation of webhooks.
However, I could not find any more documentation related to this.
Can we add webhooks ourselves now for the update/create of clients etc,..
Is there any more docs available for this new feature?
Like what the event value should be for these types of webhooks (clients, services, add-ons,..)
Good news — this is now available. You can subscribe to webhooks for client changes independently of bookings, exactly as discussed above: one change_client event per client update, not one per booking on that client.
Manage subscriptions via the REST API:
- GET /admin/webhooks — list your subscriptions
- POST /admin/webhooks — create one (url + event)
- DELETE /admin/webhooks/{id} — remove one
Available event values right now: new_booking, change_booking, cancel_booking, new_client, change_client, delete_client, new_offer, new_invoice.
There isn’t a dedicated event for services or add-ons yet — only the ones listed above. Let us know if that’s something you need and we can look into it as a separate request.
That’s great news, thanks for the update.
The same goes for the new API swagger docs, way better and good to see these changes arrive.
Great to see the signature + proper docs introduced as well.
As for other webhooks, ideally a provider create/update (especially for working hours)
Services/add-ons could be useful too but with the the ones available now, we can get started already.
Again, thanks for the improvements, the new api docs, webhooks and this forum being actively followed up from the SB devs make working with SB as a dev a lot more fun!
