Open Connectivity for Tours, Activities, and Attractions
OCTO (Open Connectivity for Tours, Activities, and Attractions) is an open standard API specification for the in-destination experiences sector of the travel industry. The standard defines agreed-upon schemas, endpoints, and capabilities commonly needed when connecting platforms, resellers, OTAs, and other technologies in tours, activities, and attractions. OCTO is open source.
Open Connectivity for Tours, Activities, and Attractions publishes 4 APIs on the APIs.io network, including Availability API, Bookings API, Products API, and 1 more. Tagged areas include Activities, Attractions, Open Standard, Tours, and Travel.
Open Connectivity for Tours, Activities, and Attractions’ developer surface includes authentication, documentation, getting-started guide, support, and 5 more developer resources.
Kin Score
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Open Connectivity for Tours, Activities, and Attractions Availability API
The Availability API from Open Connectivity for Tours, Activities, and Attractions — 2 operation(s) for availability.
Open Connectivity for Tours, Activities, and Attractions Bookings API
The Bookings API from Open Connectivity for Tours, Activities, and Attractions — 5 operation(s) for bookings.
Open Connectivity for Tours, Activities, and Attractions Products API
The Products API from Open Connectivity for Tours, Activities, and Attractions — 2 operation(s) for products.
Open Connectivity for Tours, Activities, and Attractions Supplier API
The Supplier API from Open Connectivity for Tours, Activities, and Attractions — 1 operation(s) for supplier.
Pricing Plans 1
Published pricing tiers and plan structures.
Octo Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Octo Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Octo Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help