Stay organized with collections
Save and categorize content based on your preferences.
BatchGetWaitEstimates
This example illustrates a case where a restaurant usually allows party_size values
from 2 to 10 but at the time of the request, party_size values higher than 7 can no
longer be accomodated (close to closing time, for example) and party_size of 2 has
actually no wait.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[[["`BatchGetWaitEstimates` allows merchants to retrieve the current wait times for various party sizes for a specific service, such as reservations."],["The response includes a `waitlist_status` indicating if the waitlist is open and a list of `wait_estimate` objects detailing the estimated wait for each party size, potentially using `parties_ahead_count` or remaining empty for immediate seating."],["Using `CreateWaitlistEntry`, `GetWaitlistEntry`, and `DeleteWaitlistEntry`, users can add themselves to the waitlist, check their status and estimated wait, and remove themselves from the waitlist, respectively."],["Wait estimates can vary based on real-time availability and operational constraints, such as party size limitations near closing time."]]],["The provided content details waitlist management for a restaurant. It begins by checking wait estimates for party sizes 2-10, revealing that parties over 7 cannot be accommodated and party size 2 has no wait. A new waitlist entry is then created for a party of 3, assigning it an ID. Retrieving that ID confirms the party is waiting with 3 parties ahead. Finally the entry is deleted.\n"]]