A tours and activities API lets a travel platform search, price and book tours, attractions, theme-park tickets and local experiences from many suppliers through one integration. It returns live dates and time slots, prices per adult, child or group, and a voucher after booking. Tripgic’s Activities & Tours API does this in the same JSON as its flights and hotels.
This guide explains how an activities API works, what data it returns, how it differs from an attraction ticket API and a tour package API, who uses one, what it costs and how to connect it. Facts about Tripgic come from its own Activities & Tours API page, pricing page and documentation, read on 26 October 2026.
What Is a Tours and Activities API?
An application programming interface (API) lets two systems talk to each other. A tours and activities API connects your booking platform to the companies that sell experiences, so your platform can search, price and book them without anyone typing a reservation by hand.
“Tours and activities” covers a wide range. It includes guided city tours, day trips, food and cultural experiences, museum and landmark tickets, theme-park entry, shows, and adventure activities such as diving or desert safaris. The industry also calls this category “things to do”, “experiences” or “attractions”.
Two things make the category different from flights and hotels. First, there is no single global system that holds the inventory. Activities are sold by a very large number of local operators, many of them small. Second, the product is consumed at a fixed place and time, so availability, pricing and the final document all depend on a date, a time slot and the number and type of participants.
For a platform that already sells flights or hotels, activities add a product to a trip the customer has already planned. A traveller who has booked a hotel in a city for three nights is a natural buyer for a tour, a ticket or a day trip in the same city on the same dates.
Activities API vs Tours and Activities API vs Attraction Ticket API
Buyers search for this product under many names, and providers use them loosely. The names matter less than the scope, so check which products a given API actually covers.
| Name | What it usually covers | Typical delivery |
|---|---|---|
| Tours and activities API | Guided tours, day trips, experiences, attractions and tickets together | Voucher or e-ticket |
| Activities API / experiences API / things-to-do API | Usually the same scope as above, under another name | Voucher or e-ticket |
| Attraction ticket API | Entry tickets only: museums, theme parks, landmarks, shows | Dated or timed e-ticket |
| Tour package API | Pre-packaged, often multi-day tours with a fixed itinerary | Booking confirmation and travel documents |
| Tour operator software | Software that an operator uses to run its own tours and sell them | Not an inventory source for resellers |
The last row is a frequent source of confusion. Tour operator software helps an operator manage its own departures, guides and bookings. It is not a way for a reseller to buy other companies’ activities. If you want to sell many operators’ products, you need an activities API, not operator software.
At Tripgic the split is explicit. The Activities & Tours API sells single experiences: tours, attractions, theme parks, day trips and tickets. The separate Tour Package API sells pre-packaged tours through its own flow.
How a Tours and Activities API Works
The flow follows the same search, price and book pattern as other travel APIs, with two extra steps that are particular to activities: choosing a time slot and delivering a redeemable document.
- Search. Your platform sends a destination, a date and optional filters such as category. The API returns matching products.
- Availability. For the chosen product, the API returns open dates and time slots, each with its own capacity.
- Pricing. The API returns the live price for each option and participant type: adult, child, group.
- Booking. You send the traveller details and the chosen slot, and the API confirms the booking with the supplier.
- Voucher. The API returns a voucher or e-ticket, often with a QR code, and the confirmation type.
- Redemption. The traveller shows the voucher at the venue or meeting point.

The voucher step is what makes activities different. A flight booking ends in an airline booking reference and a ticket number; a hotel booking ends in a confirmation. An activity ends in a document the traveller has to show at a specific place, sometimes at a specific time, so the API has to tell you what form that document takes and what the traveller must do with it.
The search, price and book core is the same as in a flight booking API. Only the inventory and the final document change, which is why a platform that already sells flights or hotels can add activities without a new architecture.
What Data You Get From a Tours and Activities API
Good activity content is detailed, because travellers buy experiences on the strength of the description and the photos. A strong API returns far more than a title and a price.
| Data type | What it includes | Why it matters |
|---|---|---|
| Product info | Title, description, photos, duration, languages | Helps travellers choose with confidence |
| Availability | Open dates, time slots, remaining capacity | Prevents selling a slot that is already full |
| Pricing | Price per participant type, currency | Shows the true cost before booking |
| Options | Pickup, language, add-ons, meeting point | Lets travellers choose the version they want |
| Cancellation | Free-cancellation window, refund rules | Sets clear expectations and reduces disputes |
| Confirmation | Instant or on request, voucher type | Tells the customer what happens after they pay |
| Voucher | E-ticket, QR code, redemption note | Lets the traveller enter or join |
A single tour can have several options, several time slots per day and several participant types, so the data model is richer than a hotel room or a car. Plan your database and your product pages around options and slots from the start, rather than adding them after the first release.
Where Activities Content Comes From
There is no global distribution system for activities. The inventory is spread across a very large number of local operators, and it reaches resellers through four layers.
- Direct operators. The local company that runs the tour or owns the venue.
- Reservation systems. Booking software that many operators use to manage their slots and capacity.
- Resellers and marketplaces. Large platforms that group many operators and resell their products.
- Aggregating APIs. APIs that combine several of the above into one normalised feed for platforms.

Connecting operators one by one is not realistic for most platforms. A single popular city can have hundreds of activity providers, each with its own format, rules and voucher. This is why most platforms use one API that has already done the aggregation, the same reason they use one for multi-supplier travel inventory in other categories.
Who Uses a Tours and Activities API
The buyers of activities APIs are broader than travel companies. Any business that knows where and when its customer will be can sell them something to do there.
- OTAs and travel apps. They offer tours and tickets right after a flight or hotel booking, using the city, dates and travellers they already hold. The activity becomes a second product on a booking that already exists.
- Banks and fintech apps. A travel section in a banking or payments app can sell experiences to cardholders, either as a paid product or as part of a benefits programme.
- Loyalty programmes and reward catalogues. Points can be redeemed for attraction tickets and tours, which are often easier to fulfil than flights and appeal to members who are not planning a trip.
- Super-apps and digital wallets. Apps that already handle payments and identity can add experiences as one more service in the same account.
- Curated experiences marketplaces. Businesses that build their own storefront for a niche, such as food tours or adventure travel, use an API for inventory while they own the curation and the brand.
- Tour operators. An operator that sells its own tours can add third-party activities to extend its range without contracting new suppliers.
- Corporate and event platforms. Platforms that organise trips or events can add team activities and local experiences to an itinerary.
What these buyers share is ownership of the customer. The API supplies inventory and confirmations; the business keeps the storefront, the price and the relationship.
Common Challenges With a Tours and Activities API
Activities are rewarding to sell, but they have pitfalls that hotels and flights do not. Knowing them before you build saves rework.
1. Real-time availability
A popular slot can sell out quickly. You need live availability at the moment of booking, not a cached copy from earlier in the day. Stale data leads to failed bookings and disappointed customers.
2. Time-slot inventory
A boat tour might run at 9:00, 13:00 and 17:00, each with its own capacity. Your system has to treat each slot as its own product for availability and display, not just the day.
3. Vouchers and redemption
The booking is not the end. Some venues scan a QR code, some need a printed voucher, some check a name on a list at a meeting point. Your confirmation page and email must show exactly what the traveller needs and where to go.
4. Cancellation rules
Free-cancellation windows differ by product and are often short, such as 24 or 48 hours before the start. Show the rule from the API response at checkout and in the confirmation, and make sure your own refund process follows it.
5. Localisation
Activities are deeply local, and travellers come from many countries. Descriptions, languages and meeting points need to be clear in the customer’s language, which is why multilingual content in the API response matters.
6. Uneven data quality
Small operators do not always provide rich data. Photos may be few and descriptions short. An aggregating API helps by normalising the content, but test it in your own top destinations before you rely on it.
How to Choose a Tours and Activities API
Most activity APIs look similar in a demo. These checks separate them.
| Check | What to ask |
|---|---|
| Scope | Tours, attractions, theme parks and day trips, or only one of them? |
| Coverage | How many bookable products in your customers’ top five destinations? |
| Live data | Is availability checked live at booking, per date and time slot? |
| Participant pricing | Are adult, child and group prices returned for each option? |
| Confirmation | Is the confirmation type returned per product, before the customer pays? |
| Policies | Are cancellation rules and inclusions structured in the response? |
| Languages | Which content languages are available for your markets? |
| One integration | Are activities in the same API and schema as your flights and hotels? |
| Pricing model | Commission, net rate or a flat fee per booking? |
The last two checks have the biggest long-term effect. A separate activities integration is a second system to maintain, and a percentage fee grows with every price increase in your catalogue.
What a Tours and Activities API Costs
Activity providers charge in a few common ways. Compare the model first, then the numbers at your expected volume.
| Model | How it works | What to watch |
|---|---|---|
| Commission | You or the provider keep a percentage of each booking | Your cost or margin moves with the ticket price |
| Net rate | You buy at a net price and set your own selling price | You carry the pricing decision and the margin |
| Flat fee per booking | A fixed amount per booking on top of the net price | Predictable, and does not grow with the ticket price |
| Subscription | A fixed monthly fee | Pays off only at steady volume |
On Tripgic, activities sit under “all other products”: the supplier’s net price plus a flat fee per booking, never a percentage, after a one-time plan activation. Which plans include activities, and the figures, are on the pricing page.
What to Launch First: A Plan for the Activities Category
Launching every activity in every city on day one spreads a small team too thin. A staged launch proves the flow and the demand first.
Start with your customers’ top destinations. Look at where your existing bookings go, take the top five cities, and launch activities there first. Coverage that is deep in five cities sells better than coverage that is thin in five hundred.
Start with simple products. Attraction tickets and fixed-time tours are the easiest to sell: one date, one slot, clear participant prices. Products that confirm on request, or that need pickup details from the traveller, can follow once the basic flow works.
Place the offer where the trip is already known. The best moments to show activities are the booking confirmation page, the confirmation email and a pre-trip message a few days before travel. At each of those points you already know the city, the dates and the number of travellers, so the search can be pre-filled.
Measure three numbers from the first week. The share of trips that add an activity, the share of activity bookings cancelled, and the share of searches that end with no available slot. The first tells you whether the offer works, the second whether your policies are clear, and the third whether coverage is deep enough in your cities.
Activities for Travellers From the Middle East and Asia
If your customers travel from the Gulf or South-East Asia, a few details matter more than elsewhere. Family travel is common, so child and group pricing must be clear on every product. Languages matter, so check that descriptions are available in the languages your customers read. And local peaks, from school holidays to religious holidays, move demand sharply, so test availability in a peak week as well as an average one. Our guides to the UAE and Saudi Arabia cover those markets in more depth.
Tripgic Activities & Tours API: What You Get
Tripgic is a B2B travel API, and its Activities & Tours API sells tours, attractions, theme-park tickets and local experiences worldwide. Here is what it returns, from Tripgic’s own pages:
- A global catalogue. Tours, attractions, theme parks, day trips and tickets, searchable by category, destination and date.
- Real-time availability. Live availability and pricing, with date and time-slot selection for each product.
- Participant pricing. Adult, child and group price tiers for each option.
- Instant confirmation where supported. Many products confirm instantly with a mobile voucher or e-ticket, and the confirmation type is returned with each product.
- Rich, multilingual content. Descriptions and imagery in multiple languages, with meeting-point and pickup details.
- Clear policies. Cancellation policies and inclusions returned in the response, ready to show at checkout.
- One schema with the rest of the API. Activities follow the same normalised JSON as flights, hotels and transfers, so you book them in the same session as the trip. The documentation lists the activity endpoints with code samples in PHP, Node.js and Python.
- More than activities. The same integration sells flights from GDS, NDC and 100+ low-cost carriers, 2M+ hotel properties, transfers, tour packages, rail, eSIM and visas: 73 endpoints across 8 product families.
- Your brand, your customer. You own the storefront, the brand and the customer, and your customers pay you, never Tripgic.
The sample on Tripgic’s page is a desert safari in Dubai, priced per adult and per child with a mobile voucher, which is a typical first product for a platform selling to Gulf travellers.
How to Connect: Five Steps
Tripgic’s own page lists the path from first call to production:
- Book a kick-off call and get sandbox credentials at no charge.
- Search the catalogue by destination, category and date.
- Check live availability and per-participant pricing for the chosen option and time slot.
- Book and hand the customer the voucher or e-ticket; the confirmation type is returned with each product.
- Show the cancellation policy from the response, test end to end, then switch to production credentials.
Activation of a live plan usually takes 3–5 business days, so start the commercial steps while you build. Test four cases before you go live: a slot that sells out between search and booking, a child participant, a cancellation inside the free window, and a product that confirms on request rather than instantly.
Final Thoughts
A tours and activities API turns a fragmented, local category into one product your platform can sell next to flights and hotels. The hard parts are live time-slot availability, per-participant pricing, vouchers and cancellation rules, and a good API handles all four in its response.
Choose on scope, coverage in your own destinations and whether activities live in the same integration as the rest of your travel products. Activities are one of several products a traveller adds to a trip; mobile data is another, and our eSIM API guide shows how to sell it in the same checkout.
Tripgic sells tours, attractions and tickets worldwide through the same API as its flights and hotels. Book a kick-off call to get free sandbox access.
Mohammad Fahim





