AI-generated Key Takeaways
-
The
BatchAvailabilityLookup
is crucial for displaying current merchant availability and validating requested appointment slots. -
Successful implementation of
BatchAvailabilityLookup
methods is required for completing page load and slot click milestones by returning accurate, real-time availability. -
If the
BatchAvailabilityLookup
response fails, availability is based on the last feed upload; review the Actions Center dashboard for errors if unexpected slots appear. -
There are specific success rate requirements for both
BatchAvailabilityLookup
page load and slot click responses. -
False availability at slot click is considered an error and can lead to your integration being disabled.
When a BatchAvailabilityLookup
is issued, your Booking Server displays current
merchant availability and verifies that the requested appointment slots are
valid and available.
To complete the BatchAvailabilityLookup
page load and slot click milestone
tasks, you need to successfully build and deliver both methods to let your
integration return accurate, real-time availability.
BatchAvailabilityLookup page load task requirements
- 90% of your last 20
BatchAvailabilityLookup
page load responses have no errors.
BatchAvailabilityLookup slot click task requirements
- 95% of your last 20
BatchAvailabilityLookup
slot click responses have no failures. - 100% of your last 20
BatchAvailabilityLookup
slot click responses have no errors.
BatchAvailabilityLookup basics
The BatchAvailabilityLookup
verifies that only current slots are presented to
users during the reservation flow. It can be called multiple times during the
booking flow lifecycle, such as page load and slot click, to display proper
availability to the user who attempts to book a reservation.
BatchAvailabilityLookup page load
When a user clicks Reserve a Table for your venue in the placesheet, the
BatchAvailabilityLookup
request is called on page load and includes multiple
slots for the list view. The payload contains numerous slots that the
Actions Center considers as available, based on your latest Feed uploads or any
intervening availability RTUs.
The response must include every slot request and the current availability of the slot. This prevents the display of any unavailable slots to the user who makes the reservation.
BatchAvailabilityLookup slot click
When a user finds available slots for booking and clicks a slot, the
BatchAvailabilityLookup
request is called for slot click. In this case, only
the selected slot is sent.
The response must represent the current, actual availability of the slot. If it's booked out before the slot click, return that the slot isn't available.