# Sandbox Bookings API accepts concurrent overlapping buyer-level bookings

**URL:** <https://developer.squareup.com/forums/t/sandbox-bookings-api-accepts-concurrent-overlapping-buyer-level-bookings/28394>\
**Category:** Questions\
**Created:** [October 29, 2026, 10:12pm UTC](https://developer.squareup.com/forums/t/sandbox-bookings-api-accepts-concurrent-overlapping-buyer-level-bookings/28394 "2026-10-29T22:12:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nataliya](https://avatars.discourse-cdn.com/v4/letter/n/54ee81/32.png) [@Nataliya](https://developer.squareup.com/forums/u/Nataliya)\
**Post date:** [October 29, 2026, 10:12pm UTC](https://developer.squareup.com/forums/t/sandbox-bookings-api-accepts-concurrent-overlapping-buyer-level-bookings/28394/1 "2026-10-29T22:12:51Z")

</div>

Hi Square team,

While testing a booking integration in Sandbox, two concurrent CreateBooking requests were both accepted for the same staff member, location and 45-minute service:

- October 30, 2026, 10:00–10:45 AM

- October 30, 2026, 10:30–11:15 AM

- Timezone: America/Edmonton

Both returned HTTP 201 with ACCEPTED status. Subsequent GET requests confirmed both bookings remain ACCEPTED. We also checked the Sandbox Dashboard: both appointments are visible for the same staff member, overlapping by 15 minutes.

The requests used different test customers and idempotency keys. Token introspection confirmed APPOINTMENTS\_WRITE and APPOINTMENTS\_READ, without APPOINTMENTS\_ALL\_WRITE or APPOINTMENTS\_ALL\_READ.

API version: 2026-09-16.

As a control, two concurrent requests with identical start times resulted in one accepted booking and one rejection: “That time slot is no longer available.”

Is the partial-overlap result a Sandbox limitation, a configuration issue, or unexpected concurrency behavior? Does buyer-level CreateBooking check the full appointment interval atomically for conflicts?

We have only tested this in Sandbox and are not claiming the same behavior occurs in Production. We can provide a detailed report and booking/request IDs privately if needed.

Thank you.

---

<div class="post-metadata">

**Author:** ![zacstlouis](https://avatars.discourse-cdn.com/v4/letter/z/b5a626/32.png) [@zacstlouis](https://developer.squareup.com/forums/u/zacstlouis)\
**Post date:** [October 29, 2026, 11:24pm UTC](https://developer.squareup.com/forums/t/sandbox-bookings-api-accepts-concurrent-overlapping-buyer-level-bookings/28394/3 "2026-10-29T23:24:06Z")

</div>

I recommend following the [documented availability-search and booking-creation workflow](https://developer.squareup.com/docs/bookings-api/use-the-api#search-for-available-slots). You could implement your own app-level lock for resources/staffing but you can’t guarantee you are the only booking system connected to the Square account.

If this becomes a real issue in a production/live environment please feel free to respond back here.
