Suppliers, Products & Rates

Travel Curious connects Resellers to Suppliers through a channel binding process - a commercial agreement that makes a Supplier's Products and Rates visible to your API requests. If you do not see the Suppliers or Products you expect, contact the Supplier directly or reach out to your Travel Curious Integration Manager.

Suppliers

A Supplier represents the operator providing the travel experience - a tour company, museum, attraction, or event venue. The Supplier object carries the operator's identity, contacts, accepted traveler types, business hours, and location data.

🔗 Available Endpoints & Params

⚙️ Supplier Object Capabilities

📥 Fields Recently Added to Supplier Models

👁️‍🗨️ Response Example

Get Supplier call response example below. Note: the id field needs to be unique and is used to identify the Supplier.

xxxxxxxxxx

Products

A Product is a bookable experience offered by a Supplier - a walking tour, museum entry, river cruise, parasailing session, or live show. Each Product belongs to one Supplier and may have multiple Rates.

🔗 Available Endpoints & Params

⚙️ Product Object Capabilities

📥 Fields Recently Added to Product Models

👁️‍🗨️ Response Example

xxxxxxxxxx

Rates

A Rate defines a specific bookable option within a Product. A single Product can have multiple Rates, for example, separate morning and afternoon sessions with independent capacity, or a standard and premium tier. Each Rate has its own pricing, hours, cancellation policy, and hold configuration.

🔗 Available Endpoints & Params

⚙️ Rate Object Capabilities

📥 Fields Recently Added to Rate Models

👁️‍🗨️ Response Example

xxxxxxxxxx

Rate Type

There are three different rate types: FREESALE, PASS, and RESERVED.

• FREESALE Tickets and entry passes are available during the opening hours of the attraction, and there is no specific entry time.
• PASS Rates are used for Products where access is granted multiple times, whereas FREESALE and RESERVED Rates are normally single-use.
• RESERVED Rates can be with or without capacity, depending on the requirements and inventory defined by the Supplier, and always require a hold to ensure that the availability for a certain date and time does not change between the availability check and the booking request. Bookings can, however, be rejected if there is insufficient capacity at the requested date and time.

Being able to handle both types of product rates gives you, the Reseller, the flexibility to manage both general admission (FREESALE) and time-slot defined (RESERVED) types. This allows you to accommodate a broader range of use cases for different suppliers and their connected products.

Validity vs. Hours

The rate.hours are used to define the available times for the product, which are the product operating hours the traveler is able to enter the attraction.

rate.valid is used to determine when the rate is available for purchase. Bookings can only occur within the defined valid from and valid until attributes. Some suppliers set up products ahead of their validity date for visibility and preparation. Please note and enforce the validity dates.

An example for this would be if a Supplier sets up 2 different rates: General Admission ticket for 2026 and 2027.

xxxxxxxxxx

name: General Admission

code: GA2023

valid: 2026-01-01 to 2026-12-31

name: General Admission

code: GA2024

valid: 2027-01-01 to 2027-12-31

They are available to be booked the entire year, but there are specific days and times the product is available in that year.

xxxxxxxxxx

rate.hours[0]

- Monday, Tuesday, Wednesday, Thursday

- 5:00pm to 7:00pm

- valid: 2023-01-01 to 2023-12-31

Rate minTravelers & maxTravelers

This field represents the minimum and maximum number of travelers to qualify for this rate which means the maximum number of tickets that can be purchased for this rate. The data is being mapped from the Supplier setup. This will prevent customers from selecting more than the allowed quantity and getting errors during Hold and Booking requests.

Rate travelerTypes, ageBand and modifier

Support list of ageBand to describe a particular age or occupation of a traveler type

• Ideally, being able to consume the name and modifier to support the full breadth of price/traveler types the operators provide. These could be things like EU_CITIZEN, MILITARY

• Minimally support all age bands in the specifications ADULT,ANY,CHILD,INFANT,SENIOR,STUDENT,YOUTH

  • The ANY type may be used instead of the above listed ageBand, if distinctions between age or occupation are not relevant to the product. It’s a generic ageband type used by some suppliers and it’s recommended to be supported, otherwise, a workaround needs to be done to map that value.

• Solve multiple instances of the same age band. There are instances where operators will send 2 prices for the same traveler type (ie 2 - ADULT). This typically means there is a difference in the name/modifier that makes it a different traveler type still limited to adults OR it means they’re running a special price for a limited time. You can:

  • Consume name/modifier and display both
  • Display only one lower or higher of the 2 prices

Cancelable Flag

The cancellation policy for a product is indicated by the boolean cancelable = true or cancelable = false. When true, it indicates that bookings made under this Rate are eligible for cancellation. Please note that this does not refer to a hold, which can always be released or canceled regardless of this setting.

✨Tip: You can also check the refundable boolean on the Rate, which indicates if a booking made with this Rate is eligible for a monetary refund. This defines the financial policy, whereas cancelable defines the operational ability to void a booking.

Rate Prices

Each Rate object contains a prices array listing baseline prices by traveler type. These are always superseded by the Price Schedule when a scheduled price exists for the requested date - always check the Price Schedule first and use static prices only as a fallback.

However, because experience prices often fluctuate based on seasonality or specific dates, you must use the Price Schedule API to retrieve the actual bookable price for a specific date.

When placing a Hold or a Booking, provide the priceId from Price Schedule response.

More detailed pricing implementation steps can be found in the Pricing section.

Rate Traveler Type

Defines the eligibility requirements and classification for a traveler. Includes age ranges, modifiers, and display information.

⚙️ Traveler Type Object Capabilities

📥 Fields Recently Added to Traveler Type Models

Traveler Type Constraints New

Adds a structured constraints array (with min, max, and type) to the travelerType object to help you programmatically enforce operational rules like age or weight restrictions.

📥 Fields Recently Added to Constraints Models