Manage your services
APIs for Services (opening hours): Create, Update, and Retrieve Time Slots
Last updated
APIs for Services (opening hours): Create, Update, and Retrieve Time Slots
Last updated
ℹ️ If rooms and tables specify the "what," services specify the "when." In OctoTable, a service refers to the designated time slot for a specific offering, such as breakfast, lunch, aperitif, or dinner. Each service has its own availability and booking rules.
⚙️ Use the base resource URL for the following examples, or
GET /services
Retrieves a list of available service for the specified property (e.g., restaurant) using the property ID
Headers
Content-Type
application/json
Authorization
Bearer <token>
Property
<your_property_id>
Response
GET /services/{service_id}
Headers
Content-Type
application/json
Authorization
Bearer <token>
Property
<your_property_id>
Response
POST /services
⚠️ Reserve with Google updates could take up to 24 hours to process.
Headers
Content-Type
application/json
Authorization
Bearer <token>
Property
<your_property_id>
Body
name
string
Name of the seìì
average_stay
int
Average meal duration in minutes.This is important because the table becomes available again when the set time expires. For example, if you select 60, a table booked for 7 pm will be free at 8 pm.
days_of_week
enum [SUN, MON, TUE, WEN, THU, FRI, SAT]
This defines the days of the week in which a service is available for booking. It ensures bookings are only allowed on the specified days.
start_time
date time
Start date time of the calendar
end_time
date time
End time of the calendar
max_advance
int
This setting defines the maximum number of days in advance a customer can make a reservation.
Response
PUT /services/{service_id}
⚠️ Reserve with Google updates could take up to 24 hours to process.
Headers
Content-Type
application/json
Authorization
Bearer <token>
Property
<your_property_id>
Body
name
string
Name of the calendar
average_stay
int
Average meal duration in minutes. This is important because the table becomes available again when the set time expires. For example, if you select 60, a table booked for 7 pm will be free at 8 pm.
days_of_week
enum [SUN, MON, TUE, WEN, THU, FRI, SAT]
This defines the days of the week in which a service is available for booking. It ensures bookings are only allowed on the specified days.
start_time
date time
Start date time of the calendar
end_time
date time
End time of the calendar
max_advance
int
This setting defines the maximum number of days in advance a customer can make a reservation.
Response
DELETE /services/{service_id}
Headers
Content-Type
application/json
Authorization
Bearer <token>
Property
<your_property_id>
Response
📕 ADDITIONAL NOTES
Average stay: This refers to the typical duration of a customer's reservation for a particular service, such as a table or event. It is calculated based on past bookings and helps predict how long a reservation will last. For example, if the average stay for dinner is 90 minutes, the system will expect that each reservation will last around 90 minutes, allowing it to manage availability for subsequent bookings. The average stay helps optimize table usage and scheduling.
Example: If a table has an average stay of 90 minutes and a reservation is made for 7:00 PM, the table will be blocked from 7:00 PM to 8:30 PM. However, it will also be unavailable for any booking starting at 5:45 PM or later because the table is already reserved. However, the table will still be available for reservations starting at 5:30 PM or earlier, as the 90-minute stay won't overlap with the 7:00 PM booking.
Slot times: Slot times define the available time intervals for reservations, which must fall within the designated start and end times for a service. For example, if the service is available from 6:00 PM to 10:00 PM, reservation slots can only be set within that window.
The restaurant can customize the slot intervals to be every 15, 30, or 45 minutes, depending on its needs. Additionally, the user has the flexibility to delete any time slots they do not want, allowing them to adjust availability as needed. Example: If a restaurant is offering dinner from 6:00 PM to 10:00 PM with 30-minute slots, it might initially create time slots from 6:00 PM to 10:00 PM in 30-minute increments (6:00, 6:30, 7:00, etc.). However, if the restaurant decides not to take any reservations at 9:30 PM, they can delete that slot, and the system will only allow reservations up to 9:00 PM Advance_max: Specifies the maximum number of days in advance a customer can book a reservation for a specific service. This setting helps control how far ahead customers can plan their bookings, ensuring that reservations are not made too far in advance.
Retrieves details of a specific calendar for the given property using the calendar ID
Creates a new service entry for the specified property using the provided availability details
Updates the details of a specified calendar entry using the provided availability details
Deletes an existing service entry from the specified property using the calendar ID
For example, if advance_max is set to 30 days, a customer can only book a reservation up to 30 days ahead of the current date. So, if today is January 1st, the customer can make a reservation for any date from January 1st to January 31st, but they will not be able to book for February 1st or later until the 30-day window resets. Show_rooms: this parameter determines whether the final customer can choose the room. If set to "true", the customer will be able to select their preferred room from the available options for dining. Example:
