Tiqets Attractions & Tickets Scraper

Turn public Tiqets attraction and product pages into structured ticket inventory.

Extract ticket names, Tiqets product IDs, prices, currencies, discounts, availability, next dates, product types, ratings, bundle composition, URLs, and optional public review samples.

Use the results for recurring OTA price monitoring, attraction benchmarking, affiliate catalog updates, destination research, and travel-market analysis.

What does Tiqets Attractions & Tickets Scraper do?

The Actor accepts direct public Tiqets attraction or ticket product URLs.

For attraction pages, it extracts the current ticket offering cards and optional bundle cards.

For direct product pages, it returns the structured product record.

Each output row is designed for analysis and export:

• 🎟️ Tiqets product, product-group, venue, or bundle ID
• 🏛️ Parent attraction name and URL
• 💶 Current price and source currency
• 🏷️ Original price and discount percentage when public
• 📅 Availability and next available date
• 🧭 Location and product-type labels
• ⭐ Rating and review count
• 🔗 Canonical product URL
• 🧩 Bundle component product IDs
• 💬 Optional embedded public review sample
• 🕒 Extraction timestamp and source URL

The scraper uses anonymous HTTP pages rather than browser automation, keeping runs fast and predictable.

Who is it for?

Online travel agencies

Create normalized Tiqets inventory snapshots for destination coverage, product matching, and supplier comparisons.

Attraction operators

Track how nearby or competing attractions package tickets, guided tours, city passes, and bundles.

Travel-market analysts

Compare ticket price ranges, rating volume, availability, discounting, and product mix across attractions.

Affiliates and publishers

Refresh ticket links and public offer metadata before updating destination guides or recommendation pages.

Destination marketing teams

Build recurring attraction catalogs for research dashboards and tourism planning.

Data engineers

Feed structured Tiqets ticket data into warehouses, spreadsheets, webhooks, APIs, or scheduled workflows.

Why use this Tiqets scraper?

Manual ticket monitoring is slow and difficult to repeat.

Tiqets pages can expose several offer types, dates, discounts, and bundle relationships on one attraction page.

This Actor normalizes those fields into stable dataset columns.

Benefits include:

• ✅ No Tiqets login required for the supported public scope
• ✅ Direct attraction and product URL support
• ✅ Typed numbers, booleans, arrays, dates, and URLs
• ✅ Global output limit for predictable jobs
• ✅ Duplicate suppression across overlapping inputs
• ✅ Optional public review samples without full review crawling
• ✅ Optional Apify Proxy configuration for geography or rate-limit recovery
• ✅ JSON, CSV, Excel, XML, RSS, and API exports through Apify datasets

What Tiqets data can you extract?

Field	Type	Meaning
recordType	string	offering, bundle, or attraction fallback
entityId	number	Public Tiqets entity ID
entityType	string	Product, product group, bundle, or venue
name	string	Ticket, bundle, or attraction name
description	string	Public offering description
url	string	Canonical or source-derived Tiqets URL
images	array	Public image URLs
attractionId	number	Parent attraction/venue ID
attractionName	string	Parent attraction name
attractionUrl	string	Parent attraction URL
location	string	Venue or location label
price	number	Current public price
originalPrice	number	Price before a public bundle discount
currency	string	Source currency, such as EUR
discountPercent	number	Public discount percentage
availability	string	Structured availability status
isAvailableOnBookingDate	boolean	Availability flag exposed by Tiqets
nextAvailableDate	string	Next public date in ISO format
productTypes	array	Labels such as guided_tour
isTiqetsChoice	boolean	Public Tiqets Choice flag
checkoutDisabled	boolean	Public checkout-disabled flag
rating	number	Public aggregate rating
reviewCount	number	Public rating/review count
bundleProductIds	array	Product IDs included in a bundle
reviews	array	Optional embedded public review sample
sourceUrl	string	Input URL used for extraction
scrapedAt	string	UTC extraction timestamp

Missing fields are omitted rather than filled with misleading values.

How to scrape Tiqets attractions and tickets

1. Open the Actor input page.
2. Add one or more public Tiqets attraction or product URLs.
3. Choose a low maxItems value for your first run.
4. Decide whether to include bundles.
5. Enable public review samples only when needed.
6. Leave proxy use disabled unless your scale or geography requires it.
7. Start the run.
8. Review the Tiqets ticket inventory dataset view.
9. Export to JSON, CSV, Excel, or your downstream integration.
10. Schedule the Actor when you need recurring snapshots.

A useful first run is the prefilled Louvre attraction example with ten records.

Input

{
  "startUrls": [
    {
      "url": "https://www.tiqets.com/en/louvre-museum-tickets-l124297/?exp_v_new_availabilities=0"
    }
  ],
  "maxItems": 10,
  "includeBundles": true,
  "includeReviews": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

startUrls

Required list of direct public Tiqets attraction, venue, or product URLs.

URLs from locale paths such as /en/ are accepted.

Only tiqets.com hosts are allowed.

maxItems

Global record cap across every input URL.

The default is 25 and the prefill is 10.

The minimum is 1 and the maximum is 10,000.

includeBundles

When enabled, bundle cards include public bundle IDs, EUR prices, discounts, ratings, and component product IDs.

includeReviews

When enabled, each applicable record contains the small review sample already embedded in public structured page data.

This option does not paginate a full review archive.

proxyConfiguration

Optional Apify Proxy or custom proxy configuration.

Direct HTTP is sufficient for the prefilled example.

Output example

{
  "recordType": "offering",
  "entityId": 1109119,
  "entityType": "product",
  "name": "Louvre Museum: Dedicated Entry + Small Group Guided Tour",
  "url": "https://www.tiqets.com/en/things-to-do-in-paris-c66746/tickets-for-louvre-museum-dedicated-entry-small-group-guided-tour-p1109119/",
  "attractionId": 124297,
  "attractionName": "Tickets for Louvre Museum",
  "attractionUrl": "https://www.tiqets.com/en/louvre-museum-tickets-l124297/",
  "location": "Louvre Museum",
  "price": 100,
  "currency": "EUR",
  "discountPercent": 0,
  "availability": "InStock",
  "nextAvailableDate": "2026-07-20",
  "productTypes": ["guided_tour"],
  "isTiqetsChoice": true,
  "rating": 4.5,
  "reviewCount": 234,
  "sourceUrl": "https://www.tiqets.com/en/louvre-museum-tickets-l124297/",
  "scrapedAt": "2026-07-20T00:00:00.000Z"
}

Live values change as Tiqets updates prices, inventory, ratings, and dates.

How much does it cost to scrape Tiqets tickets?

This Actor uses pay-per-event pricing.

A one-time Run started event costs $0.005 per run.

An Item extracted event is charged for each saved offering, bundle, or attraction record.

Apify plan tier	Price per ticket record
FREE	$0.00010879
BRONZE	$0.000094602
SILVER	$0.000073789
GOLD	$0.000056761
PLATINUM	$0.000037841
DIAMOND	$0.000026488

Subscription tiers receive automatic per-record discounts. Platform prices are authoritative if this documentation and the run page ever differ.

To estimate a job:

1. Count the attraction URLs you want to monitor.
2. Estimate the ticket and bundle cards per attraction.
3. Set maxItems to a safe upper bound.
4. Multiply expected records by your displayed tier price.
5. Add the displayed one-time start price.

Start with ten records to validate the workflow cheaply.

Price and availability monitoring workflow

Run the same attraction URL list on a schedule.

Store each dataset with its scrapedAt value.

Join snapshots by entityId and recordType.

Compare:

• Current and original price
• Currency
• Discount percentage
• Availability status
• Next available date
• Rating and review count
• Product type mix
• Bundle component IDs

Send changed rows to a webhook, database, spreadsheet, or alerting service.

Working with bundles

Bundle rows use recordType: "bundle".

They include a stable public bundle ID when available.

bundleProductIds lists the public Tiqets product IDs contained in the bundle.

originalPrice and price support discount analysis.

Bundle names may be ID-based when the public page exposes structured pricing but no standalone bundle title.

Disable includeBundles when you only need bookable offering cards.

Reviews and ratings

Ratings and review counts are extracted when present in public structured data.

Set includeReviews to true to attach Tiqets' embedded public review sample.

Each review can contain:

• Author name
• Publication date
• Review text
• Rating value

Do not treat this sample as a complete review archive.

For reputation monitoring, compare aggregate rating and review count across scheduled snapshots.

Data quality and deduplication

Records are deduplicated by record type and Tiqets entity ID or URL.

Numbers are emitted as numbers rather than formatted text.

Boolean source flags remain booleans.

Dates use the source ISO date when available.

Currency is preserved from the source and is not converted.

The Actor fails rather than returning a successful empty dataset when every page cannot be extracted.

Individual broken URLs are logged while other supplied URLs continue.

Tips for reliable Tiqets extraction

• Use direct attraction or product URLs instead of general home pages.
• Keep the original locale path when you care about locale-specific output.
• Preserve currency beside every stored price.
• Use a low maxItems while validating a new URL list.
• Disable reviews when you only need inventory changes.
• Disable bundles when your downstream model accepts products only.
• Schedule conservatively rather than polling continuously.
• Configure a proxy only after direct HTTP shows a geography or throttling need.
• Check run logs for individual pages that changed structure.
• Keep sourceUrl and scrapedAt in every warehouse table.

Integrations

Google Sheets

Export each run as CSV or connect through Make/Zapier to append price snapshots.

Webhooks

Use an Apify run-finished webhook to trigger inventory diffing after each scheduled run.

Data warehouses

Load JSON dataset items into BigQuery, Snowflake, Redshift, or PostgreSQL.

Business intelligence

Build attraction price, availability, product mix, and rating dashboards in Looker Studio, Power BI, or Tableau.

AI workflows

Send descriptions and review samples to an LLM for product categorization, summary, or sentiment analysis.

Affiliate catalogs

Refresh public product URLs and ticket metadata before publishing destination pages.

Use the Actor with the Apify API

Replace YOUR_TOKEN with an Apify API token.

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/tiqets-attractions-tickets-scraper').call({
  startUrls: [
    { url: 'https://www.tiqets.com/en/louvre-museum-tickets-l124297/' }
  ],
  maxItems: 10,
  includeBundles: true,
  includeReviews: false
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("automation-lab/tiqets-attractions-tickets-scraper").call(run_input={
    "startUrls": [
        {"url": "https://www.tiqets.com/en/louvre-museum-tickets-l124297/"}
    ],
    "maxItems": 10,
    "includeBundles": True,
    "includeReviews": False,
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~tiqets-attractions-tickets-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "startUrls": [{
      "url": "https://www.tiqets.com/en/louvre-museum-tickets-l124297/"
    }],
    "maxItems": 10,
    "includeBundles": true,
    "includeReviews": false
  }'

Use Tiqets data with MCP

Connect the Actor to AI assistants through Apify MCP.

MCP endpoint:

https://mcp.apify.com/?tools=automation-lab/tiqets-attractions-tickets-scraper

Claude Code

claude mcp add --transport http apify \
  "https://mcp.apify.com/?tools=automation-lab/tiqets-attractions-tickets-scraper"

Claude Desktop

Add an HTTP MCP server using the same endpoint and your Apify authentication:

{
  "mcpServers": {
    "tiqets-tickets": {
      "url": "https://mcp.apify.com/?tools=automation-lab/tiqets-attractions-tickets-scraper"
    }
  }
}

Cursor

Open Cursor MCP settings and add the same mcpServers configuration:

{
  "mcpServers": {
    "tiqets-tickets": {
      "url": "https://mcp.apify.com/?tools=automation-lab/tiqets-attractions-tickets-scraper"
    }
  }
}

VS Code

Add an MCP server to your workspace or user configuration:

{
  "mcpServers": {
    "tiqets-tickets": {
      "url": "https://mcp.apify.com/?tools=automation-lab/tiqets-attractions-tickets-scraper"
    }
  }
}

Example prompts:

• “Extract the current ticket prices and next dates for these Tiqets attractions.”
• “Compare discounted bundles and standard offerings for this museum.”
• “Create a CSV-ready table of product IDs, ratings, prices, and currencies.”
• “Find price and availability changes between these two dataset snapshots.”

Scheduling recurring runs

Open Schedules in the Apify Console.

Choose the Actor and save your attraction URL input.

Select an interval appropriate for the workflow:

• Hourly for time-sensitive inventory research
• Daily for competitor price monitoring
• Weekly for destination catalog maintenance

Use webhooks to notify downstream systems only after successful runs.

Retain prior datasets when you need historical comparisons.

Legal and responsible use

This Actor extracts data exposed on public Tiqets pages.

You are responsible for complying with applicable laws, contracts, website terms, database rights, privacy rules, and fair-use requirements.

Do not use the Actor to overload Tiqets or evade access controls.

Use reasonable schedules and output limits.

Do not infer sensitive personal information from review content.

Review your jurisdiction and use case before redistributing collected data.

Troubleshooting

Why did my run reject a URL?

The Actor accepts only HTTP(S) URLs on tiqets.com or its subdomains.

Use a direct public attraction, venue, or product page.

Why is a price missing?

Tiqets may expose a product without a current public price for the selected locale or inventory state.

Missing values are omitted instead of guessed.

Why are there fewer rows than maxItems?

maxItems is a cap, not a requested minimum.

The page may contain fewer public ticket or bundle records.

Why is a bundle name based on its ID?

Some pages expose structured bundle IDs, prices, and component products without a standalone public bundle title in the same payload.

Why are reviews incomplete?

The option captures only the small public JSON-LD sample.

It intentionally does not claim to provide full review pagination.

What if Tiqets rate-limits my larger job?

Reduce schedule frequency and concurrency first.

Then configure Apify Proxy for geography or rate-limit recovery.

FAQ

Does this Actor require a Tiqets account?

No account is required for the supported public page scope.

Can it scrape several attractions in one run?

Yes. Add several direct URLs to startUrls; maxItems applies globally.

Does it convert currencies?

No. It preserves the source currency so price observations remain auditable.

Can it extract direct ticket product pages?

Yes. Direct public Tiqets product URLs are supported.

Can it monitor availability?

Yes. Save scheduled snapshots and compare availability, isAvailableOnBookingDate, and nextAvailableDate.

Does it use a browser?

No. The supported scope is extracted from server-rendered structured HTML over HTTP.

Can I export results to Excel?

Yes. Apify datasets support Excel and CSV exports in addition to JSON and API access.

Related scrapers

Combine this Actor with other travel and location tools from Automation Lab:

• Google Maps Scraper for attraction discovery and local business context
• Booking Scraper for nearby accommodation market research
• Tripadvisor Scraper for destination and review comparisons

Related actors may have different inputs, pricing, and data scopes.

Support

When reporting a problem, include:

• The Tiqets URL that failed
• A link to the Apify run
• The relevant log message
• The expected record or field
• Whether proxy use was enabled
• Whether the failure is repeatable

Do not post API tokens or private credentials.

Public page structures change over time, so precise examples help diagnose extraction issues quickly.