LogoLogo
SupportChangelogAPI ReferenceStatus
Distributor API
Distributor API
  • Welcome
  • Getting Started
    • Functionalities
    • Integration Process
      • Implementation Guide
    • OCTO & Prioticket
      • Feature Comparison
    • Postman & Interactive Documentation
    • Connect Once, Reach the World
      • Featured Suppliers
        • Supplier Overview Europe
        • Supplier Overview Americas
        • Supplier Overview Middle East
      • Featured Resellers
    • Statement on API Excellence
    • Frequently Asked Questions
  • Key Concepts
    • Product Structure
      • Product types and classes
      • Admission types
      • Extra Options
      • Pickup Points
      • Combi, Clusters, Bundles & Addons
        • Cluster
        • Combi
        • Addons
        • Bundle
    • Availability and Capacity
      • Availability
      • Capacity
        • Shared and Allocated Capacity
      • Availability API
    • Pricing Guide
      • Who are you?
      • Configurations
      • Variable Pricing
      • Dynamic Pricing
      • How It All Comes Together
    • Booking Logic
      • Cart Management
      • Payments
      • Cancellation & Refunds
      • Booking Questions
    • Additional Capabilities
      • Locations, Destinations and Categories
      • Recommendations
      • Promotions
      • Webhooks
      • Translations
    • Technical Concepts
      • Authentication
      • Idempotency
      • Rate Limiting
      • Timeout Handling
      • Error Handling
      • API versioning
      • Pagination
      • Formats
      • Headers
      • Caching
  • Endpoints
    • About
    • Authentication
    • System
    • Products
      • Stock
    • Availability
    • Reservations / Cart
      • Promocodes
    • Orders
      • Email & Vouchers
    • Payments
    • Contacts
    • Notifications
    • Models
  • Resources
    • Release notes
    • Roadmap
    • Postman
    • Swagger
    • Changelogs
      • Parameter Changelog
    • API Specs
      • V3.8 (Latest)
      • V3.7
      • V3.6
      • V3.5
    • Support
    • Certification
  • Status Dashboard
Powered by GitBook
On this page
  • The Four Pillars of the Prio Distributor API
  • Additional APIs for Full Flexibility
  • Create a booking

Was this helpful?

Export as PDF
  1. Key Concepts

Booking Logic

How to Book with the Prioticket Distributor API

With the Prio Distributor API, connecting to our platform and processing bookings couldn’t be easier. Whether you’re looking to browse product content, check live availability, or confirm bookings in real-time, our API offers a streamlined process designed for travel resellers, marketplaces, and OTAs.

This page explains the end-to-end booking flow, giving you a clear roadmap to building your integration, from retrieving content to issuing tickets.

The Four Pillars of the Prio Distributor API

The Distributor API is divided into four core areas, each designed to handle a key part of the booking journey:

🔗 API Type
💡 What It Does

Retrieve products, destinations, categories, and other key product details to populate your platform.

Check real-time availability, capacity, and time slots for the products you want to sell.

Temporarily hold reservations while you collect payment or manage a shopping cart.

Confirm reservations, create direct bookings, and retrieve barcodes/tickets for your guests.

Additional APIs for Full Flexibility

🔗 API Type
💡 What It Does

Secure your connection using OAuth-based credentials.

Use Prioticket’s Payment Service Provider integrations (optional) or handle payments yourself.

Manage guest profiles (only needed for recurring guests).

Set up webhooks to receive real-time updates on external booking changes.

Monitor API uptime and system health.

Create a booking

To book a product through this API, you generally need to follow these steps:

  1. Check availability and pricing: Use the Get Products and Get Availabilities endpoints to verify if tickets for the desired tour or activity are available for a specific date, time, and quantity.

  2. Request a booking hold: If tickets are available, request a pricing / availability hold for the booking using the Create Reservation endpoint.

  3. Collect payment: Once a booking hold is requested, collect payment either through the provided payment endpoints or via your own payment service provider.

  4. Confirm the booking: Finalize the booking by confirming it using the confirm order endpoint.

PreviousHow It All Comes TogetherNextCart Management

Last updated 13 days ago

Was this helpful?

Content APIs
Availability APIs
Reservation APIs
Booking APIs
Authentication APIs
Payment APIs
Contact APIs
Notification APIs
System APIs