Introduction
This documentation details OCTO Cloud'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/
OCTO Cloud implement's the core specification but also provides 10 optional capabilities:
Content
Pricing
Hotel Pickup
Price Adjustments
Multi-booking Cart
Promotions / Offers
Card Payments
Online Check-in
Webhooks
Self-service Mapping
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.
Name | Description |
Reseller | You are the reseller, connecting via the API |
Supplier | The supplier on OCTO Cloud which you are connecting to |
Product | The attraction, activity or tour |
Option | A variant of the product, all products must have at least one option |
Unit | The ticket type, e.g. Adult, Child, Senior etc. |
Booking | A booking made for a specific product and option and one or more unit items |
Unit Item | A line item per unit within the booking |
Voucher | A single barcode that can be used for the whole booking |
Ticket | A barcode that can be used per unit item |
