Skip to main content
The opening hours endpoints let you manage when your restaurant accepts reservations. Each record represents one service period on one day of the week — for example, a Saturday lunch service running from 12:00 to 15:00 with 90-minute slots every 30 minutes. All requests require a valid JWT Bearer token. The day_of_week field maps days to integers as follows:

List opening hours

Returns all service periods configured for your restaurant.

Endpoint


Create an opening hours entry

Adds a new service period. You can add multiple services per day — for example, a separate lunch and dinner service on the same day.

Endpoint

Request body

number
required
Day of the week as an integer. 0 = Monday through 6 = Sunday.
string
required
The time when the first reservation slot opens, in HH:MM format (24-hour clock). For example, "12:00".
string
required
The time when the last reservation slot ends, in HH:MM format. For example, "15:00".
number
required
How long each reservation lasts, in minutes. For example, 90 means tables are held for 90 minutes per booking.
number
required
How frequently a new slot starts, in minutes. For example, 30 means slots are offered at :00, :30, and so on within the service window.
string
Optional name for this service period — for example, "Lunch", "Brunch", or "Dinner". Displayed in the booking widget to help guests identify the service.

Update an opening hours entry

Updates one or more fields on an existing service period. Only include the fields you want to change.

Endpoint

string
required
The ID of the opening hours entry to update.

Delete an opening hours entry

Permanently deletes a service period. Returns 204 No Content on success.

Endpoint

string
required
The ID of the opening hours entry to delete.