EventUp APIeventup.com ↗
Access EventUp venue data via API. Search venues by city, retrieve filters, featured listings, and autocomplete suggestions for party, wedding, and corporate spaces.
What is the EventUp API?
The EventUp API exposes 4 endpoints that cover venue search, filter discovery, featured listings, and autocomplete across the EventUp platform. The search_venues endpoint returns paginated venue listings with fields for pricing, capacity, amenities, venue types, and contact information for any searched city or location. Combined with get_venue_filters, developers can build location-aware venue finders with full facet data.
curl -X GET 'https://api.parse.bot/scraper/b84efb92-5e32-4e34-a581-55c899788c46/search_venues?page=1&radius=50&location=Chicago' \ -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 eventup-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.eventup_api import EventUp, Venue, FeaturedVenue, FilterSet, AutocompleteResult, FilterOption, PlaceSuggestion
client = EventUp()
# Discover locations via autocomplete
result = client.venues.autocomplete(query="chi")
for place in result.places:
print(place.title, place.full_name, place.slug)
# Get filter options for a location
filters = client.venues.filters(location="Chicago")
for amenity in filters.amenities:
print(amenity.name, amenity.count)
# Search venues in Chicago with pagination
for venue in client.venues.search(location="Chicago", radius=25):
print(venue.title, venue.city_and_state, venue.display_price, venue.standing_capacity)
# Browse featured venues platform-wide
for featured in client.featuredvenues.list():
print(featured.title, featured.city_and_state, featured.display_price)
Search for venues by location with pagination support. Returns comprehensive venue listings including pricing, capacity, amenities, venue types, contact info, and location data. The API normalizes city names to slug format and attempts common state suffixes if the initial search fails. Paginated via integer page counter; each page returns up to 36 venues.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| radius | integer | Search radius in miles. |
| locationrequired | string | City or location name (e.g., 'Las Vegas', 'Chicago', 'New York'). Automatically normalized to slug format for the API. |
{
"type": "object",
"fields": {
"page": "integer - current page number",
"venues": "array of venue objects with id, title, slug, url, pricing, capacity, amenities, venue_types, location data",
"has_next": "boolean - whether more pages exist",
"num_pages": "integer - total number of pages available",
"place_name": "string - name of the searched location",
"total_venues": "integer - number of venues in this response"
},
"sample": {
"data": {
"page": 1,
"venues": [
{
"id": 48130,
"url": "https://eventup.com/venue/bar-avec/",
"slug": "bar-avec",
"phone": "+1 (555) 012-3456",
"title": "Bar Avec",
"cities": [
"Chicago",
"Evanston",
"Schaumburg"
],
"tagline": "Relaxed open-air rooftop restaurant.",
"amenities": [
"WiFi",
"A/V Equipment",
"Full Bar"
],
"max_price": 1000000000,
"min_price": 2500,
"event_types": [
"Birthday Party",
"Corporate Event",
"Social Event"
],
"is_featured": true,
"venue_types": [
"Restaurant",
"Cocktail Lounge"
],
"dollar_signs": 1,
"place_string": "River North",
"display_price": "$2,500",
"look_and_feel": [
"Classic",
"Classy",
"Exposed Brick"
],
"neighborhoods": [
"River North"
],
"city_and_state": "Chicago, IL",
"location_point": {
"lat": 41.8936,
"lon": -87.6329
},
"seated_capacity": null,
"default_photo_url": "//venue-media.eventup.com/resized/venue/bar-avec/fc6c.480x320.jpg",
"standing_capacity": null
}
],
"has_next": true,
"num_pages": 19,
"place_name": "Chicago",
"total_venues": 36
},
"status": "success"
}
}About the EventUp API
Venue Search and Pagination
The search_venues endpoint accepts a location string (city name such as 'Chicago' or 'Las Vegas'), an optional radius in miles, and an optional page integer for pagination. Each response includes an array of venue objects with fields for id, title, slug, url, pricing, capacity, amenities, venue_types, and location data. The response also surfaces has_next, num_pages, and total_venues so you can walk through all results for a given market. Location strings are normalized to slug format internally, with fallback attempts on common state suffixes.
Filter Facets and Taxonomy
get_venue_filters returns the full set of filterable dimensions for a location: amenities, venue_types, event_types, look_and_feel, and neighborhoods. Each facet item includes an id, name, and count indicating how many venues in that area match. Neighborhood objects also carry a city field. This endpoint is useful for populating filter UIs or understanding the taxonomy of a specific market before querying.
Featured Venues and Autocomplete
get_featured_venues requires no parameters and returns a platform-wide list of promoted venues with total, plus venue objects containing id, title, slug, url, pricing, capacity, and location data. The get_autocomplete endpoint accepts a query string and returns a suggestions object split into venues (with id, title, slug, url, default_photo_url, city_and_state) and places (with type and slug). Place slugs returned here can be passed directly as the location parameter in search_venues.
The EventUp API is a managed, monitored endpoint for eventup.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when eventup.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 eventup.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 venue comparison tool that shows pricing and capacity side-by-side for a given city using
search_venuesfields. - Populate neighborhood and amenity filter dropdowns for an event planning app using
get_venue_filtersfacet counts. - Surface promoted venue listings on a travel or event discovery site using
get_featured_venues. - Implement a location autocomplete that resolves partial city names to valid
locationslugs viaget_autocomplete. - Aggregate venue type distribution across multiple cities to analyze supply in different markets.
- Generate structured venue directories for specific event categories (weddings, corporate) using
venue_typesandevent_typesfilters. - Monitor featured venue inventory changes over time by periodically calling
get_featured_venuesand comparing results.
| 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 EventUp have an official developer API?+
What does `get_venue_filters` return, and how does it differ from `search_venues`?+
get_venue_filters returns filterable facets — arrays of amenities, venue types, event types, look-and-feel categories, and neighborhoods — each with an id, name, and venue count for the specified location. It does not return individual venue records. search_venues returns the actual venue listings. The two endpoints are complementary: use get_venue_filters to understand available filter values, then apply those dimensions contextually when building search UIs.Can I retrieve individual venue detail pages, including full photo galleries or reviews?+
search_venues and get_featured_venues, which include pricing, capacity, amenities, and location data, but does not expose a dedicated single-venue detail endpoint with full photo galleries or user reviews. You can fork the API on Parse and revise it to add a venue detail endpoint using the slug or id values already returned.How does pagination work in `search_venues`, and are there known limits per page?+
search_venues response includes page (current page), has_next (boolean), and num_pages (total pages). Increment the page parameter and check has_next to walk through all results. The total_venues field reflects the count of venues in the current response rather than a global total, so use num_pages to gauge full result set size.Does the API support filtering search results by amenity or venue type directly in `search_venues`?+
search_venues accepts location, radius, and page as inputs; it does not accept amenity IDs or venue type IDs as direct filter parameters. The filter taxonomy is available through get_venue_filters. You can fork the API on Parse and revise it to pass filter parameters into the search endpoint using the IDs returned by get_venue_filters.