Waitlist

The waitlist (walk-in / waitlist) is the queue of guests who arrived without a reservation. The host adds the guest to the queue, the system estimates the wait time, and when a table is ready the guest is called and seated. This section covers both sides of the process:

• Restaurant side (tag WaitingAdmin, path /api/wm/admin/restaurant/{restaurantId}/waitings) — adding to the queue, listing, changing status, calling and seating the guest, messaging with them.
• Guest side (tag WaitingGuest, path /api/rsv/mb/guest/walkins) — the guest joins the queue on their own, tracks their position in line and the time estimates.

All endpoints require a Bearer token (see Authentication). Times are ISO 8601 in the restaurant’s local time zone. Errors are ProblemDetails (see Errors).

Waitlist entry (key fields)

A queue entry is described by the WaitingContract contract (in responses) and UpdateWaitingItemContract (when creating/updating). Below are the fields needed in most integrations.

Nested objects

Adding a guest to the queue

Add an entry (restaurant side)

POST /waitings

Creates a waitlist entry on behalf of staff. Body — UpdateWaitingItemContract.

The most commonly used body fields: customerName, phone, groupSize, areas, expectedTimeMinutes (wait in minutes), estimatedTurnOverTime, specialRequests, internalNotes, email, tableNumber, waiterIds[], autoSeat, additionals, customerProfile.

curl -X POST https://api.hostmeapp.com/api/wm/admin/restaurant/123/waitings \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "customerName": "John Parker",
    "phone": "+16175550123",
    "groupSize": 2,
    "areas": "Terrace",
    "specialRequests": "Window table"
  }'

Guest joins the queue themselves

POST /api/rsv/mb/guest/walkins

Guest endpoint: the guest adds themselves to the queue (for example, via a widget or a kiosk). Body — CreateMobileWalkinContract.

curl -X POST https://api.hostmeapp.com/api/rsv/mb/guest/walkins \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "restaurantId": 123,
    "groupSize": 3,
    "customerName": "Maria Ivanova",
    "phone": "+16175550100",
    "expectedTime": 30
  }'

Response. Returns the created booking entry as a BookingContract.

Listing and reading entries

List entries for a period

GET /waitings

Returns all waitlist entries of the restaurant for a period.

Response — an array of WaitingContract.

curl -G https://api.hostmeapp.com/api/wm/admin/restaurant/123/waitings \
  -H "Authorization: Bearer $TOKEN" \
  --data-urlencode "from=2026-07-01T00:00:00" \
  --data-urlencode "to=2026-07-01T23:59:59"

Compact list

GET /waitings/compact

A lightweight list of entries (BookingCompactContract) — handy for a display board or dashboard: contains id, customerName, phone, groupSize, areas, status, state, tableNumber, expectedTime, estimatedTurnOver, unreadMessageCount and more, without the full order tree.

Get an entry by ID

GET /waitings/{waitingItemId}

Returns an entry by identifier. Response — WaitingContract.

Updating and deleting an entry

Update an entry

PUT /waitings/{waitingItemId}

Updates a queue entry (name, phone, party size, area, wait, etc.). Body — the same fields as on creation (UpdateWaitingItemContract): send the fields you are changing.

curl -X PUT https://api.hostmeapp.com/api/wm/admin/restaurant/123/waitings/ABC_ID \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "groupSize": 4, "areas": "Main Hall", "expectedTimeMinutes": 25 }'

Guest removes themselves from the queue

DELETE /api/rsv/mb/guest/walkins/{walkinId}

Guest endpoint: the guest removes their own entry from the queue.

Changing entry status

The entry lifecycle is driven by separate PUT endpoints. All of them take restaurantId (path, integer) and waitingItemId (path, string).

Seat a guest

PUT /waitings/{waitingItemId}/sited

When the guest gets a table, the host marks the entry as seated. Body — SeatBookingContract:

Response — the updated entry (BookingContract).

curl -X PUT https://api.hostmeapp.com/api/wm/admin/restaurant/123/waitings/ABC_ID/sited \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "tableNumber": "12", "waiterIds": [42] }'

Cancel an entry

PUT /waitings/{waitingItemId}/cancel

Calling a guest

Call a guest

PUT /waitings/{waitingItemId}/call

When a table is ready, the host initiates the call. The guest receives a notification that the table is ready.

curl -X PUT "https://api.hostmeapp.com/api/wm/admin/restaurant/123/waitings/ABC_ID/call?tableNumber=12" \
  -H "Authorization: Bearer $TOKEN"

Messaging with the guest

The host and the guest can exchange messages (for example, about the wait or the table being ready).

Messages for an entry

GET /waitings/{waitingItemId}/messages

Returns an array of MessageContract: id, body, time, origin (host/client), phone, deliveryStatus, deliveryTime, isRead.

Send a message to the guest

POST /waitings/{waitingItemId}/sendmessage

Body — CreateMessageContract (body — the message text).

curl -X POST "https://api.hostmeapp.com/api/wm/admin/restaurant/123/waitings/ABC_ID/sendmessage?origin=host" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "body": "Your table will be ready in 5 minutes" }'

Unread messages

GET /waitings/messages/unread/count

Response — CountContract: the overall count and countItems[] (entry id + count of unread messages per entry).

Wait time estimate (ETA) and statistics

Queue statistics (restaurant side)

GET /waitings/stats

Returns a queue summary and the average wait time estimate. Response — WalkinStatistic:

Estimate for the guest

GET /api/rsv/mb/guest/restaurants/{restaurantId}/walkins/expected

Guest endpoint: the expected wait time estimate by party size. Response — ExpectedTimeContract (expectedMinutesForSizes — a “party size → minutes” map).

Waitlist settings

GET / PUT /waitings/.../settings

Read and update the queue module settings. Path: /api/wm/admin/restaurant/{restaurantId}/settings. Body/response — WaitingSettingsContract:

curl -G https://api.hostmeapp.com/api/wm/admin/restaurant/123/settings \
  -H "Authorization: Bearer $TOKEN"

Guest side: tracking the queue

Guest endpoints (/api/rsv/mb/guest/walkins) let the guest track their place in the queue and manage their entry.

Walk-in status (guest)

GET /api/rsv/mb/guest/walkins/{walkinId}

Returns the guest’s entry (WalkinGuestContract) with the fields customerName, phone, groupSize, areas, status, tableNumber, expectedTime, estimatedTurnOverTime, restaurantName, restaurantImage, timeZone, plus the guest profile and flags.

Position in line

GET /api/rsv/mb/guest/restaurants/{restaurantId}/walkins/line

Returns the entry’s current position in the queue (LineStateContract):

curl -G "https://api.hostmeapp.com/api/rsv/mb/guest/restaurants/123/walkins/line" \
  -H "Authorization: Bearer $TOKEN" \
  --data-urlencode "walkinId=ABC_ID" \
  --data-urlencode "groupSize=2"

Walk-in data (guest)

GET /api/rsv/mb/guest/walkins/data

Reference data for the guest interface (GuestWalkinsDataContract): restaurantIds[], statuses[].

Related sections. For guests with a reservation, use Reservations. General request rules and the error format are in Conventions and Errors.