Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat BatchAvailabilityLookup dikeluarkan, Server Pemesanan Anda akan menampilkan ketersediaan penjual saat ini dan memverifikasi bahwa slot janji temu yang diminta valid dan tersedia.
Untuk menyelesaikan tugas tonggak pencapaian pemuatan halaman dan klik slot BatchAvailabilityLookup, Anda harus berhasil membuat dan mengirimkan kedua metode agar integrasi Anda dapat menampilkan ketersediaan real-time yang akurat.
Persyaratan tugas pemuatan halaman BatchAvailabilityLookup
90% dari 20 respons pemuatan halaman BatchAvailabilityLookup terakhir Anda tidak memiliki
error.
Persyaratan tugas klik slot BatchAvailabilityLookup
95% respons klik slot BatchAvailabilityLookup terakhir Anda tidak mengalami kegagalan.
100% respons klik slot BatchAvailabilityLookup terakhir Anda tidak memiliki
kesalahan.
Dasar-dasar BatchAvailabilityLookup
BatchAvailabilityLookup memverifikasi bahwa hanya slot saat ini yang ditampilkan kepada pengguna selama alur reservasi. Fungsi ini dapat dipanggil beberapa kali selama siklus proses alur pemesanan, seperti pemuatan halaman dan klik slot, untuk menampilkan ketersediaan yang tepat kepada pengguna yang mencoba memesan reservasi.
Pemuatan halaman BatchAvailabilityLookup
Saat pengguna mengklik Pesan Meja untuk tempat Anda di panel informasi hotel, permintaan
BatchAvailabilityLookup dipanggil saat halaman dimuat dan menyertakan beberapa
slot untuk tampilan daftar. Payload berisi banyak slot yang dianggap tersedia oleh Pusat Tindakan berdasarkan upload Feed terbaru Anda atau RTU ketersediaan yang ada di antaranya.
Respons harus menyertakan setiap permintaan slot dan ketersediaan slot saat ini. Tindakan ini mencegah tampilan slot yang tidak tersedia kepada pengguna yang membuat reservasi.
Klik slot BatchAvailabilityLookup
Saat pengguna menemukan slot yang tersedia untuk pemesanan dan mengklik slot, permintaan
BatchAvailabilityLookup akan dipanggil untuk klik slot. Dalam hal ini, hanya slot yang dipilih yang dikirim.
Respons harus menunjukkan ketersediaan slot saat ini dan sebenarnya. Jika
sudah dipesan sebelum klik slot, kembalikan bahwa slot tidak tersedia.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-26 UTC."],[],[],null,["# BatchAvailabilityLookup Ready\n\nWhen a `BatchAvailabilityLookup` is issued, your Booking Server displays current\nmerchant availability and verifies that the requested appointment slots are\nvalid and available.\n\nTo complete the `BatchAvailabilityLookup` page load and slot click milestone\ntasks, you need to successfully build and deliver both methods to let your\nintegration return accurate, real-time availability.\n| **Note:** If the `BatchAvailabilityLookup` response fails for any reason, slots are presented to the user based on your last Availability Feed upload. If unexpected slots appear, review the Booking Server dashboard in the Actions Center for errors.\n\nBatchAvailabilityLookup page load task requirements\n---------------------------------------------------\n\n- 90% of your last 20 `BatchAvailabilityLookup` page load responses have no errors.\n\nBatchAvailabilityLookup slot click task requirements\n----------------------------------------------------\n\n- 95% of your last 20 `BatchAvailabilityLookup` slot click responses have no failures.\n- 100% of your last 20 `BatchAvailabilityLookup` slot click responses have no errors.\n\nBatchAvailabilityLookup basics\n------------------------------\n\nThe `BatchAvailabilityLookup` verifies that only current slots are presented to\nusers during the reservation flow. It can be called multiple times during the\nbooking flow lifecycle, such as page load and slot click, to display proper\navailability to the user who attempts to book a reservation.\n\n### BatchAvailabilityLookup page load\n\nWhen a user clicks **Reserve a Table** for your venue in the placesheet, the\n`BatchAvailabilityLookup` request is called on page load and includes multiple\nslots for the list view. The payload contains numerous slots that the\nActions Center considers as available, based on your latest Feed uploads or any\nintervening availability RTUs.\n\nThe response must include every slot request and the current availability of the\nslot. This prevents the display of any unavailable slots to the user who makes\nthe reservation.\n\n### BatchAvailabilityLookup slot click\n\nWhen a user finds available slots for booking and clicks a slot, the\n`BatchAvailabilityLookup` request is called for slot click. In this case, only\nthe selected slot is sent.\n\nThe response must represent the current, actual availability of the slot. If\nit's booked out before the slot click, return that the slot isn't available.\n| **Warning:** False availability at slot click is considered an error. Your integration can get disabled if there are too many slot click errors. The high error rates for slot click indicate that your page load `BatchAvailabilityLookup` response doesn't reflect real-time inventory accurately."]]
