Skip to main content

Walk-ins

A walk-in is a reservation without a guest. It has guest: null and source: "pos". Use walk-ins for guests who arrive without a reservation, for example when a POS opens a table.

Create a walk-in​

Request​

POST /external/reservations/walk-ins

Parameters​

  • attendees (required): Number of guests, at least 1
  • tableIds (optional): Table IDs. Every ID must belong to a floor plan of the restaurant. When omitted, the API picks the first free table or table combination for attendees.
  • experienceId (optional): Experience of the walk-in. When omitted, the restaurant's default experience is used.
  • status (optional): seated (default) or ordered

The walk-in starts now, rounded down to 15 minutes. Its duration comes from the experience.

Example​

curl -X POST \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"attendees": 2,
"tableIds": ["2f72e7aec901-4427-9ffd-bc4fc435c431"]
}' \
https://api.molzait.com/external/reservations/walk-ins

Response​

201 Created with the reservation:

{
"id": "4a4ccb52c0bc-4be3-96cd-32accbb3e3d0",
"number": "R-001235",
"attendees": 2,
"experience": {
"id": "ad5b78a02ca8-4768-bd80-487130c73856",
"name": {
"en": "Dinner",
"de": "Abendessen"
},
"shorthand": "DIN"
},
"startTime": "2024-01-02T18:45:00Z",
"endTime": "2024-01-02T20:45:00Z",
"checkinTime": "2024-01-02T18:52:00Z",
"checkoutTime": null,
"status": "seated",
"source": "pos",
"restaurantId": "e54ba2b9e5f1-4568-a5e0-5998573e002a",
"guest": null,
"pinnedTables": [
{
"id": "2f72e7aec901-4427-9ffd-bc4fc435c431",
"name": "45",
"minPartySize": 2,
"maxPartySize": 4
}
],
"labels": []
}

Errors​

  • 400: Invalid body, or a table ID does not belong to the restaurant
  • 403: The experience has no slot right now, the restaurant has no default experience, or no table is free when tableIds is omitted
  • 404: The experience does not exist, belongs to another restaurant or is private. A private default experience also returns 404.
  • 409: A seated or ordered reservation of the current service day is on one of the tableIds. Retrying a request that already created the walk-in also returns 409.

Update a walk-in​

Update a walk-in like any other reservation:

PATCH /external/reservations/{reservationId}

All fields are optional:

  • status: The new status, for example paid or finished
  • day and minutes: The new start. Send both together. minutes counts from the start of the service day in the restaurant's timezone. The service day starts at 05:00, so times between 00:00 and 05:00 belong to the previous day and are 1440 or more (1500 = 01:00).
  • attendees: The new party size, at least 1
  • tableIds: The new tables. Every ID must belong to a floor plan of the restaurant, otherwise the API returns 400.

A walk-in keeps its tables when attendees or day/minutes change. A reservation with a guest gets new tables automatically unless you send tableIds. When attendees or day/minutes change, the reservation must fit a slot of its experience, otherwise the API returns 403. A reservation of another restaurant returns 404.

Example​

curl -X PATCH \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"attendees": 4
}' \
https://api.molzait.com/external/reservations/4a4ccb52c0bc-4be3-96cd-32accbb3e3d0

Check in a table​

POST /external/reservations/checkin

Send tableName, tableIds or both. The API uses all tables that match either. If no table matches, it returns 404.

curl -X POST \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tableName": "45"
}' \
https://api.molzait.com/external/reservations/checkin

The API then goes through these steps and stops at the first match:

  1. A booked or reconfirmed reservation on these tables that starts within 15 minutes of now. If there is none, an arrived reservation that starts within 60 minutes of now. The API sets it to ordered and returns it with 200. The restaurant can turn this step off.
  2. A seated or ordered reservation on these tables that started in the current service day. The service day runs from 05:00 to 05:00 the next day. The API returns it unchanged with 200.
  3. Otherwise the API creates a walk-in with status ordered on these tables and returns it with 201. Its party size is the sum of the tables' maximum party sizes. It uses the restaurant's default experience. Without a default experience the API returns 403.

Check out a table​

POST /external/reservations/checkout

Send tableName, tableIds or both, as for check-in.

curl -X POST \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tableName": "45"
}' \
https://api.molzait.com/external/reservations/checkout

The API looks for a seated or ordered reservation on these tables that started in the current service day (05:00 to 05:00 the next day):

  • It sets the reservation to paid and returns it with 200. About 10 minutes later the reservation is set to finished automatically.
  • A walk-in that was checked in less than 10 minutes ago is set to voided instead. This removes walk-ins that were only opened to print a bill.

It returns 404 when no table matches or no such reservation exists.

List walk-ins​

GET /external/reservations leaves walk-ins out by default. Add includeWalkIns=true to include them:

curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.molzait.com/external/reservations?from=2024-01-02&to=2024-01-02&includeWalkIns=true"

Next steps​