# Ticketmaster France Ticket Availability Scraper (`soldout/ticketmaster-fr-stock`) Actor Real ticket availability on ticketmaster.fr, per date, per category and per fare - not just the catalogue metadata. - **URL**: https://apify.com/soldout/ticketmaster-fr-stock.md - **Developed by:** [Soldout](https://apify.com/soldout) (community) - **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $15.00 / 1,000 seance priceds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Ticketmaster France — Live Stock by Category ![market](https://img.shields.io/badge/market-France%20only-1f6feb) ![seat counts](https://img.shields.io/badge/seat%20counts-83.6%25%20of%20live%20categories-2ea043) ![fare grid](https://img.shields.io/badge/fare%20grid-not%20in%20Discovery%20API-8957e5) ![per date](https://img.shields.io/badge/per%20date-%240.015-fb8500) > **France only.** This Actor reads `ticketmaster.fr`. The `idmanif` identifier it takes as input belongs to the French site and has no meaning on `ticketmaster.de`, `.co.uk`, `.com` or any other Ticketmaster domain — those run on a different platform. If you need another country, this Actor is not for you. Every other Ticketmaster scraper returns the **catalogue**: name, venue, dates, on-sale times, artists. Most of them wrap the official Discovery API, which is free and public. This one returns what that API does not carry — **whether a given fare, in a given category, on a given date, can actually be bought right now**. ### What you get One record per date (`séance`), with its full fare grid — real output, trimmed to two categories: ```json { "idmanif": "645408", "idseance": 2846127, "date": "2026-10-16T20:00:00.000+02:00", "label": "Vendredi 16 octobre 2026 à 20:00", "available": true, "resaleAvailable": false, "hasPlacesDispo": true, "categories": [ { "code": "0R", "label": "CATEGORIE OR", "priceMin": 79.6, "nbPlaces": 35, "inStock": true, "zones": [ { "idzone": "257", "label": "Porte A", "nbPlaces": 5, "inStock": true, "numbered": true }, { "idzone": "272", "label": "Porte P", "nbPlaces": 12, "inStock": true, "numbered": true }, { "idzone": "277", "label": "Porte U", "nbPlaces": 18, "inStock": true, "numbered": true } ], "tarifs": [ { "idNatCl": 1, "nameNatCl": "TARIF NORMAL", "price": 79.6, "min": 1, "max": 8, "inddispo": true } ] }, { "code": "FX", "label": "FOSSE OR", "priceMin": 69.7, "nbPlaces": 0, "inStock": true, "tarifs": [ { "idNatCl": 1, "nameNatCl": "TARIF NORMAL", "price": 69.7, "min": 1, "max": 8, "inddispo": true } ] } ], "scrapedAt": "2026-09-08T09:12:44.109Z" } ``` The two categories above show both cases: `CATEGORIE OR` has **35 seats left, split across three doors**, while `FOSSE OR` returns `0` yet is on sale — see below. ### Reading the availability fields **`nbPlaces` is the remaining seat count**, and it is populated on **83.6 %** of categories that are on sale — measured over 5 424 live categories, up to 4 069 seats on a single one. When a category carries `zones`, that count is broken down **per entrance door**, which is as close to a live seat map as Ticketmaster publishes. **But `0` does not mean sold out.** On the remaining 16 %, Ticketmaster returns `0` on categories that are perfectly buyable — standing-room blocks especially. Availability is therefore carried by `inddispo`, fare by fare, and that is exactly what `inStock` summarises. Read `inStock` to know *whether* you can buy, `nbPlaces` to know *how much is left* when Ticketmaster says so. `hasPlacesDispo` is Ticketmaster's own header flag for the date. `available` comes from the date list, `resaleAvailable` tells you the official resale is open on that date. A date that could not be read carries `error`, and `blocked: true` if the WAF rejected it rather than the endpoint failing. Those dates are never charged. ### Why this is hard to get elsewhere ticketmaster.fr sits behind DataDome. The fare grid is not in the Discovery API, is not in the page HTML, and does not survive a plain HTTP client — it takes a signed token bound to the exit IP that fetched it. This Actor does not solve any of that itself: it reads a service that holds a warm token cycle shared across all runs, which is why a single date costs a fraction of a cent instead of a full solver call. Measured across the French catalogue: **1.31 dates per event** on average, median 1, maximum 351. ### Input | Field | Type | Default | What it does | |---|---|---|---| | `startUrls` | array | `[]` | Event pages on ticketmaster.fr. Anything containing `/idmanif/` works. | | `idmanifs` | array | `[]` | The bare IDs, if you already hold them. Merged with `startUrls`, deduplicated. | | `concurrency` | integer | `3` | Manifestations queried in parallel. Above 3 you mostly queue behind the shared token cycle. | ### What you pay for | Event | Price | Charged when | |---|---|---| | Actor start | $0.01 | Once per run. | | Seance priced | $0.015 | One date delivered with its fare grid. | Dates that failed are **not** charged. The median event has a single date, so a typical event costs $0.015. If you cap a run with *max cost per run*, delivery stops at the cap instead of handing over the rest for free — the run then ends with a `coverage` record in its key-value store telling you exactly how much of your list was covered. ### Limits France only — see the note at the top. This Actor reads live availability; it does not place orders, hold seats, or bypass queues. # Actor input Schema ## `startUrls` (type: `array`): Event pages on ticketmaster.fr ONLY, for example https://www.ticketmaster.fr/fr/manifestation/-/idmanif/667631. Anything containing /idmanif/ works, and plain numbers are accepted too. URLs from ticketmaster.de, .co.uk, .com or any other country will not resolve. ## `idmanifs` (type: `array`): The bare idmanif values, if you already hold them. Merged with Ticketmaster event URLs, duplicates removed. ## `concurrency` (type: `integer`): How many manifestations are queried in parallel. One manifestation costs one upstream request per date, and the median event has a single date. Raising this past 3 mostly queues work behind the shared token cycle rather than speeding it up. ## Actor input object example ```json { "idmanifs": [], "concurrency": 3 } ``` # Actor output Schema ## `seances` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("soldout/ticketmaster-fr-stock").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("soldout/ticketmaster-fr-stock").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call soldout/ticketmaster-fr-stock --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,soldout/ticketmaster-fr-stock" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/5Czprvl0TEMvuy8eH/builds/gvepNvpVXJ9FySeEQ/openapi.json