This documentation details Ventrata's implementation of the OCTo API Specification which is an open API standard initiative for the experiences industry. More information about the OCTo specification and who's part of it can be read here: https://octospec.com/
Ventrata implement's the core specification but also provides 10 optional capabilities:
Promotions / Offers
OCTo defines core terms that are re-used throughout the specification. A full description of those terms can be found on OCTo Spec Website but we have included a table below to get started.
You are the reseller, connecting via the API
The supplier on Ventrata which you are connecting to
The attraction, activity or tour
A variant of the product, all products must have at least one option
The ticket type, e.g. Adult, Child, Senior etc.
A booking made for a specific product and option and one or more unit items
A line item per unit within the booking
A single barcode that can be used for the whole booking
A barcode that can be used per unit item