Base path
All OTA endpoints are under:List products
Retrieve all activities that are available in the operator’s shopfront.Query parameters
Example request
Response
Returns a200 response with a list of products.
Resolve a product
Look up a specific product by its ID or name.Query parameters
Provide either
ID or Name, not both.
Example request
Responses
Get available dates
Retrieve dates with available capacity for a specific activity within a date range.Path parameters
Query parameters
Example request
Responses
Get available timeslots
Retrieve timeslots with availability for a specific activity on a given date.Path parameters
Query parameters
Example request
Responses
Get waiver questions
Retrieve the waiver questions associated with an activity. Use this to display required forms to customers before they complete a booking. Questions can be marked as required — your integration should validate that all required fields (including file uploads) are completed before submitting the booking.Responses
Get waiver questions
Retrieve the waiver questions associated with an activity. Use this to display required forms to customers before they complete a booking.Path parameters
Example request
Responses
Create a booking
Submit a new booking for an activity.Example request
Responses
Bookings created through the OTA API are recorded with the OTA partner’s payment reference. The operator sees these bookings in their bookings dashboard alongside online and POS bookings.
Typical integration flow
A standard OTA integration follows these steps:1
Discover products
Call list products to retrieve the operator’s activities. Cache results and refresh periodically.
2
Check availability
When a customer selects an activity, call get available dates to show bookable dates, then get available timeslots for the chosen date.
3
Collect waiver responses
Call get waiver questions and display the required fields to the customer before checkout.
4
Create the booking
Submit the reservation with create a booking. Handle a
409 response by prompting the customer to choose a different timeslot.Error handling
All error responses follow the RFC 7807 problem detail format. See error format for details.Related guides
API introduction
Authentication, base URL, and error format.
Adventuro integration
Pre-built OTA integration with Adventuro marketplace.