Eventim Scraper - DE Events, Dates and Tickets

Scrape the CTS Eventim catalogue (Europe's largest ticket shop): concerts, festivals, comedy, classical, sports and leisure events with dates, venues, prices and availability across Germany and the EU.

What it collects

Each event row carries the listing fields plus, with detail fetching on, the full event page fields:

• Identity: event id, product group id, title, event type and status, URL
• Dates: start and end (ISO 8601 with timezone)
• Venue: name and city on every row; street, region, postal code, country and venue URL with detail fetching on
• Tickets: price from, price high, currency, availability, per-tier prices with availability each (detail mode), promoter name
• Taxonomy: categories with parent names, tags
• Detail mode only: description, image, offer validity start, and the venue address fields beyond name and city
• Incremental mode only: changeType (NEW, UPDATED, REAPPEARED, EXPIRED), changedFields, firstSeenAt, lastSeenAt

Sample row (illustrative placeholder values, not a live listing):

{
  "eventId": "00000000",
  "title": "Sample Artist Live at Sample Arena",
  "startDate": "2027-05-01T20:00:00+02:00",
  "venueName": "Sample Arena",
  "venueCity": "Berlin",
  "priceFrom": 49.9,
  "priceCurrency": "EUR",
  "ticketAvailability": "in_stock"
}

Input

Two modes. Search mode queries the catalogue by city, keyword, category, date window and stock flag. URL mode reads pasted Eventim links: event links become single records, city and venue links read that scope. The date window, stock flag and sort order apply in search mode and to pasted city and venue links; keyword, city and category fields apply to search mode only.

• cities: city names, one per line (Berlin, Hamburg, Munich). Each city is one catalogue scope. Empty searches all cities.
• query: optional keyword (artist, event or venue name).
• categories: for example Concerts, Comedy, Classical, Sports. Each category multiplies the city scopes.
• dateFrom, dateTo: YYYY-MM-DD bounds on the event date.
• inStockOnly: only events whose tickets are currently bookable.
• sort: DateAsc (default), DateDesc, NameAsc, NameDesc, Rating, Recommendation.
• urls: event links (read as single records), city and venue links (read that city's catalogue scope). Event links are read through the detail lane and bill the detail surcharge each, even when Fetch event details is off.
• fetchDetails: off by default. Reads each event's own page to add the description, image, the venue address beyond name and city, price span and per-tier prices. Detail pages need the slower alternate connection (about 16 seconds per event), so enable it only when you need those fields. Adds a per-event surcharge.
• maxItems: stop after this many events (default 20, 0 means no limit).
• maxPages: upper bound on city and category scopes walked (default 0, no limit).

Coverage note: the catalogue API serves the first 50 matches per filter combination and ignores deeper paging, so very large cities return the soonest 50 per scope. Combine cities with categories and date windows to cover more of the catalogue. With several scopes and a Max items cap, the cap is split evenly across the scopes, so each city contributes its share rather than the run returning the newest events globally.

Resume and recurring updates

• resumeFromRunId: paste a previous run or dataset id to continue a large pull without returning events already collected there.
• incrementalMode: turn on for scheduled monitoring. The first run marks every event NEW. Later runs return only NEW, UPDATED and REAPPEARED events unless emitUnchanged or emitExpired are also on (both return and bill extra rows). State is keyed per search setup, or per stateKey when you name the campaign. EXPIRED rows are only produced after a run that finished every scope cleanly.

Send results into your apps (MCP connectors)

• mcpConnectors: connector ids to pipe results into (optional).
• notionParentPageUrl: parent page for the Notion export.
• maxNotifyListings: cap per connector per run (default 50, dataset unaffected).

Connection

proxyConfiguration: Apify Proxy settings. The default (datacenter) works on every plan and serves the catalogue. Event detail pages refuse ordinary connections, so detail reads escalate to the result-unblocking lane automatically (never for runs on custom proxies). Set the environment variable EVENTIM_ALTERNATE_CONNECTION=0 to disable that lane.

Cost

Pay per event pricing: one event record charge per returned row, one actor start charge per run, plus one detail enrichment charge per event whose detail page was read (fetchDetails on, or pasted event links). Suppressed unchanged rows in incremental mode are fetched but never billed.

Limitations

• Detail reads take about 16 seconds each through the alternate lane; a large fetchDetails run can take several minutes.
• Pasted search-page (/search/) links are not readable scopes; use a city or venue link instead.
• The actor reads the English (/en/) catalogue paths.

Independent tool, not affiliated with CTS Eventim. Collects only publicly available catalogue data. Use responsibly and in line with the site terms.