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:
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
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:
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.
Request a booking hold: If tickets are available, request a pricing / availability hold for the booking using the Create Reservation endpoint.
Collect payment: Once a booking hold is requested, collect payment either through the provided payment endpoints or via your own payment service provider.
Confirm the booking: Finalize the booking by confirming it using the confirm order endpoint.
Last updated
Was this helpful?