Feverup APIfeverup.com ↗
Access Fever's event catalog via API: search events by city, filter by category, and retrieve full event details including pricing, venue, and ratings.
What is the Feverup API?
The Feverup API covers 6 endpoints for discovering live events and experiences across cities worldwide. Starting with list_cities to retrieve supported city codes, you can then call search_events with a keyword and city code to get paginated results including ticket price, rating, venue, and upcoming session data for each matching event.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/e12557d2-bcfd-4498-a035-9341769b02b4/list_cities' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace feverup-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.feverup_api import Feverup, City, EventSummary, Event, EventNotFound
client = Feverup()
# List all supported cities
for city in client.cities.list():
print(city.city_name, city.city_code, city.is_top_city)
# Construct a city and search for events
nyc = client.city("NYC")
for event in nyc.events.search(query="concert", limit=5):
print(event.name, event.price, event.currency, event.rating)
# Browse popular events in a city
for event in nyc.events.list(limit=3):
print(event.name, event.location_name, event.num_ratings)
# Filter by category
for event in nyc.events.by_category(category="candlelight-concerts", limit=3):
print(event.name, event.price, event.next_sessions)
# Get exhibition and expo events
for event in nyc.events.exhibitions(limit=3):
print(event.name, event.city_name, event.cover_image_url)
# Drill into event details
for summary in nyc.events.search(query="museum", limit=1):
detail = summary.details()
print(detail.title, detail.venue.name, detail.venue.city)
print(detail.start_date, detail.end_date, detail.price, detail.currency)
print(detail.rating, detail.description[:100])
Returns all supported Fever cities with their codes, names, slugs, and metadata. The full city list is returned in a single response with no pagination. Each city's city_code can be used to scope event queries.
No input parameters required.
{
"type": "object",
"fields": {
"cities": "array of city objects with city_id, city_code, city_name, country_name, slug, thumbnail_url, and is_top_city"
},
"sample": {
"data": {
"cities": [
{
"slug": "new-york",
"city_id": 6,
"city_code": "NYC",
"city_name": "New York",
"is_top_city": true,
"country_name": "United States",
"thumbnail_url": "https://applications-media.feverup.com/image/upload/fever2/city/photos/web/new-york-560x560.jpg"
}
]
},
"status": "success"
}
}About the Feverup API
City Discovery and Event Search
list_cities returns a flat array of all supported Fever cities — each object includes city_id, city_code, city_name, country_name, slug, thumbnail_url, and an is_top_city flag. The city_code value (e.g. NYC, LON, PAR) is the key input for scoping all other endpoints. search_events accepts a required query string and an optional city_code, returning paginated results with fields like rating, num_ratings, price, currency, cover_image_url, and location metadata. Pagination is managed via a zero-based page integer; when next_page is null, you have reached the last page.
Category and Popularity Filtering
get_category_events filters results by a category slug — examples include candlelight-concerts, exhibitions, and immersive-experiences — while sharing the same response shape as search_events. get_city_events drops the category constraint and returns events ordered by popularity for a given city_code. get_exhibition_expos is a specialized endpoint combining an expo keyword search with the exhibitions category, useful for surfacing expo-specific listings without manually constructing that query yourself.
Event Detail
get_event_detail accepts a numeric plan_id (the id field from any listing endpoint) and returns the full event record: title, url, price, currency, rating, category, end_date, an images array of URL strings, and a structured venue object containing name, address, city, region, and country. The end_date field follows ISO datetime format and may be null for open-ended events.
The Feverup API is a managed, monitored endpoint for feverup.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when feverup.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official feverup.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a city-specific event discovery app using
get_city_eventssorted by popularity andget_event_detailfor full venue and pricing info. - Aggregate candlelight concerts or immersive experience listings across multiple cities via
get_category_eventswith differentcity_codevalues. - Power a travel planning tool that surfaces upcoming events in a destination city using
search_eventswith arrival-city codes fromlist_cities. - Create a deals or price-comparison feed by collecting
priceandcurrencyfields from event search results across multiple cities. - Index exhibition and expo listings for a niche content site using
get_exhibition_exposacross all supported cities. - Enrich venue data pipelines with structured
venue.address,venue.region, andvenue.countryfields fromget_event_detail. - Build a rating-based recommendation engine using
ratingandnum_ratingsfields returned bysearch_eventsorget_category_events.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Feverup have an official developer API?+
What does `get_event_detail` return that the listing endpoints do not?+
get_event_detail returns fields not present in listing results: a full images array, the url of the event page on Feverup, a structured venue object with street address and region, and the end_date in ISO datetime format. Listing endpoints return a summary location string and cover image but not the complete venue breakdown.How does pagination work across the search and listing endpoints?+
search_events, get_category_events, get_city_events, get_exhibition_expos) use a zero-based integer page parameter. The response includes a next_page field that is an integer when more results exist and null when you have reached the final page. The total_count field indicates the full number of matching events.Does the API expose ticket purchase links or real-time seat availability?+
url field on get_event_detail, nor real-time seat inventory. You can fork this API on Parse and revise it to add an endpoint targeting ticketing data if that surface becomes accessible.Can I filter events by date range or upcoming session time?+
end_date field is available per-event in get_event_detail, and listing results include upcoming session times, but you cannot pass a start or end date as a filter. You can fork this API on Parse and revise it to add date-based filtering logic on top of the returned session data.