CreateBooking accepts bookings when team member and resources are unavailable

[TusharDev]

Hi,

We're building a custom booking website using the Bookings API with seller-level permissions (Appointments Premium, Japan, Sandbox).

In our tests:

1. SearchAvailability correctly hides a time slot when all 3 resources (rooms) are booked, including the 15-minute blocked time after each appointment.
2. But CreateBooking still accepts a booking at that same time. The booking is created with no resource assigned.
3. CreateBooking also accepts a booking for a team member who is already booked at that time, creating a double booking.

Questions:

1. Is this expected behaviour for seller-level CreateBooking?
2. Does CreateBooking with buyer-level permissions (APPOINTMENTS_WRITE only) reject bookings when the team member or resource is unavailable?
3. What do you recommend to prevent double bookings when bookings come from both the API and the Dashboard?

Thanks!

[henrykeil]

I’d treat CreateBooking as a separate validation step rather than relying only on SearchAvailability. It would be worth checking whether the API is expected to enforce resource and team-member conflicts itself. For mixed API and Dashboard bookings, I’d also add a final availability check before creating the booking.