Antylogic
DemoApp login

399 operational guides

Docs sections
DocsOnline booking
Device

Check Public Availability

Explains how a public guest checks optimiser-backed booking times for Harbor Soho after choosing a date, automatic public service, party size and optional table preference, without creating a customer, reservation or table assignment.

In this article

Use this guide when validating the public booking journey from the guest side. The availability check starts on the public booking page and ends on the Time step, where returned slots are shown for the selected automatic service.

This action is read-only. It evaluates current capacity, layout resources and existing bookings, but the slot is not held until the separate reservation creation step succeeds.

Before you start

  • Public booking is enabled for the location and the location is visible to public guests.
  • The location plan includes `reservation-automatic:use`.
  • The guest opens `/:orgId/:locationId/booking` or `/:orgId/:locationId/reservar` for the correct organisation and location.
  • A public automatic service occurrence, such as Harbor Soho's `Soho lunch service`, is available for the selected date and has a layout and optimisation configuration.
  • The guest enters a party size greater than zero before availability is checked.
  • If table preferences are documented, public table preferences are enabled and the service layout provides selectable zones, tables or table types.

Instructions

  1. 1.

    Open the Public Booking Page

    The guest opens Harbor Soho's public booking URL. Antylogic loads the public profile, bookable days and available services for the organisation and location in the URL. No staff login is required.

  2. 2.

    Choose Date and Service

    The guest chooses a bookable date and a public service. Manual services may be listed for public handling, but this availability check only continues for automatic services that are public, open, current and tied to the location.

  3. 3.

    Enter Party Size

    The guest enters the number of people. Blank, invalid or non-positive input is treated as `0`, so the Time step cannot request availability until a positive `party_size` and selected `occurrence_id` are present.

  4. 4.

    Select an Optional Preference

    When preferences are enabled, the guest can continue with no preference, choose a zone, or choose a table type. A zone becomes preferred table IDs, while a table type is sent as a soft preference with `table_type_mode: "preferred"`.

  5. 5.

    Check Available Times

    On the Time step, Antylogic posts the occurrence, party size and valid preference fields to `POST /api/public/{orgId}/{locationId}/booking/availability`. The optimiser evaluates the service setup, layout resources, current non-cancelled reservations and table assignments, then returns available slots.

  6. 6.

    Review Returned Slots

    The guest reviews the returned time cards. The best scored returned slot can be marked `Preferred`, a returned slot can be selected, and split-table eligibility may show a required departure-time callout. If no slots are returned, the page moves toward the waitlist path instead of selecting a booked slot.

Validations and limits

  • The public profile is hidden when public booking is disabled, billing is blocked, the location is deleted, the URL organisation does not match the location, or the automatic reservation plan feature is unavailable.
  • The availability endpoint only accepts `POST`; invalid JSON returns `payload invalido`.
  • `occurrence_id` is required and `party_size` must be greater than zero.
  • Internal services, manual booking modes, waitlist booking modes, wrong-location occurrences, completed occurrences and past local-day occurrences cannot use this availability action.
  • If `public_booking_table_preferences_enabled` is false, the Preferences step is removed and the backend clears preference fields even if sent directly.
  • The current public booking page does not send `duration_minutes` in the availability payload; duration is sent later during reservation creation.
  • The GB demo runtime currently marks Harbor Soho public booking as disabled, so captures require documentation-runtime setup before recording.

Expected result

The guest sees optimiser-backed public booking time slots for the selected automatic service. No customer, reservation or table assignment is created by this action.