With the Wix Bookings V2 API you can manage bookings for a site's services. The booking object holds information about the customer and the session or schedule they have booked. You can then use the eCommerce APIs (coming soon) to handle the checkout and payment flow.

The Wix Bookings V2 API allows your app to:

• Create new bookings (coming soon)
• Retrieve existing bookings
• Manage the booking's life cycle

You can read more about:

• The Wix Bookings service catalog
• Using the Wix Bookings waitlist
• Customer payments using Wix Pricing Plans

• Booking: Information about the service that the customer has booked. Includes details about the time, location, participants, and payment.
• Booking Status: Information about the booking's life cycle.
  • CREATED: The booking has been created, but doesn't yet appear in the business calendar. You need to create a booking before you can start the checkout flow in eCommerce (coming soon).
  • CONFIRMED: The site owner has confirmed the booking and it appears in the business calendar.
    • You can manually confirm a booking via the API.
    • Bookings are automatically confirmed when the service is configured to do so and the eCommerce order (coming soon) has been approved. An automatic confirmation includes checking the slot's or schedule's availability.
  • PENDING: The booking is waiting to be confirmed or declined by the owner and is displayed in the business calendar. You can't manually set bookings as PENDING via an API. Bookings are automatically set as PENDING when an eCommerce order related to the booking has been created (coming soon).
  • WAITING_LIST: The booking is pending on a waiting list. You must use the Waitlist APIs to create bookings in status WAITING_LIST. You can't change a booking's status from CREATED to WAITING_LIST with the Bookings V2 APIs.
  • DECLINED: The booking has been declined by the site owner.
    • You can manually decline a booking with the Decline Booking endpoint.
    • Bookings are automatically declined when an eCommerce order has been declined or a double booking happened for free bookings.
  • CANCELED: The booking has been canceled by the site owner or the customer. You can cancel bookings with the API.
• Double booked: A double booking can happen in case of 2 or more simultaneous eCommerce checkout processes or if the site owner manually accepts bookings that exceed the service's capacity limit.
  • When a double booking happens for paying customers, the doubleBooked boolean is set to true for the second booking and the owner is notified. They must then manually resolve the situation.
  • When a double booking happens for free services, the second booking's status is set to DECLINED while the first booking is retained.
• Service: Business offering. For example, a fitness studio may offer a 1-hour yoga class, a 45 minute HIIT training session, and a 30 minute 1-on-1 personal training. Learn more about services.
• Variant: Unique variation of the service. Each service variant may have a different price. Read more about service variants.
• Availability: Free time on a schedule that customers can book. You can read more about Query Availability. The Create Booking (coming soon) and Reschedule Booking endpoints check if a slot or schedule is available, unless you pass skipAvailabilityValidation in the body of the request. Confirm Booking doesn't check availability. Instead, the availability is checked during the eCommerce payment flow (coming soon).
• Schedule: Entity that holds availability information. A schedule can either belong to a resource (for example, a staff member) or a service. When creating a booking (coming soon) for a course, you need to pass the service's schedule in the body of the request.
• Session: An occupied period of time on a schedule. When creating a booking (coming soon) for a class you need to pass the service's relevant existing session as slot in the body of the request.
• Slot: An available period of time in a schedule that can be booked by a customer. When creating a booking (coming soon) for an appointment you need to pass the relevant slot in the body of the request.
• Deposit: Amount the customer must pay immediately when checking out the booking.
• Visitor: Anyone who isn't registered as a member or hasn't logged in to the Wix site. If a visitor creates a booking they're added as a contact.
• Member: Someone who is a registered member in the Wix site and has a login.
• Wix Pricing Plans: A pre-paid bundle of services or a membership that provides access to certain services.

• The participantNotification field holds only information about the last message sent to the customer. It also doesn't include details which type of message has been sent.
• You must use the Waitlist APIs to create bookings in status WAITING_LIST. You can't change a booking's status from CREATED to WAITING_LIST with the Bookings V2 APIs.

With Bookings Confirmation service, you can ensure that checkout completion is handled in a way that prevents double bookings.
Once the checkout is complete, call the confirmOrDeclineBooking function to apply it to the booking.
Typically, the booking status will be updated to CONFIRMED, and you'll see it on the calendar.
However, in some cases, such as when over-booking could occur, the booking may be declined.
For more information about the ConfirmOrDeclineBooking endpoint, please refer to its documentation.

• Booking: Information about the service that the customer has booked. Includes details about the time, location, participants, and price.
  • Service: Online or in-person business offerings, such as courses and private sessions. For example, a fitness studio may offer a 1-hour yoga class, a 45 minute HIIT training session, and a 30 minute 1-on-1 personal training. Bookings offers 3 types of services:
    • Appointments: Appointments take place whenever a customer books a specific time slot. For example, your hair salon may be open for business from 9:00 AM to 7:00 PM and a customer can book a session at any available time during the day.
    • Classes: Classes can be scheduled on different days, at different times, with different resources, such as staff members. Customers can sign up for single sessions or a class's recurring sessions. For example, a language school offers a beginner's Spanish class every Monday at 8:00 PM. Clients can join the session they want and don't have to commit to attending all sessions.
    • Courses: A limited number of sessions for the same service that starts and ends on a particular day. Customers sign up for the entire course and not one session. For example, a 12-session introductory course to Pilates, starting on February 1st and ending on March 17th.
• Schedule: A collection of all sessions that belong to the same class, course, appointment, or resource. Schedules also comprise available slots that can still be booked.
  • Session: An occupied period of time in a schedule. Sessions are the building blocks of appointments, classes, and courses. Each of these types of services comprise sessions. The collection of related sessions for a service represent the service's schedule.
  • Slot: An available period of time in a schedule that can be booked by a customer. While this includes existing sessions that are available for booking, it can also represent a period of time that can be booked based on the availability of a resource, such as a barber with appointments of 30 minutes each that are open for booking every weekday between 8:00 - 17:00. These slots are calculated according to the constraints of the schedule.
• Calendar: General overview about the availability and bookings of the business, including its services and resources. Manage your appointments, classes and courses on the calendar.
• Resource: Business asset like a staff member, room, or equipment that's needed to provide a service.
• Availability: Free time on a schedule that customers can book. You can read more about Query Availability. The Create Booking and Reschedule Booking endpoints check if a slot or schedule is available, unless you pass skipAvailabilityValidation in the body of the request. Confirm Booking doesn't check availability. Instead, the availability is checked during the ecom payment flow(coming soon) and with Confirm or Decline Booking.
• Double Bookings: Double bookings occur if the total number of bookings for a period of time is greater than the number of spots or resources for the same period of time. Regarding sessions or a schedule, when it does not have enough capacity to accommodate the booking's participants, and for appointments bookings when the same staff member and service overlap.

The following flow presents how Confirm Or Decline Booking determines the booking status.

Calling a checkout after creating a booking, is optional, Confirm or Decline Booking can be called after Create Booking

• Whether the availability check is required If skipAvailability is true, it will skip the check and it will never be a doubleBooking.
• Whether the booking is paid for.If the payment status is PAID or PARTIALLY_PAID, the booking is confirmed regardless of the doubleBooking parameter.
• Wether the booking requires business confirmation. Instead of CONFIRMED the status is set to PENDING. This happens since it needs to always be manually approved by the owner. You can bypass the confirmation check by setting the skipBusinessConfirmation property to true when creating a booking.