# Feature Comparison ### Overview * **Prioticket Distributor API V3.8:** A full-featured API specification designed to provide distributors access to a wide range of tourism-related products, including real-time availability, booking management, pricing, content management and customization. * **OCTO API 1.0:** An industry-standard API specification focused on creating a common data format for exchanging availability and booking details among suppliers and distributors. {% hint style="info" %} Note: This comparison evaluates the specifications of both APIs, not the systems behind them. {% endhint %} *** ### Strengths & Weaknesses #### **Prioticket API Strengths** * **More extensive booking management** with full order modifications and cart-based functionality. * **AI-driven localization** for automated translations and currency handling. * **Dynamic pricing and discount flexibility** beyond standard base pricing. * **Strong content management tools** including bulk updates and media handling. * **Channel management tools** for better inventory allocation. * **Advanced recommendations and bundling** for better customer experiences. * **Dependency-based booking system** ensuring required prerequisites for specific services. * **Direct integration with multiple Payment Service Providers (PSPs).** * **Fully capable of powering a complete booking website** without the need for an intermediary reservation system. #### **Prioticket API Weaknesses** * **More complex integration** due to the vast number of features. * **Potentially higher setup time** for developers unfamiliar with its extensive functionality. #### **OCTO Strengths** * **Industry-wide adoption** due to its standardized data structure. * **Easier integration** for distributors working with multiple suppliers following OCTO standards. * **Simplified structured approach** to booking and availability, reducing complexity. * **Greater interoperability** between various platforms using the same schema. #### **OCTO Weaknesses** * **Limited customization options** for pricing, booking flows, and product modifications. * **Lacks support for multi-day products and itineraries.** * **Does not support seating management** or advanced booking dependencies. * **No direct integrations with payment providers**, requiring external handling. * **No official support for content listing, filtering, locations & pickups, or categories, making it unsuitable for a fully functional booking website.** * **OCTO is still a young initiative**, and while some of these features are under review, widespread adoption could take significant time. *** ### Feature Comparison | Feature | Distributor API V3.8 | OCTO API 1.0 | | ------------------------------------ | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ | | Product Content | Detailed product descriptions, pricing, images, and media assets. | Not supported. | | Filtering & Search | Advanced filtering by category, location, tags, and attributes. | Not supported. | | Availability Checks | Real-time availability with advanced slot-based rules. | Provides real-time availability retrieval. | | Booking Management | Full booking lifecycle: create, modify, cancel, retrieve vouchers. | Supports essential booking operations with standardized workflows. | | Pricing & Discounts | Supports dynamic pricing, custom discounts, early-bird pricing, and tiered pricing. | Provides structured base pricing options. | | Multilingual & Multicurrency | AI-powered translation for product listings, automatic currency conversion. | Supports multilingual product descriptions and multi-currency transactions. | | Webhooks & Notifications | Customizable webhooks for booking status changes, cancellations, and updates. | Supports event-driven notifications for key booking and availability updates. | | Cart & Order Handling | Multi-product bookings, ability to add items to existing orders. | Focuses on single transaction per order but supports structured modifications. | | Direct Booking | Supports instant booking without reservation. | Not supported. | | Runtime Pricing | Supports final quote of the price before making a booking. | Supports final quote of the price before making a booking. | | Pickup & Logistics | Pickup location management. | Not supported. | | Customization & Add-ons | Supports extras, product options, group pricing, family pricing, and product add-ons. | Not supported. | | Seating & Allocations | Configurable seating charts, flexible allocations. | Not supported. | | Cancellations & Refunds | Advanced cancellation policies, automatic refunds, and rules-based handling. | Supports structured cancellation terms but relies on supplier policies. | | Reporting & Analytics | Detailed sales, performance tracking, and customer insights. | Basic reporting, relies on external data processing. | | Product Recommendations | AI-driven recommendations based on customer preferences and booking patterns. | Not supported. | | Dependency Management | Ensures proper sequencing of bookings, such as requiring an entry ticket before an add-on. | Not supported. | | Combi & Cluster Products | Allows bundling of multiple products together, creating unique packages. | Limited to individual product bookings. | | Itineraries & Multi-Day Tours | Fully supports complex, multi-day travel plans and custom itineraries. | Not supported. | | Category & Destination Management | Organizes products by themes, destinations, and interest-based categories. | Not supported. | | Direct Payment Provider Integrations | Supports multiple PSPs like Stripe, PayPal, Adyen, and more. | No direct PSP integrations; handled externally. | | Promotional Codes & Discounts | Fully supports promo codes, discount campaigns, and seasonal offers. | Not supported. | | Favorites & Wishlists | Allows customers to favorite products for easier access. | Not supported. | *** ### Developer Experience & Documentation | Aspect | Distributor API V3.8 | OCTO API 1.0 | | --------------------- | ----------------------------------------------------------- | ------------------------------------------------------- | | API Documentation | Comprehensive and feature-rich documentation with examples. | Well-structured, standardized industry documentation. | | Postman Collections | Available for easy testing and onboarding. | Available for streamlined API testing. | | SDKs & Libraries | Some SDKs available for faster implementation. | Mostly relies on third-party community implementations. | | API Playground | Interactive API testing tools available. | API reference tools included. | | Developer Support | Dedicated support team with onboarding assistance. | Community-driven with some direct support. | | Code Samples & Guides | Extensive examples for various use cases. | Limited examples but clear documentation structure. | *** ### Summary Both APIs provide robust solutions for distributing tourism-related products, but they cater to different needs. **Prioticket API excels in customization, dynamic pricing, and cart-based booking**, making it ideal for companies needing more flexibility. **OCTO API offers a standardized, widely adopted structure**, which simplifies integrations for distributors working with multiple suppliers. For developers, **both API specifications provide strong documentation and resources**, but **Prioticket API offers more hands-on support, interactive tools, and SDKs, while OCTO API focuses on clear structure and industry compliance.** OCTO API, while promising as an industry-wide standard, currently lacks key features required to build a fully functional booking website. Prioticket API is a **complete, enterprise-ready solution**, allowing direct website development without the need for an intermediary system. OCTO provides basic booking and availability capabilities but does not compare in terms of feature support. The choice depends on whether the priority is **deep feature customization (Prioticket API) or broad interoperability (OCTO API).** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.prioticket.com/getting-started/octo-and-prioticket/feature-comparison.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.