Table Availability

Checking availability before booking — which slots and tables are free for the required date, time and party size.

Before creating a reservation, check availability — which slots and tables are free on the required date for the given party size. There are two endpoints: the host one (full control) and the guest one (what an online guest sees).

Host availability

GET /api/rsv/admin/restaurants/{restaurantId}/availability

The restaurant’s table availability for a date. Behaviour depends on the AsOnlineGuest parameter:

AsOnlineGuest=true — calculated as for an online guest: limited slots, no occupied tables.
AsOnlineGuest=false — full host availability: closed slots are filtered out and overbooking/events are handled.

Parameters

Parameter	In	Type	Description
`restaurantId` *	path	integer	Restaurant identifier
`Date`	query	date-time	Date (and time) to calculate availability for
`GroupSize`	query	integer	Party size
`RangeInMinutes`	query	integer	Search window around the time, in minutes
`TableTurnOver`	query	number	Expected table turnover time
`ExcludeId`	query	string	Exclude the reservation with this ID (e.g. when editing an existing one)
`Areas`	query	string	Filter by areas/floors
`AllowBusyTables`	query	boolean	Allow showing occupied tables
`DeliveryType`	query	string	Service type (dine-in/delivery/pickup)
`AsOnlineGuest`	query	boolean	Calculate as for an online guest (see above)

Example

curl -G https://api.hostmeapp.com/api/rsv/admin/restaurants/123/availability \
  -H "Authorization: Bearer $TOKEN" \
  --data-urlencode "Date=2026-07-01T19:00:00" \
  --data-urlencode "GroupSize=2" \
  --data-urlencode "RangeInMinutes=120" \
  --data-urlencode "AsOnlineGuest=true"

Response. The endpoint returns the available slots and tables for the date. The exact schema of the successful response (200) is not fixed in the specification — rely on the actual response from your environment. Documented error codes: 400 Bad Request, 404 Not Found (body — ProblemDetails).

Guest availability

GET /api/core/mb/restaurants/{restaurantId}/availability

The guest (“mobile/booking”) variant of availability — what an online guest sees. The parameter set is simpler:

Parameter	In	Type	Description
`restaurantId` *	path	integer	Restaurant identifier
`Date`	query	date-time	Date
`PartySize`	query	integer	Party size
`RangeInMinutes`	query	integer	Search window, in minutes
`Areas`	query	string	Filter by areas
`DeliveryType`	query	string	Service type

Note: here the party size parameter is called PartySize (in the host endpoint it is GroupSize).

Which one to use

Scenario	Endpoint
Booking widget/storefront for a guest	`GET /api/core/mb/.../availability`
Host Panel, full control, overbooking	`GET /api/rsv/admin/.../availability`

Found a slot — create the reservation: Create & Manage.