Sandbox Bookings API accepts concurrent overlapping buyer-level bookings

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.

I recommend following the documented availability-search and booking-creation workflow. 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.