# Introduction ### Supplier-Side Integration: OCTO Prioticket fully adopts and enforces the **OCTO (Open Connectivity for Tours & Activities)** specification for supplier-side connectivity. If you are a supplier (inventory holder) looking to connect your system to Prioticket, **OCTO is the supported protocol**. By using the OCTO standard, suppliers expose product data, availability, pricing, and booking endpoints in a format that can be consumed reliably and predictably by the Prioticket platform and its distribution partners. #### Why OCTO? OCTO is an open API specification developed by industry leaders to create a common language between suppliers and resellers. It provides: * **Faster integration timelines** through standardized endpoints and schemas * **Consistent data structures** across systems, reducing miscommunication * **Lower maintenance overhead** by avoiding custom formats * **Built-in interoperability** with current and future OCTO-compliant resellers For suppliers, this means a predictable way of connecting to multiple distributors without reinventing formats or processes. *** ### Compliance and Specification Prioticket’s platform is built to consume standard OCTO Supplier APIs as defined in the official specification. To build a compliant integration, your development team should understand the required endpoints, data formats, booking logic, and error handling defined by the OCTO standard. 🔗 [Access the OCTO Specification](https://docs.octo.travel) Your integration must fully comply with the standard. We do not support modified request/response formats, undocumented or custom fields, or deviations from the booking and availability model. Non-compliance will prevent integration, as we are unable to support or maintain partial or custom implementations. ### Multi-Supplier Authentication (If Applicable) In standard OCTO implementations, a bearer token typically corresponds to a single supplier account. If your system manages multiple suppliers under a shared API credential (aggregator model), supplier context must be explicitly included in each request. In such cases, the Authorization header should follow this format: ``` Authorization: Bearer | ``` The supplier ID must uniquely identify the supplier context for the request. This ensures correct routing, validation, and reporting within the Prioticket platform. *** ### Prioticket’s OCTO Supplier Implementation Our adoption of OCTO is not just about compliance; it is designed to maximize efficiency, scalability, and ease of connectivity for our partners. We have developed a dedicated, production-grade OCTO library optimized for high-volume distribution and operational reliability. **Key capabilities include:** * **Runtime Pricing** – Prioticket’s standard approach across all integrations, including OCTO, is to retrieve both availability and pricing in real time — where supported by the supplier. This applies when the supplier has implemented OCTO’s Pricing and Notifications capabilities. It ensures end customers always see accurate, up-to-date rates, discounts, and availability without the need for manual updates. * **Runtime Availability** – For suppliers that do not support pricing at runtime, Prioticket retrieves only availability (vacancy) data in real time. This ensures customers always see the latest capacity information, even when prices are managed separately or not exposed through the supplier’s API. * **Efficient Caching** – When real-time retrieval is not feasible, Prioticket applies smart caching strategies to optimize performance and ensure a smooth, responsive booking experience — even during peak demand or when supplier systems have technical limitations. * **Dedicated Connectivity Environment** – OCTO supplier traffic runs in a separate optimized environment, ensuring stability, scalability, and no interference with other integrations. **Coming in 2026: Automated Product Ingestion**\ We're actively working towards supporting automated product ingestion for OCTO suppliers. Once available, this will further streamline onboarding and reduce time to market. Please note that this feature will require full OCTO capability coverage — including **Core, Content, Pricing, and Notifications**. These enhancements mean suppliers connected through OCTO benefit from faster onboarding, better data accuracy, and higher booking success rates, while maintaining full compliance with OCTO standards. *** ### Next Steps for Suppliers If you are a supplier looking to integrate with Prioticket: 1. Review the official [OCTO specification](https://docs.octo.travel) 2. Build your API interface strictly according to the standard 3. Certify your OCTO integration in the [official OCTO self-certification tool](https://certify.octo.travel/) 4. Reach out to Prioticket to begin the testing and onboarding process via [this link](https://customer.support.prioticket.com/servicedesk/customer/portal/5/group/10/create/123) 5. Once your integration passes compliance checks, we will enable connectivity for distribution For help during implementation, our team is happy to support your developers in understanding the OCTO requirements. Need help? Contact our [API Support Desk](https://customer.support.prioticket.com/servicedesk/customer/portal/5) *** ### What About Distributor-Side OCTO? OCTO also defines a **distributor-side implementation**, which allows resellers to consume data from Prioticket via OCTO. While we are capable of supporting distributor-side OCTO, we have developed a **much more powerful and feature-rich Distributor API**, which is our **strongly preferred approach** for resellers and OTAs. For more details on why our Distributor API is preferred over OCTO on the reseller side, and to understand feature differences, please refer to: 📘 [OCTO & Prioticket – Integration Overview](https://docs.prioticket.com/getting-started/octo-and-prioticket)\ 📊 [OCTO vs Prioticket API – Feature Comparison](https://docs.prioticket.com/getting-started/octo-and-prioticket/feature-comparison) *** ### Summary | Role | Integration Type | Recommended API | | ------------ | ----------------------- | ------------------- | | **Supplier** | Expose your products | ✅ OCTO Supplier API | | **Reseller** | Consume from Prioticket | ✅ Distributor API |