Fever Scraper - Events, Prices, Venues & Dates
Pricing
from $1.50 / 1,000 event records
Fever Scraper - Events, Prices, Venues & Dates
Scrape Fever events by city, category, keyword or URL. Extract from-prices, venues, dates and ratings, with optional enrichment for event descriptions, venue addresses and available sessions.
Pricing
from $1.50 / 1,000 event records
Rating
0.0
(0)
Developer
Abot API
Maintained by CommunityActor stats
1
Bookmarked
1
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Fever Scraper: Events, Experiences and Prices by City
Fever Scraper turns feverup.com into a clean events data feed. Browse a city's whole catalogue of immersive experiences, pop-ups, concerts and local events by name, category or keyword, or paste Fever links straight in. Every row carries the event identity, the from-price in its own currency, the venue, the date range and the rating pair from the listing itself. The description, venue address with coordinates, categories, session dates and ticket availability are one toggle away, then export to JSON, CSV or Excel, or pull results straight into your app through the API.
Why This Scraper?
- Two ways to find events. Browse city catalogues by name with an optional category and keyword, or paste any Fever event, city or category link and let the URL decide the scope.
- No page-by-page crawl to get stuck on. A city catalogue page renders its whole feed in one request. A category page can serve only its first window behind the site's Load more control; when that happens the run reports "Partial results" instead of silently under-counting.
- Identity, price and rating on every row. The event title, from-price with its own currency, venue, date range and rating pair come straight from the listing, with no toggle required.
- Event-page depth on demand. Switch on the description, venue address with coordinates, categories, session dates and ticket availability, and the extra fee applies only to the records you actually enrich.
- Built for schedules. Incremental mode returns only new and changed events on repeat runs, and a fully refused run fails loudly instead of quietly returning an empty dataset.
- Keyword and price filters the site itself lacks. Both are applied to what this run actually reads, checked against each event's own currency.
- Wide city coverage. Dozens of cities across several languages, from New York and London to Madrid, Paris, Milan and Sao Paulo.
Use Cases
- Local event guides and newsletters: pull a city's candlelight, music, exhibition or food events with prices and dates for a weekly roundup.
- Price and availability monitoring: schedule incremental mode against one city or category to catch price drops, new sessions or events going on sale.
- Travel and city-guide apps: feed nearby experiences, venues and ratings into your own app or itinerary tool.
- Competitive and market research: track which immersive experiences and pop-ups are launching across cities and how they are priced.
- Ticketing aggregators: build a cross-city catalogue of experiences with venue, price and session data for comparison.
Data You Get
Sample shape: values are illustrative placeholders, not from a live record.
| Field | Example |
|---|---|
recordId | "9000001" |
rowType | "event" |
eventId | "9000001" |
url | "https://feverup.com/m/9000001" |
title | "Sample Concert Evening" |
citySlug | "new-york" |
locale | "en" |
category | "candlelight" |
priceFrom | 25 |
priceText | "From 25.00 USD" |
originalPrice | 30 |
onSale | true |
discountPercent | 16.7 |
currency | "USD" |
startDate | "2026-11-01T19:00:00-04:00" |
endDate | "2026-11-30T21:00:00-04:00" |
venueName | "Sample Hall" |
rating | 4.5 |
ratingCount | 320 |
isNew | false |
description (Fetch event details) | "A candlelit evening of chamber music for all ages." |
venueAddress (Fetch event details) | "100 Sample Street, New York, 10001" |
ticketsAvailable (Fetch event details) | true |
reviews (Fetch event details) | [{"reviewer": "Sample G.", "rating": 5, "date": "2026-10-04T19:55:04+00:00", "text": "Great evening.", "helpfulVotes": 0}] |
changeType (incremental mode) | "UPDATED" |
Every row also carries imageUrl, priceType ("from" on a from-priced event), sessionDate (the specific date a session card matched, on category agenda pages), latitude/longitude and categories (event details toggle), firstSessionDate/lastSessionDate and sessionsText (event details toggle), detailCarriedForward (present and true only when a failed details read was repaired from a previous run's snapshot instead of left blank), scrapedAt, and, in incremental mode, changedFields, firstSeenAt and lastSeenAt.
How to Use
- Pick a mode:
search(browse city catalogues) orurl(paste Fever links). - In search mode, list one or more cities, and optionally a category and a keyword filter; in url mode, paste event, city or category links, each one deciding its own scope.
- Optionally set the price bounds and switch on Fetch event details for the description, venue address, categories, session dates and ticket availability.
- Set Max items to control run size and cost, then click Start.
Browse a city:
{"mode": "search","cities": ["new-york"],"maxItems": 20}
Narrow to a category and a price band:
{"mode": "search","cities": ["new-york"],"category": "candlelight","minPrice": 20,"maxPrice": 60,"maxItems": 20}
Browse a city with full event details:
{"mode": "search","cities": ["london"],"fetchDetails": true,"maxItems": 10}
Paste Fever links (an event and a category):
{"mode": "url","urls": ["https://feverup.com/m/653922","https://feverup.com/en/new-york/candlelight"],"maxItems": 10}
Pasting a single event link returns its full detail fields (description, address, session dates) either way, since that page has to be read to identify the event; the details fee is only added when Fetch event details is switched on.
URL shapes (url mode)
| Shape | Example | Notes |
|---|---|---|
| City catalogue | https://feverup.com/en/new-york | Whole city catalogue. |
| City, www host | https://www.feverup.com/en/london | Same as the plain host. |
| City, other locale | https://feverup.com/es/madrid | Locales en, es, fr, it, pt, de. |
| Category | https://feverup.com/en/new-york/candlelight | Also https://feverup.com/en/london/music-events. |
| Category, trailing slash | https://feverup.com/en/new-york/candlelight/ | Same scope. |
Category with ?page=2 | https://feverup.com/en/new-york/candlelight?page=2 | The site ignores the query, so this is the same scope and is never read as page 2. |
| Event | https://feverup.com/m/653922 | Also with a tracking query such as ?utm_source=x. |
Not supported, each logs a per-URL warning that names the reason and counts as an unresolved URL (never a silent zero): a locale-only page such as https://feverup.com/en, nested category paths such as /en/new-york/candlelight/jazz, and /en/m/ID (use https://feverup.com/m/ID).
The default now scrapes one example per shape. If you switch to url mode and leave the URLs field untouched, the actor reads the example URLs above (a few city and category pages and one event), up to your item limit, instead of nothing.
In search mode, cities and category accept plain names ("New York", "London", "Music Events") and Fever city codes (NYC, LON); Vienna and Washington DC resolve to Fever's own slugs wien and washington. A name that cannot be read fails the run with a clear message.
If you come from another Fever scraper, its input words work too: city (name, slug or code such as LON), queryType (browse is search mode, event reads one event) and id (a numeric event ID, same as pasting https://feverup.com/m/ID; when it is filled only that event is read and Mode and the sample URL list are ignored, unless queryType is browse). Its output names map onto ours: name is title, venue is venueName, price is priceText, numeric_price is priceFrom, cover_image is imageUrl, coordinates are latitude and longitude, start_time and end_time are startDate and endDate, city_code is citySlug, queryType is rowType. The site has no native sort or keyword parameter, so keyword and price filters apply to the rows the run reads.
Run it from your code
Python:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("abotapi/fever-com-scraper").call(run_input={"mode": "search", "cities": ["new-york"], "maxItems": 20})for event in client.dataset(run["defaultDatasetId"]).iterate_items():print(event["title"], event["priceFrom"], event["currency"])
JavaScript:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });const run = await client.actor('abotapi/fever-com-scraper').call({ mode: 'search', cities: ['new-york'], maxItems: 20 });const { items } = await client.dataset(run.defaultDatasetId).listItems();
Or connect it to Make, Zapier, n8n, Google Sheets or webhooks from the Integrations tab.
Resume and recurring updates
- Resume (
resumeFromRunId) continues one interrupted run: paste its run or dataset id and the actor skips every record id already collected there, so you don't pay twice. Every city page and every pasted URL is still read on each run (there is no page-by-page crawl to resume mid-page), so Resume saves the push and the charge for records already collected, not the read itself. A category page may still only reach its first window if the site's Load more control caps it, whether or not Resume is set. - Incremental mode (
incrementalMode) is for running the same search again and again, for example daily. Each record is classifiedNEW,UPDATED(withchangedFields),UNCHANGED(suppressed and not billed unlessemitUnchangedis on),REAPPEAREDorEXPIRED. A record only turnsREAPPEAREDif it was previously marked absent, and that only ever happens after an earlier run hademitExpiredon and completed a full, uncapped, non-resumed scan of every tracked city or category with none of its sources refused;EXPIREDfollows that same rule and is never produced by default. A category page that only served a capped window of its catalogue (behind the site's Load more control) is never treated as a complete scan, so that run skips EXPIRED detection and says so in the log. - Resume and Incremental mode do not mix on a state key that already has tracked records: the run stops with a message asking you to remove Resume or pick a different State key, so a resumed run never seeds a monitoring baseline from a partial dataset.
stateKeynames or shares the stored state. With incremental mode off, output is exactly as before.- What is compared: every returned field (price from, original price, on-sale flag, discount, currency, dates, venue, description, categories, tickets available). Rating, rating count, image URL, scrape time and the carried-forward marker never decide UPDATED (they are still returned).
- Ignore fields when detecting changes (
ignoreFieldsForChanges): list field names (or dotted paths such assessions.image) that must never make a record UPDATED or appear inchangedFields. Changing this list does not cause a one-time wave of UPDATED rows. - Change scope (
changeScope):priceAndStockmakes only price, original price, on-sale flag, discount, currency and tickets available decide UPDATED. Defaultallis unchanged. - Compact UPDATED rows (
compactUpdates, off by default): UPDATED rows carry only the event id, URL, title, current price fields andpriceChangeswith old and new values. The event details charge is not applied to a compact row, since the details are not in it. NEW rows stay full. - Expire after N missed scans (
expireAfterMissedScans, default 1): with Emit expired, a record is marked EXPIRED only after that many consecutive complete scans miss it. EXPIRED means the event dropped out of the listing (sell-out, ended run or ranking change), not that it is proven unavailable.
Send results into your apps (MCP connectors)
Optionally pipe the scraped events into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape: the Apify dataset is never changed.
What gets written to the connector: a condensed, human-readable summary of each event, not the full JSON record. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.
- Authorize a connector once under Apify, Settings, Integrations (Notion, Linear, Airtable, or Apify).
- Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
- For Notion, also set
notionParentPageUrlto the page where event pages should be created.
The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.
Input Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
mode | string | search | search walks city catalogues, url processes the Fever URLs you paste. |
cities | array | ["new-york"] | City slugs to browse (search mode), for example new-york, london, madrid, paris, milan, sao-paulo. |
queryType | string | (none) | Alternative mode word: browse is search mode, event reads one event (use with id). |
city | string | (none) | One city by name, slug or code such as LON; when set it replaces cities, so only this city is scraped. |
id | string | (none) | A numeric Fever event ID, same as pasting https://feverup.com/m/ID. When filled, only that event is read: Mode and the sample URL list are ignored (set queryType to browse to ignore it). |
locale | string | en | Site language prefix for city pages: en, es, fr, it, pt or de (search mode). |
category | string | (none) | Narrow every city walk to one category slug, for example candlelight, music-events, exhibitions or food (search mode). |
query | string | (none) | Keep only rows whose title or categories contain this keyword (search mode). |
urls | array | one example per supported shape (see the URL shapes table) | Fever event, city or category URLs to process (url mode). |
minPrice | integer | (none) | Keep only events whose from-price is at least this amount, in the row's own currency. |
maxPrice | integer | (none) | Keep only events whose from-price is at most this amount, in the row's own currency. |
maxReviewsPerEvent | integer | 20 | With Fetch event details on, attaches up to this many of the newest guest reviews to each event (maximum 500, 0 turns them off). Reviews are included in the event details fee and add no separate charge; changes to the reviews list alone never mark a row UPDATED. |
fetchDetails | boolean | false | Fetch each event's page for description, venue address with coordinates, categories, session dates and ticket availability. Charged once per record. |
maxItems | integer | 20 | Stop after collecting this many records across all cities and URLs. 0 means unlimited. |
resumeFromRunId | string | (none) | Continue one interrupted run: paste its run or dataset id to skip records already collected there. |
changeScope | string | all | Incremental only: priceAndStock limits UPDATED to price and availability moves. |
compactUpdates | boolean | false | Incremental only: slim UPDATED rows with priceChanges. |
expireAfterMissedScans | integer | 1 | Incremental only: consecutive complete scans a record must miss before EXPIRED. |
ignoreFieldsForChanges | array | empty | Incremental only: fields that never decide UPDATED. |
incrementalMode | boolean | false | Turn on for recurring monitoring of the same search: later runs return only NEW, UPDATED and REAPPEARED records. |
stateKey | string | (none) | Name this monitoring campaign, or deliberately share state across differently configured runs. |
emitUnchanged | boolean | false | Also return (and bill) records that have not changed since the last run. |
emitExpired | boolean | false | Also return (and bill) records that were tracked before but are no longer found, once a run has fully scanned the tracked search. |
mcpConnectors | array | (none) | Optional: send a summary of each record to apps you authorized under Integrations. |
notionParentPageUrl | string | (none) | Notion connector only: page under which event pages are created. |
maxNotifyListings | integer | 50 | Cap on records written to each connector per run. Does not affect the dataset. |
proxy | object | {"useApifyProxy": true} | Connection settings. Leave the default unless a run reports it could not read any results. |
Output Example
Sample shape: values are illustrative placeholders, not from a live record.
{"recordId": "9000001","rowType": "event","eventId": "9000001","url": "https://feverup.com/m/9000001","title": "Sample Concert Evening","citySlug": "new-york","locale": "en","category": "candlelight","priceFrom": 25,"priceText": "From 25.00 USD","originalPrice": 30,"onSale": true,"discountPercent": 16.7,"currency": "USD","priceType": "from","startDate": "2026-11-01T19:00:00-04:00","endDate": "2026-11-30T21:00:00-04:00","venueName": "Sample Hall","rating": 4.5,"ratingCount": 320,"isNew": false,"imageUrl": "https://feverup.com/images/sample-event.jpg","description": "A candlelit evening of chamber music for all ages.","venueAddress": "100 Sample Street, New York, 10001","latitude": 40.0,"longitude": -74.0,"categories": ["Music", "Family"],"firstSessionDate": "2026-11-01T19:00:00-04:00","lastSessionDate": "2026-11-30T20:30:00-04:00","ticketsAvailable": true,"sessionsText": "Nov 1 - Nov 30","scrapedAt": "2026-11-01T12:00:00Z","changeType": "UPDATED","changedFields": ["priceFrom", "originalPrice"],"firstSeenAt": "2026-10-01T12:00:00Z","lastSeenAt": "2026-11-01T12:00:00Z"}
Plan Requirement
Datacenter connections are enough for Fever: no residential proxy is required, and the default Apify proxy setting works without any change. Fever pages were read successfully over datacenter connections without a block. If a connection is refused, the run retries on a backup connection and logs "Served over the backup connection (the default connection was unavailable)."
On an Apify free plan the proxy may be unavailable. The run then logs "The selected connection is unavailable to this run" and continues on a backup connection, where some pages may still be unavailable. If nothing at all could be read you get one of these failures: "The proxy connection was refused for this account, so no page could be read" (your plan does not include proxy access), "No results: residential proxies are unavailable on this run" (the backup connection also could not load the pages), or "Could not load any results page (the requests failed), so nothing was collected" (a connection problem, not an empty search; try again later). You can also supply your own proxy URLs under Proxy configuration.
FAQ
How much does it cost?
You pay a one time actor start fee plus a fee per event record returned, and a separate event details fee (the detail-enrichment event, charged once per record at the end of the run) only for records returned with Fetch event details on and whose event page was successfully read. Guest reviews are part of that fee and add no further charge. The record fee is the apify-default-dataset-item event. The Pricing tab shows the current rates. Use Max items to cap the cost of any run.
Is it legal to scrape Fever?
This actor collects only publicly available event listing data. You are responsible for how you use it: follow feverup.com's terms and the laws that apply to you, and get legal advice if you plan commercial redistribution. Event names, dates and prices are generally facts, but photos and descriptions may be subject to third-party rights.
Can I get only new or changed events on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated and reappeared records, and unchanged ones are not billed unless you ask for them.
Why did my run fail instead of returning an empty dataset?
If the run collected zero records and any pasted URL could not be opened or read, the run fails with a clear connection message instead of returning a false "zero results", since a URL you explicitly asked for was never resolved. A run that collected zero records only because some city or category pages were refused, while others returned records or genuinely matched nothing, stays a success whose status message names what could not be read.
What happens to an event whose date has passed?
Fever itself stops listing an event on its city and category pages once it is no longer bookable. On a monitored search with Incremental mode and Emit expired records both on, the next run that completes a full, uncapped scan of the tracked scope marks that event EXPIRED. If it ever reappears on the site later, it comes back as REAPPEARED, never as a fresh NEW record.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.
๐ More scrapers you might like
Pair this actor with these related scrapers from the same team:
| ๐งฉ Viagogo Scraper Scrape Viagogo events by artist, production, venue, city, category, or URL. Extract event... | โฝ Eventim Scraper Scrape CTS Eventim Germany and EU event catalogue: concerts, festivals, comedy, sports... |
| ๐งฉ Songkick Scraper Scrape Songkick concert and event calendars: upcoming and past dates, venues, cities... | ๐ SeatGeek Scraper Scrape SeatGeek events with ticket price ranges (lowest, highest, average, median)... |
| โ๏ธ Pollstar Scraper Scrape Pollstar upcoming concerts and tour dates: play date, venue with full address and... | ๐งฉ Ticketmaster Scraper Discover and scrape Ticketmaster events across the US, UK, Australia and Canada. Search... |
๐ Browse all abotapi scrapers
๐ฌ Support
- ๐ Found a bug or a missing field? Open a ticket on the Issues tab. We usually reply within hours.
- ๐ ๏ธ Need another site, extra fields or a private build? Email contact@abotapi.com.
- โญ Enjoying it? A quick review on the actor page helps other users find it.