Availability & Pricing API

These endpoints allow you to get live availability and pricing date on Tiqets products.

This section provides an in-depth look at how to handle product availability, ticket limits, and pricing when integrating with the Tiqets Distributor API.

You'll find recommendations for caching strategies, explanations of availability time ranges, how to interpret ticket limits at both product and variant levels, and how to handle family ticket types.

We also cover key pricing rules, including Tiqets' retail pricing policy, the concept of dynamic pricing, and how to ensure checkout consistency by refreshing data regularly.

Make sure to follow these guidelines to ensure a smooth customer experience and full compliance with Tiqets’ platform requirements.

Availability requirements

Caching

We encourage distributors to create a copy of product content, price and availability information in their own system, periodically updating it to ensure freshness and accuracy. Please find our recommendations for caching intervals here: Caching Product and Availability Information

Please also take note of our suggestions for handling products that are not available: Unavailable Products

The Availability & Pricing API allows partners to obtain information regarding Tiqets' products and their availability.

Availability Time Range

The Availability endpoint allows the retrieval of 31 days of availability and pricing per API request. The limit has purely technical reasons and is in place to ensure the API remains easily consumable. Due to the limit, API response messages do not get too big and response times stay relatively fast. However, it is possible to request availability and pricing for a longer time range, and we encourage all of our API partners to do so. Products can have availability and pricing for up to one year; we recommend retrieving availability and pricing for at least three months. In order to do so, please send separate API requests for time ranges of up to 31 days.

Please note that the returned availability time range depends on the configuration of each individual product. This means that some products might not return availability the full three months.

Example If the current date is June 12, 2025 and you want to retrieve availability for product 123456 for the next three months, you can send the following three requests:

  GET https://api.tiqets.com/v2/products/123456/availability?start_date=2025-06-12&end_date=2025-07-11
  GET https://api.tiqets.com/v2/products/123456/availability?start_date=2025-07-12&end_date=2025-08-11
  GET https://api.tiqets.com/v2/products/123456/availability?start_date=2025-08-12&end_date=2025-09-11

Availability Limits

The Availability endpoint returns four elements that reflect the limits for minimum and maximum tickets that can be booked within an order. There are limits on product as well as on variant level. In order to create a successful order, all limits need to be respected.

Product level

• availability: Total number of tickets availabile for the product and date/timeslot. This value is volatile and can change frequently.

• max_tickets_per_order: Maximum number of tickets within one order. This is a fixed value which usually does not change frequently.

Variant level

• max_tickets: Maximum number of tickets available for the given variant. This value is volatile and can change frequently.

• min_per_order: Minimum number of tickets required to be booked if this variant is selected. This is a fixed value which usually does not change frequently.

This means:

• The number of tickets in an order needs to be smaller than or equal to the minimum of availability and max_tickets_per_order.

• The number of tickets per variant needs to be equal to or larger than min_per_order (if the value is not null) and smaller than or equal to max_tickets. Please keep in mind that variant dependencies also need to be respected.

Family tickets

Family tickets allow more than one visitor to use one shared ticket, usually in a group of a defined number of adults and children. The availability for variants of type family works differently than for all other variant types: Please always divide the availability returned for the family variant by the number of occupied tickets.

Example:

• id: 14248

• variant_type: family

• label: Family

• description: '2 Adults and 2 Children'

• maximum_visitors_per_ticket: 4

• max_tickets: 14

The maximum number of family tickets that can be bought in this case is 14 // 4 = 3. Each ticket is valid for 2 adults and 2 children, meaning 3 tickets are valid for a total of 6 adults and 6 children.

Pricing Requirements

It is expressly prohibited to impose any additional fees on the price paid by the end-customer. The price charged by the supplier to the customer, in the absence of any distribution partners, must be identical to the price charged to the customer when distribution partners are involved.

Consequently:

• The Tiqets Retail Price, as communicated via the API, must be adhered to by the distributor at all times. Any liability arising from deviations from these pricing conditions shall be the sole responsibility and risk of the distributor.

• For transparency it is required that the distributor presents the price breakdown of Retail Price, Sale Ticket Value, and Booking Fee (in case a Booking Fee is being charged).

Price changes and "Dynamic Pricing"

Prices are determined by our suppliers and can be changed by them at will. Although the vast majority of products exhibit stable pricing throughout the year, some products' prices fluctuate. The most common pricing approaches featured in our catalog:

• Stable Pricing: Still the most common approach, prices tend to change once or twice per year.

• Peak/Off-Peak Pricing: A significant portion of our products tend to charge higher prices during visitor peaks, where a peak may be defined as:

  • Certain days of the week (weekday vs. weekend)

  • Certain hours of the day (Sunrise/sunset, or simply the time that most people chose to visit)

  • Certain weeks/months that are considered to be "Peak Season"

• Dynamic Pricing: A handful of products frequently changes prices (up to multiple times per day) depending on a variety of not disclosed factors. Therefor prices may increase or decrease at no particular frequency.

An example of Peak/Off-Peak pricing is test product 1006521 (Planet Earth: Apocalypse Tour) in the sandbox. Variant 38283 has seasonal price changes on the first of March, June, September, and December.

Please cache and refresh all availability and pricing information conform our recommendation, to increase accuracy and checkout success rates.

An example of this behaviour is product 1006521 (Planet Earth: Apocalypse Tour) in the sandbox. Variant 38283 has seasonal price changes on the first of March, June, September, and December.

⚠️Deprecation notice: dynamic_pricing field The meaning and value of the "Dynamic Pricing" field in the API has changed over time and we expect to remove this field in a future version of our API. Many products that are currently marked as "Dynamic Pricing" will actually have prices change very rarely. Please ignore this field and always validate prices before creating an order. This minimizes the risk of being invoiced an unexpected amount or the end-customer paying the incorrect price.

Pricing fields, interpretation and requirements

⚠️Deprecation notice: price_son field The price_son field has been deprecated and should be ignored. Please only refer to the price_mediation field.

Due to the variety of contract types that Tiqets has with its suppliers, different price fields are exposed to its distributors. Each having their own use cases.

The following price components are exposed in price_mediation field of the pricing and availability endpoints:

► sale_ticket_value_incl_vat:

• Basic price of a single ticket from the supplier.

• If booking_fee_incl_vat has a value greater than 0, sale_ticket_value_incl_vat should be shown to the customer as the Face Value Price.

• Visibility: Conditionally shown if booking_fee_incl_vat > 0.

► booking_fee_incl_vat:

• Booking fee. This is an amount sometimes added on top of the supplier's price to generate additional revenue.

• The booking fee must be shown to the end customer to ensure transparency about additional service fees and to avoid misleading the customer about the supplier's direct prices.

• Visibility: Must be shown if the value is greater than 0.

► total_retail_price_incl_vat:

• Total retail price, including VAT.

• This is the sum of sale_ticket_value_incl_vat and booking_fee_incl_vat.

• Distributors are not allowed to charge more than the total_retail_price_incl_vat.

• Visibility: Must always be shown.

► distributor_commission_excl_vat:

• Distributor's commission, excluding VAT.

• This is an estimated value and may fluctuate based on various additional costs incurred by Tiqets to fulfill the order, such as payment costs, currency conversion costs, or other expenses.

• For products with dynamic pricing, the final commission amount will be specified in the invoice.

• Visibility: This field is not shown to customers on the checkout page.

► prediscount_price_incl_vat:

• This price, if present, indicates that a discount applies.

• The prediscount_price_incl_vat represents the normal (higher) price and provides the Distributor the opportunity to show their customers that they are getting a good deal.

• Visibility: Must be shown if present to indicate the discount and highlight the deal to the customer.

Variant dependencies

There can be different types of variants for a product. A variant can be stand-alone or require another variant. Also, there might be an add-on option that can be added on top of a variant.

Different offerings of the same product can be represented by different groups.

Variant type The variant_type field provides structure and classification of Tiqets' variants and to enable partners to easily map the variants to their system.

Tiqets uses these variant types:

• adult: Adult type tickets

• youth: Youth type tickets

• child: Child type tickets

• infant: Infant type tickets

• senior: Senior type tickets

• family: Family type tickets

• regular: Generic entrance tickets/add-on which valid for all type of tickets

• reduced: Generic discounted type tickets (Military/Handicapped/Special card holders)

Since the variant types are configured based on the ticket types available for the venue, every product has its own individual variant type setup.

The exact definition of the variant type is returned as label, the description contains additional details if necessary.

Age ranges are not part of the variant label or description. The minimum and/or maximum age is returned separately as age_range.

While one product might use separate variants for adult, youth, child, and infant, another product might use adult and child only and/or apply different age ranges for the variants.

A special case is the family variant type. This is one ticket for more than one person, e.g. two adults and two children. The exact group size and (age) restrictions are set individually for each variant.

Some products may have repeated variant_types. For example, Hop-On-Hop-Off products may have adult tickets for 24 hours and 48 hours. Both of them have the variant type adult.

Variant valid_with If a variant contains a valid_with_variant_ids that variant can only be selected/bought with the variant_id's in the valid_with list. In the API test environment, product 1006521 (Planet Earth: Apocalypse Tour) variant 38281 is an example of valid with case where it can only be bought with variant 38280.

!▬▬▬ Valid With (URL: https://cdn.tiqets.com/partner_api/docs/images/valid_with_validation.png "Valid_with")

Variant add-ons The is_addon attribute allows you to identify add-on variants. If true, the variant is an add-on and cannot be bought on its own. An add-on can only be added to a non-add-on variant of the same group.

A common example for an add-on would be an audio guide for a venue that can be bought in combination with an entry ticket but not on its own.

Variant group The Availability & Pricing API returns groups that categorize the tickets by what services are included or the validity of the different tickets. This grouping helps you to identify which product variants belong to the same product with exactly the same offering.

The following applies to groups:

• Group IDs are unique across the system. This means that that any group ID will only appear for one product. (Exception: group_id 0)

• If a variant is not part of a group, the returned group_id is 0.

• Multiple group IDs can be assigned to one variant. For example, an infant ticket might belong to multiple categories.

• Group names are available in English only.

Products 974282 and 1006356 in the API test environment are examples for products that make use of variant groups.

Example: This is a possible variant configuration, taking into account all flags mentioned above:

• Group: Entry Ticket

• Adult (stand-alone)

• Child (stand-alone)

• Infant (valid with Adult, Child, Reduced variant)

• Audio guide (add-on)

• Group: Entry Ticket and Guided Tour

• Adult (stand-alone)

• Child (stand-alone)

• Infant (valid with Adult, Child, Reduced variant)

You can find the corresponding API response for this variant setup on the response sample for the endpoint that returns all active product variants.

Please note that the same infant variant is used for both groups. Also, the Audio guide add-on is not available for the product variant that has a guided tour included.