Go Headless

Build Apps

Client

API Preview

Develop Websites

REST

Velo

GraphQL (Alpha)

## Standard booking flow

The primary customer-facing flow in Wix Bookings is the single-service bookings flow. The following diagram describes this flow:

![Standard flow diagram](https://wixmp-833713b177cebf373f611808.wixmp.com/images/single-service-booking-flow-md_build-apps-portal_develop-your-app_business-solutions_wix-bookings_assets_standardbookingflowdiagram.png)



1. When the customer views the site’s list of services, the client calls [Query Services](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/query-services) and displays all available services.
1. When the customer selects a specific service to view, the client:
    1. Calls [Get Service](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/get-service) (optional). 
    1. Checks availability:
     - For appointments and classes: Calls [Query Availability](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/time-slots/availability-calendar/query-availability). 
     - For courses: Checks the requested number of participants against the capacity (`defaultCapacity` in the [Query Services](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/query-services) or [Get Service](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/get-service) response).
    1. Displays details of the specific service and available time slots.
1. When the customer selects a time slot to book, the client displays a booking form, based on the [Query Services](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/query-services) (or [Get Service](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/services/services-v2/get-service)) response.
1. Customer fills out the booking form.
1. When the customer clicks “book now”:
    1. The client calls [Query Availability](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/time-slots/availability-calendar/query-availability) again to validate that the time slot is still available. 
    1. Then the client calls [Create Booking](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/bookings-create-booking) to create a booking for the customer. 
    1. If a site contributor configured manual approval for this service, they will receive a notification requesting review and approval (limited to free or offline payments).
1. If online payment is required: the client leads the customer to the eCom checkout flow. 
If a [Pricing integration](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::1f53cf8d-5984-4c90-8158-a824e27e9921slug::calculate-price*fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/pricing/pricing-integration-spi/calculate-price) is implemented, Wix calls the implementor to calculate the price to charge.
1. If the session is free or takes offline payments: the client skips checkout entirely.
1. When the customer has completed the eCom checkout flow (or when the session is free or the customer is paying offline), an [Order Approved](fallback::https://dev.wix.com/docs/rest/business-solutions/e-commerce/orders/order-approved) webhook is triggered.
1. Once the order is approved, Wix Bookings calls [Confirm Or Decline Booking](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/mark-booking-as-pending) which triggers the following logic:
    1. If [manual confirmation](fallback::https://support.wix.com/en/article/wix-bookings-requiring-approval-for-appointment-bookings) is enabled, Wix Bookings calls the internal Mark Booking as Pending endpoint to mark the booking as pending, and sends a notification to the site contributors to manually confirm the booking. When a site contributor confirms the booking, Wix Bookings calls the internal Confirm Booking endpoint to mark the booking as confirmed.
    1. If this booking causes an overbooking:
       - If payment was made: Wix Bookings calls the internal Confirm Booking endpoint and a notification about the overbooking will be sent to the site contributors.
       - If no payment was made: Wix Bookings calls [Decline Booking](fallback::https://dev.wix.com/docs/rest/business-solutions/bookings/bookings-and-time-slots/bookings-v2/bookings-v2-and-confirmation/decline-booking). 
    1. In all other cases, Wix Bookings calls the internal Confirm Booking endpoint to mark the booking as confirmed. 

Once the booking is confirmed:
- A session is added to the business’s booking calendar, and to the schedules of any affected staff and resources.
- Any notifications that have been set up are triggered.
- Any automations set to be triggered by a session being booked are triggered, and any automations set to be triggered around a session start and session end are scheduled.
- The customer can view and manage their booking (cancel, reschedule, etc.) in the site’s [members area](fallback::https://support.wix.com/en/article/site-members-about-the-members-area).
- The site contributors can [view and manage bookings](fallback::https://support.wix.com/en/article/wix-bookings-managing-your-business-with-the-booking-activity-panel) in the site dashboard’s booking calendar.