Group Booking [BETA]
Do a Group Booking with Authenticated Checkout
Last updated
Do a Group Booking with Authenticated Checkout
Last updated
Multiple attendees can be booked onto a single to attend the same activity. Such a Group Booking can be done using very similarly to booking for a single attendee.
Customer: The person who is paying for the booking. This is the person who is contacted about changes to the booking (e.g. cancellation) and receives confirmation email
Attendee: A person who will be attending the booked activity. NOTE: Often, the customer will also be an attendee and so their ID will be included twice in the Authenticated Checkout request — once as Customer and once as Attendee.
POST /api/checkout-sessions
customer
MUST be a Customer Account ID. Customer object is not allowed for Group Booking.
There are multiple OrderItem
s. Please include one OrderItem for each Attendee.
Constraints:
Only one activity at a time can be booked. In practice, this means that each OrderItem
must have the same values for orderedItem
and acceptedOffer
.
How this differs from the single-attendee request documented in :
Each OrderItem has a required attendee
field. Like customer
, this accepts an imin Customer Account ID (info on Customer Account management ). As mentioned above, the ID used in customer may, and often will, also be used as one of the attendee
s if the person who is booking the activity is also going to attend it.