Nimbryxo Studio

Use Eventbrite Event Finder with Venue Geocoordinates with Python

Browse Eventbrite listings by city or category and get event dates, venue address and geocoordinates, cover images, organizer and ticket link for every event.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "includeDetails": false,
  "maxItems": 3,
  "organizerMode": false,
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/d/united-states/all-events/"
    }
  ],
  "useSitemap": false
}

Download input.example.json and save your reviewed copy as input.json.

FieldTypeRequiredDescription
startUrlsarrayoptionalEventbrite browse URLs (e.g. https://www.eventbrite.com/d/ny--new-york/all-events/), direct event URLs (/e/...), or organizer URLs (/o/...). Accepts URL strings and {"url": ...} objects. When set, this wins over the filter fields.
locationstringoptionalLegacy city/region slug used when startUrls and locations are empty, e.g. ny--new-york, ca--san-francisco, united-states, online. Blank defaults to united-states.
categorystringoptionalLegacy category slug such as music, business, food-and-drink, sports. Kept for backward compatibility: when used alone it runs as a keyword query, matching the old category URL behaviour. Use 'categories' for exact taxonomy filtering.
maxItemsintegeroptionalMaximum number of unique events to return across all queries. The source caps each query at 1,000 events; above 1,000 the actor splits by date, category, price, and online coverage, or scans the event sitemap when useSitemap is enabled.
keywordsarrayoptionalKeyword queries (q). Each value is a separate query slice; results are deduplicated by event ID.
locationsarrayoptionalCity, region, or place IDs, e.g. ny--new-york, london, united-kingdom--london, 85977539. Multiple locations run as separate queries and are deduplicated.
countrystringoptionalCountry filter. Combined with locations when possible; use any to leave it open.
categoriesarrayoptionalExact EventbriteCategory filters. Accepts display names, numeric IDs, or EventbriteCategory/<id>. Captured catalog: Business & Professional (101), Science & Technology (102), Music (103), Film, Media & Entertainment (104), Performing & Visual Arts (105), Fashion & Beauty (106), Health & Wellness (107), Sports & Fitness (108), Travel & Outdoor (109), Food & Drink (110), Charity & Causes (111), Community & Culture (113), Religion & Spirituality (114), Family & Education (115), Seasonal & Holiday (116), Home & Lifestyle (117), Auto, Boat & Air (118), Hobbies & Special Interest (119), School Activities (120), Other (199). Unknown values are skipped with a warning.
formatstringoptionalExact EventbriteFormat filter. Accepts the display name or an EventbriteFormat/<id> value.
datePresetstringoptionalDate window. today and tomorrow use the browse page; the other presets use the search API. custom requires dateFrom and dateTo.
dateFromstringoptionalStart date (YYYY-MM-DD). Used only with datePreset=custom.
dateTostringoptionalEnd date (YYYY-MM-DD). Used only with datePreset=custom.
priceFilterstringoptionalFree or paid events. Uses the search API's price filter and is checked again client-side.
eventTypestringoptionalAny, in-person, or online. Online uses online_events_only without a place filter; in-person removes online events client-side.
sortstringoptionalRelevance keeps Eventbrite's default order. date is experimental and ascending only: it sends event_search.sort=date and forces the search API path. Ordering is by start date; same-day times may vary. Descending order is not supported.
organizerModebooleanoptionalAdd organizer profile metrics and social links from the organizer page. Also implied by organizer URLs in startUrls. Records stay event records.
includeDetailsbooleanoptionalFetch the event detail page and public event API for description, ticket classes, refunds, age, door time, UTC times, duration, series counts, and the conditional Facebook event ID. Adds one or two requests per event.
useSitemapbooleanoptionalOnly for runs above 1,000. Scan Eventbrite's event sitemaps (about 201,000 event IDs) and hydrate in batches instead of splitting search queries. Filters are applied client-side. Ignored with startUrls or maxItems <= 1,000.
proxyConfigurationobjectoptionalOptional. Never required. The actor works from a datacenter IP by default; an AUTO proxy is supported. No residential proxy or login is used.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/FdMoiJCc2SsI8M9PA/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

Omit-empty Eventbrite event records with dates, UTC times, venue address and geocoordinates, images, taxonomy, organizer profile, ticket price and availability, and optional detail fields.

Questions before you run

Which inputs are required?

No top-level fields are marked required in the published schema. Conditional requirements can still apply; check the README.

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Generated from source build cuKxsoljlR97VIqrd and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.