Welcome to the official OCTO API Developer Hub!

This portal describes the OCTO specification and provides additional resources and recommendations for developers implementing OCTO API to accept and provide data following this standard.

You may also directly access OCTO OpenAPI Specification referenced throughout this documentation as well as OCTO GitHub for additional dev resources.


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 API is already adopted by a number of industry players. Check out known implementations summarized by our member volunteers.

The OCTO API Specification is Opensource and available to anyone who wants to use it. You do not need to be a member to use this specification in your business. If, however, you would like to support OCTO and have a voice in how the specification evolves, please consider becoming a member.

OCTO is developed and administered by a member-based not-for-profit organization OCTO Standards NP Inc. To learn more about OCTO and join the initiative as a member to contribute to the specification development, please visit https://www.octo.travel/.

What's New

April 22, 2024

  • Replaced Webhooks capability proposed draft with the Notifications capability placeholder, based on Specification Committee review.

  • Added placeholders for Content and Pickups capabilities that are next in the development queue.

February 3, 2024

July 28, 2023

  • The official specification OCTO OpenAPI Specification has been updated to correct typos and all the latest changes in line with the 1.0 specification.

  • https://docs.octo.travel has been migrated to GitBook to provide additional tools for users.

  • Additional information was added to explain the concept of OCTO API Core Endpoints and additional capabilities to be added to the specification.

  • Corrected Booking Cancellation to POST /bookings/{uuid}/cancel instead of DELETE /bookings/{uuid} as per OpenAPI 3.0.

Last updated