Fever Event Scraper

Browse Fever events and experiences by city, category or keyword, or paste Fever URLs. Every row carries the event identity, the from-price with its currency, the venue, the date range and the rating pair from the listing page itself. The per-record extras (description, venue address with coordinates, categories, session dates and ticket availability) are one toggle away.

Modes

• Browse by city: walk one or more city catalogues (new-york, london, madrid, paris, milan, sao-paulo, and more), optionally narrowed to one category (candlelight, music-events, exhibitions, food) and one keyword. City pages render their catalogue inline in one read; category pages serve a capped window per grid (48 plans) with the rest behind the site's Load more control, and the run says so ("Partial results: ...") instead of pretending the window is the whole catalogue. Max items is the single cap on a run.
• Paste Fever URLs: event pages (https://feverup.com/m/653922) return that single event in full; city pages (https://feverup.com/en/new-york) and category pages (https://feverup.com/en/london/candlelight) are read like a search, the pasted URL deciding its own scope.

Inputs

• cities: city slugs to browse (search mode). Defaults to New York.
• locale: site language prefix (en, es, fr, it, pt, de). Defaults to en.
• category: optional category slug applied to every city walk (search mode).
• query: optional keyword kept against the event title and categories (search mode).
• urls: Fever URLs to process (URL mode).
• minPrice, maxPrice: keep only events whose from-price honours the bound, in the row's own currency. Every walk in both modes; a pasted event URL is the exception and returns that single event in full.
• fetchDetails: fetch each event's page for the description, venue address with coordinates, categories, session dates and ticket availability. Charged once per record. Leave off for a fast crawl.
• maxItems: the single cap on a run (default 20, 0 for unlimited).
• resumeFromRunId, incrementalMode, stateKey, emitUnchanged, emitExpired: resume one interrupted run, or monitor the same search on a schedule and receive only NEW, UPDATED, REAPPEARED (and optionally EXPIRED) rows.
• proxy: leave the default pool unless a run reports it could not read results.

Output

Each dataset row is one event:

Field	Source
recordId, eventId, url, title	listing card
citySlug, locale, category	walk scope
priceFrom, priceText, originalPrice, onSale, discountPercent, currency, priceType	listing card
startDate, endDate, sessionDate, venueName, rating, ratingCount, isNew, imageUrl	listing card
description, venueAddress, latitude, longitude, categories, firstSessionDate, lastSessionDate, ticketsAvailable, sessionsText	event page (Fetch event details)
changeType, changedFields, firstSeenAt, lastSeenAt	incremental mode

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

{
  "recordId": "000000",
  "title": "Sample Candlelight Concert",
  "citySlug": "new-york",
  "priceFrom": 25.0,
  "currency": "USD",
  "venueName": "Sample Hall",
  "startDate": "2026-10-01T19:00:00-04:00",
  "url": "https://feverup.com/m/000000"
}

Send results into your apps (MCP connectors)

Results can be piped into the apps you already use through Model Context Protocol (MCP) connectors, as an optional side channel. This never changes the dataset output.

• mcpConnectors: authorize a connector under Apify, Settings, API & Integrations, then select it here. Notion receives a page per record; other connectors receive a best-effort write or digest. Each connector gets a condensed summary per record; the complete record always stays in the dataset.
• notionParentPageUrl: the Notion page under which record pages are created. Required for the Notion connector, ignored by the others.
• maxNotifyListings: cap on records written to each connector per run.

Compute

This actor reads pages over plain HTTP; 512 MB of memory is the default and is plenty. A minimal run finishes in well under a minute.

Notes and limits

• City and category pages are complete single reads; a run stops at Max items, never at a page bound.
• Prices are quoted in each event's own currency (USD in New York, GBP in London, and so on); the price bounds compare against the row currency.
• Rating counts drift as reviews accumulate, so they never mark a row UPDATED on their own in incremental mode; price moves, venue changes and date changes do.