Tour & Activity
Connect experience marketplaces, attraction ticket distributors and tour operator booking systems to the travel platform you already run.
Guru TechnoLabs builds tour and activity API integration for OTAs, travel agencies, tour operators and DMCs. We connect the experience suppliers you choose, bring their tours, tickets and excursions into one catalogue, and run availability, booking, vouchers and cancellations through your existing website, app, agent portal and back office. You keep your platform and your supplier agreements. We build and maintain the connections.
Tour and activity API integration connects a travel company's booking system to experience suppliers' APIs, so it can show live availability, price each traveller, book tours and attraction tickets, deliver vouchers and handle cancellations automatically. The suppliers can be experience marketplaces, attraction ticket distributors, B2B wholesalers or the booking systems tour operators use to run their own departures.
Activities work differently from hotels or flights, which is why they need their own integration design:
Time slots and capacity. A walking tour may run at 09:30, 14:00 and 17:30, each with its own places left and a cut-off before the start.
Price per traveller type. Adults, children, infants and seniors are priced separately, with age bands that differ by product. Private tours are often priced per group.
Booking questions. Many activities need a pickup hotel, guide language, passport number or even height and weight before the supplier accepts the booking.
Vouchers and tickets. The traveller shows a voucher, QR code or e-ticket on the day, so the supplier's fulfilment details become part of your confirmation.
Most travel companies reach for an activity API when experiences have outgrown affiliate links and manual bookings. If several of these sound familiar, an integration is the next step.
Activities sell only through affiliate links. Customers leave your site to book, so you have no control over price, margin, customer data or service.
Excursions are booked by email or phone. Your team checks supplier sites, confirms by email and retypes details into itineraries.
Sold-out slots get sold anyway. Availability on your site lags behind the supplier, and the customer finds out after paying.
Vouchers go out by hand. Staff forward tickets and meeting-point instructions one booking at a time.
Your own tours live in a separate system. Departures you operate, or local partners' tours, never appear next to marketplace inventory.
Supplier changes arrive too late. A weather cancellation or a new start time reaches your customer after it reaches your inbox.
We cover the full activity connection, from the first supplier API to the voucher in your customer's inbox and the booking record in your back office.
Start with one supplier or connect several. Each supplier gets its own connector, and all of them feed one internal product model, so your platform works with the same structure whether a tour comes from a marketplace, a ticketing distributor or a local operator’s booking system. Adding a new supplier later means adding a connector, not rebuilding your booking flow.
The same city tour or museum ticket is often sold by more than one supplier, each with its own title, photos, categories and traveller types. We match products, meeting points and categories across sources, so customers see one listing and you decide which supplier to sell it from.
Customers see the dates, start times and places that are actually left. We handle real-time slots, freesale products that confirm on booking, on-request products that need supplier approval, and cut-off times before the start. Availability is checked again just before payment, because another seller may have taken the last places.
Prices are built per traveller from each product’s own age bands, or per group and per vehicle for private tours. We apply your markups and commissions by supplier, channel or agent group, convert currencies, and show the total before checkout.
Customers book on your site in the steps each supplier requires, often reserve first and confirm after payment. Each product’s required questions, such as pickup hotel, guide language or passport number, appear in your checkout and travel with the booking, so the supplier has them before the day. Instant and on-request confirmations are tracked separately so customers know where they stand.
Once the supplier confirms, its voucher, QR code or e-ticket is returned through the API and sent with your confirmation, along with the meeting point and what to bring. Where a supplier reports redemption or check-in status, it flows back to your booking record.
Customers see each product’s cancellation policy before they pay, and cancellations go back to the supplier automatically. Changes the supplier makes, such as a weather cancellation or a moved start time, are picked up through webhooks or scheduled checks and passed to your team and customer, with refund status recorded.
Tour operators and DMCs often sell their own departures and local partners’ tours next to marketplace stock. We connect your own tours, and operators who run systems such as Rezdy, Bókun or FareHarbor, into the same search as your API suppliers, each with its own pricing rules.
Experience suppliers grant API access under their own partner programmes, and the access level they approve decides what you can build. You hold the agreement with each supplier; we build the integration and take it through certification.
Marketplaces sell tours and activities from thousands of operators and open their catalogue to approved partners. Access is tiered, and the tier decides whether customers book on your site or are sent to the marketplace.
Ticketing distributors focus on museums, landmarks, theme parks and other admission-based products, with timed or open-date tickets and e-ticket delivery.
B2B distributors curate tours, tickets and transfers for the travel trade under wholesale agreements.
Many operators run their tours on reservation software that lets approved resellers book directly into it. Connecting these systems lets you sell local operators' inventory without a marketplace in between.
OCTO (Open Connectivity for Tours, Activities and Attractions) is an open API specification for the experiences industry. Booking systems that implement it share the same core calls: supplier, products, availability, reserve, confirm and cancel, with optional capabilities such as pricing and content. Building to OCTO once lets you reach several booking systems through one connector pattern, with smaller adjustments per supplier rather than a new build each time.
A tour and activity booking API follows the same sequence across most suppliers: load products, check availability, reserve, confirm, deliver the voucher, then manage changes. Method names differ by supplier, but the steps match.
Load products. Tour and ticket content, such as descriptions, photos, meeting points, inclusions and traveller types, is imported and stored in your database, then refreshed on the schedule each supplier sets.
Check availability. The customer picks a date; the API returns open dates, start times and places left for each slot.
Price the booking. Travellers are entered by type and the total is calculated from the product's age bands, plus your markup.
Reserve. The chosen slot is held with the supplier for a short time, so the places are not sold elsewhere during checkout.
Answer booking questions. Pickup location, guide language and any per-traveller details the product requires are collected.
Confirm and pay. Payment is taken under your integration model and the booking is confirmed with the supplier, instantly or on request.
Deliver the voucher. The supplier's voucher, QR code or e-ticket is sent with your confirmation.
Manage changes. Customer cancellations, supplier changes and refunds flow between your platform and the supplier.
The integration model decides who takes payment, who supports the traveller and who handles refunds, and suppliers approve each model separately. We help you choose the right one per supplier before any build starts.
| Affiliate (redirect) | On-site booking, supplier as merchant | Merchant of record | |
|---|---|---|---|
| Where the customer pays | On the supplier's site | On your site, through the supplier's payment flow | On your site, through your payment gateway |
| Who supports the traveller | Supplier | Supplier | You |
| Who handles refunds | Supplier | Supplier | You, with the supplier |
| Your control over pricing and data | Low | Medium | High |
| Access requirements | Usually self-service | Approval and certification | Approval, certification and proof you can run payments and service |
| Typical examples | Viator Basic access; Headout and Tiqets affiliates | Viator Full + Booking; Musement affiliate full integration | Viator Merchant; Musement merchant |
| Integration effort | Lowest | Medium | Highest |
You don't need a new platform to sell experiences. We add the activity layer to the system you already run, through its APIs or database, and leave live bookings, customer history and team processes as they are. If you don't have a platform yet, we build activity supply into a new booking portal from day one.
Tours and tickets appear in your existing search and checkout, with time-slot pickers, traveller types and booking questions built in. Agents book through your B2B portal at their own rates, and the same activities are bookable inside your travel app.
Every activity booking lands in your records with the supplier reference, voucher, net cost, selling price and margin, synced to your travel CRM and accounting. Payment runs through your gateway or the supplier's, depending on the integration model each supplier approves.
Activities add the most value inside a trip. We package tours and tickets with the flight API integrations and hotel suppliers we connect, so customers book a whole itinerary in one checkout, and add excursions to group itineraries managed in your group travel system.
Most activity integration problems are predictable. We plan for these from the first week, not after launch.
Suppliers set how often product and availability data must be refreshed, and some forbid long caching. We follow each supplier's rules so content stays current without breaching them.
Start times are local to the activity, not the customer. We store and display them correctly and close sales at each product's cut-off.
Each behaves differently at booking. Your checkout and confirmations reflect which one the customer is buying.
Required fields vary by product and traveller. We build forms from the supplier's definitions instead of one fixed checkout.
Suppliers cap requests and some calls are slow. Request scheduling, caching and timeouts keep search fast and within limits.
Some suppliers push booking changes; others must be checked on a schedule. We use whichever each supplier supports so changes are not missed.
Descriptions, policies and prices are pulled in the languages and currencies you sell in, where the supplier provides them.
Payment flows match the integration model, limit PCI DSS scope, and support 3-D Secure for European cards where required.
Booking access usually requires a certification test. We prepare test cases, complete the certification and fix findings before go-live.
Every activity integration follows seven steps, from choosing suppliers to monitored live bookings. Getting the integration model and product model right early saves the most time later.
We review your platform, markets, own tours and target suppliers, and recommend an integration model per supplier.
We help you prepare each partner application and request the access level your model needs. [CONFIRM: extent of onboarding support Guru provides.]
We map each supplier's products, options, traveller types and booking questions to one internal model.
We build a connector per supplier, import catalogue content and set refresh schedules.
Availability, reserve, payment, confirmation and voucher delivery are wired into your front end, CRM and accounting.
We test every path, including sold-out slots, on-request bookings and supplier cancellations, then complete each supplier's certification.
We go live in stages, watch bookings and supplier errors closely, and continue support under a maintenance plan.
We have fulfilled the demands of clients working in different industries. For more details, check what our clients say about us.
Yes. Each supplier issues API access to the travel business under its own partner programme, and decides which products, data and booking rights your account gets. Viator, for example, gives self-service Basic access by default and approves higher levels on request. We help you prepare each application and build to the access level you receive.
In an affiliate integration, the supplier remains the merchant of record: it takes payment, supports the traveller and handles refunds, and you earn commission. In a merchant integration, your business takes payment and provides customer service, which gives you more control over pricing and data but requires supplier approval and the operations to support it.
Yes, if the supplier approves booking access. Viator’s Full + Booking access, Headout’s API Partner type and Tiqets’ Booking API all allow on-site booking, each after approval. Until then, the integration can show live content and availability and hand checkout to the supplier.
Yes. Departures you operate, and local partners’ tours from systems such as Rezdy, Bókun or FareHarbor, can appear in the same search and checkout as marketplace products, each with its own pricing rules.
OCTO (Open Connectivity for Tours, Activities and Attractions) is an open API standard that defines common calls for products, availability, reserve, confirm and cancel. Many booking systems implement it, Bókun among them. We check each of your suppliers during the supply review; where OCTO is supported, connectors are faster to build and maintain.
No. Some return live places per time slot; others sell freely until the supplier closes a date, and some products need the supplier to accept each booking. Cancellation and amendment support also varies, and some suppliers push changes while others must be checked on a schedule. We confirm what each supplier supports before design.
After the supplier confirms, its voucher, QR code or e-ticket comes back through the API. We include it in your confirmation email and booking record, with the meeting point, start time and whether a mobile or printed voucher is accepted.
It depends on the number of suppliers, the access level each approves and their certification steps. As a guide, one supplier integrated into an existing platform takes 4–6 weeks, and three or more suppliers with product mapping take 10–16 weeks. Supplier approval can add time outside our control.
Yes. We integrate activity suppliers into your current website, booking engine, mobile app or agent portal, and connect bookings to your CRM, payments and accounting. Your existing products and live bookings stay as they are.
A white-label product is faster to launch if you have no platform and its supplier list fits your needs. A custom integration suits businesses that already run a platform, need specific suppliers or business rules, or want to own the code and customer journey. We’ll tell you honestly which fits during the supply review.