<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>thread Re: CreateBooking accepts bookings when team member and resources are unavailable in Appointments &amp; Bookings</title>
    <link>https://community.squareup.com/t5/Appointments-Bookings/CreateBooking-accepts-bookings-when-team-member-and-resources/m-p/850554#M6927</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 06 Oct 2026 12:13:24 GMT</pubDate>
    <dc:creator>henrykeil</dc:creator>
    <dc:date>2026-10-06T12:13:24Z</dc:date>
    <item>
      <title>CreateBooking accepts bookings when team member and resources are unavailable</title>
      <link>https://community.squareup.com/t5/Appointments-Bookings/CreateBooking-accepts-bookings-when-team-member-and-resources/m-p/850553#M6926</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We're building a custom booking website using the Bookings API with seller-level permissions (Appointments Premium, Japan, Sandbox).&lt;/P&gt;&lt;P&gt;In our tests:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;SearchAvailability correctly hides a time slot when all 3 resources (rooms) are booked, including the 15-minute blocked time after each appointment.&lt;/LI&gt;&lt;LI&gt;But CreateBooking still &lt;STRONG&gt;accepts&lt;/STRONG&gt; a booking at that same time. The booking is created with &lt;STRONG&gt;no resource assigned&lt;/STRONG&gt;.&lt;/LI&gt;&lt;LI&gt;CreateBooking also accepts a booking for a team member who is &lt;STRONG&gt;already booked&lt;/STRONG&gt; at that time, creating a double booking.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is this expected behaviour for seller-level CreateBooking?&lt;/LI&gt;&lt;LI&gt;Does CreateBooking with &lt;STRONG&gt;buyer-level&lt;/STRONG&gt; permissions (APPOINTMENTS_WRITE only) reject bookings when the team member or resource is unavailable?&lt;/LI&gt;&lt;LI&gt;What do you recommend to prevent double bookings when bookings come from both the API and the Dashboard?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2026 10:57:13 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Appointments-Bookings/CreateBooking-accepts-bookings-when-team-member-and-resources/m-p/850553#M6926</guid>
      <dc:creator>TusharDev</dc:creator>
      <dc:date>2026-10-06T10:57:13Z</dc:date>
    </item>
    <item>
      <title>Re: CreateBooking accepts bookings when team member and resources are unavailable</title>
      <link>https://community.squareup.com/t5/Appointments-Bookings/CreateBooking-accepts-bookings-when-team-member-and-resources/m-p/850554#M6927</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2026 12:13:24 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Appointments-Bookings/CreateBooking-accepts-bookings-when-team-member-and-resources/m-p/850554#M6927</guid>
      <dc:creator>henrykeil</dc:creator>
      <dc:date>2026-10-06T12:13:24Z</dc:date>
    </item>
  </channel>
</rss>

