Booking confirmation request

Request endpoint: POST {supplier_url}/booking

A booking confirmation request is sent when a customer places a paid order.

A booking confirmation request contains the following properties:

Request Body schema: application/json

booking_id required	string The ID of the booking to confirm.
required	Array of objects unique An array of items for the booking.
hold_id required	string The ID of the availability hold request made when a customer added the item to cart.
required	object Information about the lead booker.
tuimm_booking_id required	string^MUS[0-9]+?_[0-9]+?$ This property contains Musement booking information. The value consists of two IDs separated by an underscore. The first ID, consisting of `MUS` and numbers, is the order ID to use when contacting Musement Customer Care. The second ID, consisting only of numbers, is the ID for a single item in the order. This ID is used for internal technical checks and is not relevant when contacting Musement Customer Care.

The response to a successful booking confirmation request contains the following properties:

Booking confirmation request accepted

Response Schema: application/json

booking_id required	string The booking ID from the request.
required	Array of Per person (object) or Per group (object) An array of tickets that customers can use for their experience. Tickets can be unique per person in the booking or valid for the entire group.
transaction_id required	string The supplier's own ID for the booking request.

Timing out

During initial registration negotiations, suppliers agree to webhook response time limits. If the supplier's webhook service takes too long to respond to a booking confirmation request, the booking is no longer considered valid. When this happens, PORTA automatically sends a cancellation request. In these situations, suppliers are required to cancel the booking, regardless of the experience's cancellation policy.