API changelog β April 29, 2025
Service Booking
API Endpoint: v1/bookings
Scenario: This API is used to create service bookings.
API method: POST
Earlier behavior: Bookings cannot be made to future time slots beyond a given date.
New behavior: With additional parameters, future time slots can be retrieved for bookings.
Service Booking
API Endpoint: {api_url}/v1/bookings/{booking_id}/slots
Scenario: This API is used to get time slots.
API method: GET
Earlier behavior: It gets old time slots mention in the date parameter.
New behavior: It gets future time slots based on days mentioned in future_slot_days.
Service Booking
API Endpoint: {api_url}/v1/bookings/{booking_id}/slots/reserve
Scenario: This API is used to reserve a time slot for a booking.
API method: POST
Earlier behavior: The old API allowed reserving time slots for the date provided in the date field.
New behavior: The new version allows you to reserve time slots for all future dates.
Products
API Endpoint: {api_url}/v2/products/product_center_associations
Scenario: This API enables bulk association of multiple products to centers in a single request.
API method: PUT
Earlier behavior: New API. No earlier behaviour.
New behavior: This API enables bulk association of multiple products to centers in a single request.
Marketing Webhook
API Endpoint: Guest.OptedIn
Scenario: When a guest opts in to receive communications (transactional or marketing) via SMS, Email, or WhatsApp, a Guest.OptedIn event will be triggered.
Earlier behavior: New webhook. No earlier behaviour.
New behavior: This webhook delivers a payload containing the guest's updated communication preferences.
Marketing Webhook
API Endpoint: Guest.OptedOut
Scenario: When a guest opts out of receiving communications (transactional or marketing) via SMS, Email, or WhatsApp, a Guest.OptedOut event will be triggered.
Earlier behavior: New webhook. No earlier behaviour.
New behavior: This webhook delivers a payload containing the guest's updated communication preferences.