How to Find and Display Experiences Using the Tiqets API
This guide will walk you through creating a complete experience discovery and display system using Tiqets' Experience API. You'll learn how to search for experiences in a destination and then showcase the related products on your website.
Introduction
When building a travel platform, one of the most important features is helping your customers discover amazing experiences. The Tiqets Experience API enables you to:
Search and filter experiences across destinations worldwide
Access rich content including images, descriptions, and ratings
Retrieve product information for booking integration
Display compelling experience pages that convert browsers into bookers
Let's imagine you want to create an "Amsterdam Experiences" page for your travel website. You'd like to showcase the best museums, attractions and activities in the city, and when users click on something that interests them - let's say the Van Gogh Museum - you want to show them all the available ticket options for that experience.
Why Use the Experience API?
The Experience API is the foundation of content-rich travel platforms. Here's what it enables:
Curated destination content - Access professionally written descriptions and quality images
Product variety - Display multiple ticket options for each experience
Multi-language support - Serve global audiences in their preferred language
Flexible filtering - Help customers find exactly what they're looking for
The Complete Integration Journey
Let’s build this step by step, focusing on how you’ll gather and structure the data to create compelling experience pages. First, build your experience catalog then use our content to create detailed experience pages and finally, list the right products for each experience.
Step 1: Building Your Amsterdam Experiences Catalog
First, you'll use the Search and Filter Experiences endpoint to collect all the experiences available in Amsterdam. This data will form the foundation of your experiences catalog.
1.1 Search and Filter Experiences API Call
Query Parameters:
city_id— Target city (Amsterdam = 75061)page_size— Number of items to return (e.g. 50)lang— Response language code (e.g. en)currency— Price currency code (optional, default: EUR)type— Experience type filter (optional: venue, activity, service, poi)
1.2 Understanding the Response Data
The API returns structured data that contains everything you need to build compelling experience pages:
What each field gives you:
id- Unique identifier for detailed lookups (144593)title&tagline- Perfect for experience cards and page headersexperience_url- Direct link to Tiqets experience pageimages- Array of images in multiple sizes (small, medium, large, extra_large)address- Complete location details including coordinatesratings- Social proof with total count and average ratingfrom_price- Starting price to attract customers (€26.00)product_ids- Related products for building ticket options
Step 2: Creating Detailed Experience Pages
Now that you have your experiences catalog, you'll want to create detailed pages for each experience. Let's use the Van Gogh Museum as an example and fetch its complete data using the Get Single Experience endpoint.
2.1 Get Single Experience API Call
Path Parameters:
experienceId— Unique experience identifier (Van Gogh Museum = 144593)
Query Parameters:
lang— Response language code (optional, default: en)currency— Price currency code (optional, default: EUR)
2.2 Structuring Your Experience Page Template
With the detailed experience data, you can build rich, informative page templates

Step 3: Building Product Information for Each Experience
The experience object contains product_ids that represent different ticket options. To complete your experience pages, you'll want to collect detailed product information using the Product endpoint.
3.1 Understanding the Product Relationship
Each experience contains a product_ids array that lists all the different ticket options available for that experience. For the Van Gogh Museum (ID: 144593), you'll find different products, each representing a unique ticket type:
Example product types you might find:
703244 - Basic entry ticket
747480 - Guided tour with expert commentary
883353 - Skip-the-line access with audio guide
915319 - Entry ticket including audioguide
915321 - Small group tour experience
The product IDs in the experience response are your gateway to building a comprehensive ticket selection page. You'll use these IDs with the Product endpoint to fetch detailed information about pricing, descriptions, and booking options for each ticket type.
This allows you to create rich product comparison pages where customers can choose between different products - from basic entry to premium guided tours. You can also explore further how to build great product groups here:How to implement Cross & Upselling using Product Groups
What's Next?
Once you have experiences displaying beautifully on your website, consider these next steps:
Integrate Availability & Pricing - Show real-time availability and pricing
Add Booking Capability - Let customers complete purchases on your platform
Implement Language Selection - Serve global audiences
Boost your sales with Cross and Upsell product groups and our maximised product availabilities
Set Up Webhooks - Stay updated on inventory changes
Resources and Support
API Documentation - Complete technical reference
API Keys - Get your credentials set up
Last updated
Was this helpful?

