Availability
Room for one more?
Was this helpful?
Distributor API
Room for one more?
Was this helpful?
Get realtime availability & pricing.
Prioticket provides two distinct endpoints to support accurate availability and pricing:
Availability & Pricing Variations API – Returns detailed pricing rules and logic, ideal for advanced UI behavior or transparency in pricing explanations.
Availability & Calculated Pricing API – Returns real-time availability and final calculated pricing, optimized for booking flows and calendar rendering.
Each serves a different purpose in the booking journey. To implement them correctly and avoid common pitfalls (e.g. mismatched prices, missing availability, performance issues), please refer to the full documentation on GitBook.
Returns detailed pricing rules, variations, and conditions for the selected product.
Use this endpoint to understand why and how prices change, based on rules such as date-based pricing, quantity discounts, time-of-day rules, and other dynamic configurations.
Ideal for building advanced UIs that explain pricing logic to end users or trigger specific behaviors based on rule conditions.
📘
[FILTER] on distributor_id.
501[FILTER] on product_id.
["PRODUCT_ID_123"][FILTER] From which date availability is requested.
If supplied with to_date , then availability request is for a date range.
If supplied without to_date, then for a single date availability is requested.
[FILTER] Till which date availability is requested.
If this is empty, availability will be searched for the given from_date only.
[FILTER] Include disabled / closed (availability_active:false) entries.
falseExample: true[FILTER] on availability_capacity_id.
[FILTER] The minimum remaining availability_spots_open.
[FILTER] The iteration depth of the included entries of the sub-products in the response. This will not apply to sub-products which have shared capacity linked to the main product.
Example Setup:
Product 101 (Main)
Product 201 (Sub)
Product 301 (Nested)
Product 302 (Nested)
Product 202 (Sub)
Product 401 (Nested)
Product 402 (Nested)
sub_products_depth:0 will return Product 101.sub_products_depth:1 will return Product 101, 201 and 202.sub_products_depth:2 will return Product 101, 201, 202, 301, 302, 401 and 402.0Example: 1[CACHE] The If-Modified-Since request HTTP header makes the request conditional: the server will send back the requested resource, with a 200 status, only if it has been modified after the given date.
If the resource has not been modified since, the response will be a 304 without any body; the Last-Modified response header of a previous request will contain the date of last modification.
Note that if a single resource has changed, all records matching your request will be returned, not just those changed after the given date. This provides you with an efficient caching method.
Wed, 21 Jan 2022 07:28:00 GMTReturns up-to-date availability and pre-calculated pricing based on the selected configuration and party size.
This endpoint provides simplified access to final pricing, ideal for rendering calendars and booking flows. For advanced use cases and detailed logic (e.g. price variations, rule-based conditions), refer to our extended documentation.
📘
Unique identifier for the product assigned by Prio.
[FILTER] on distributor_id.
501[FILTER] From which date availability is requested.
If supplied with to_date , then availability request is for a date range.
If supplied without to_date, then for a single date availability is requested.
[FILTER] Till which date availability is requested.
If this is empty, availability will be searched for the given from_date only.
[FILTER] Include disabled / closed (availability_active:false) entries.
falseExample: true[FILTER] on availability_capacity_id.
[FILTER] The minimum remaining availability_spots_open.
[FILTER] The iteration depth of the included entries of the sub-products in the response. This will not apply to sub-products which have shared capacity linked to the main product.
Example Setup:
Product 101 (Main)
Product 201 (Sub)
Product 301 (Nested)
Product 302 (Nested)
Product 202 (Sub)
Product 401 (Nested)
Product 402 (Nested)
sub_products_depth:0 will return Product 101.sub_products_depth:1 will return Product 101, 201 and 202.sub_products_depth:2 will return Product 101, 201, 202, 301, 302, 401 and 402.0Example: 1[FILTER] Only show entries modified after the given date.
Fetch incremental updates through this endpoint.
[PAGING] Items Per Page - Allows user's to configure the items_per_page value. For example, to load 100 items per page, the developer may point the user to a url with the query string ?items_per_page=100.
This parameter is mainly usefull to manage response times, higher values result in longer response times and therefore it is recommended to keep this value as low as possible. We do allow to adjust this value so it can be used to batch/cache/update inventory at once.
Clients should anticipate that the value of this parameter may not be honored by the API, and should rely exclusively on the contents of the items_per_page response element in calculating actual page size.
10Example: 5[PAGING] Index-based paging - Allows user's to jump directly to a specific item position within a list of items. For example, to load 10 items starting at item 200, the developer may point the user to a url with the query string ?start_index=200.
1Example: 1[PAGING] Page-based paging - Allows user's to jump directly to a specific page within the items.
This is similar to index-based paging, but saves the developer the extra step of having to calculate the item index for a new page of items. For example, rather than jump to item number 200, the developer could jump to page 20. The urls during page-based paging could use the query string ?page=1 or ?page=20. The page_index and total_pages properties are used for this style of paging.
1Example: 1[CACHE] The If-Modified-Since request HTTP header makes the request conditional: the server will send back the requested resource, with a 200 status, only if it has been modified after the given date.
If the resource has not been modified since, the response will be a 304 without any body; the Last-Modified response header of a previous request will contain the date of last modification.
Note that if a single resource has changed, all records matching your request will be returned, not just those changed after the given date. This provides you with an efficient caching method.
Wed, 21 Jan 2022 07:28:00 GMTRequest for availability & pricing.
Represents the version of the service API that's served in the response.
3.8.0