Eventbrite Search Event Watchlist

Unofficial — independent tool, not affiliated with, endorsed by, or sponsored by Eventbrite. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

Export the events returned by multiple public Eventbrite search URLs into one deduplicated calendar dataset. Event researchers and calendar editors can schedule their city/category/keyword searches and join records by event ID. The source controls relevance and geographic matching; use the returned event city/country rather than assuming every recommendation is in the search city.

Input

Supply one to three searchUrls from the public Eventbrite /d/ search pages on www.eventbrite.com. Preserve native city, category and keyword filters in the URL. No arbitrary host, organizer account, API credential, attendee data or cookie input. maxEventsPerSearch is 1–500 (default 40); maxPagesPerSearch is 1–25 (default 2). Acquisition always begins at page 1, then advances numerically. Duplicate normalized searches are fetched once. When searchUrls is omitted, API and console runs both use New York technology events. An explicit empty or null searchUrls is invalid.

Output

One row per unique public event ID across the searches, with contact-redacted title, source event URL, local start/end date and time, timezone, online flag, public venue name and city/region/country. searchUrls retains every requested search where the event was observed; sourcePositions records source URL, page and rank. Hidden source dates/times remain empty strings, never estimated. No prices, ticket availability, popularity score, total city inventory, organizer contacts, event descriptions or attendee identities are claimed. A requested search page is a relevance-ranked sample, and the site can mix online or distant recommendations. Dates are source local values, not UTC. Rows retain page count and source-reported count metadata; these are source claims and can disagree. sourceLimitReached is true if a requested cap, our page cap or the site's finite page window prevents claiming full coverage. No source-order or inclusion comparison is claimed to be a trend.

Limits

256 MB. At most 3 searches × 25 pages, 76 requests including robots; 20 seconds per request, 300 seconds total, sequential with one-second spacing. HTML responses are limited to 2 MiB. Only anonymous allowed public /d/ pages are fetched; no event-detail, API, checkout, sign-in or organizer profile requests, no redirects, proxy, browser or paid API. robots is rechecked on every run. Cancelled or protected events are excluded. Each requested search must supply at least one usable public event; empty or inaccessible sources fail before output. Challenge/auth failures, HTTP429, timeout and incompatible embedded data are separate errors. Partial-source failure fails the entire run before charging. Requested item/page bounds are explicit samples. A hard request/body/run-time budget exhaustion fails before delivery and charging; no full inventory claim.

Privacy

Only event metadata necessary for a calendar is retained. A venue name that is itself a numbered street address is omitted. Titles and venue names have email addresses, phone patterns, URLs and @handles redacted. No organizer IDs/names/profiles, attendee data, street address, coordinates, images, freeform descriptions, raw source bodies or cookies are stored or logged. Event ID is an event identifier, never a person identifier. Output fields have a strict allowlist. Public event names can contain people's names; do not use this dataset to profile individuals.

Pricing

One primary event-delivered event at $0.001 per validated distinct event row successfully delivered. No start, enrichment, secondary or default-dataset event. A repeated event from multiple searches is charged once. Default up to 40 events costs at most $0.04; maximum 1,500 distinct events at most $1.50. Before fetching, PPE allowance must cover the requested maximum; the Actor never silently narrows searches to fit billing. Unusable rows, empty searches and failures before delivery have no event charge. This independent tool is not affiliated with Eventbrite. Source terms tension is recorded in the scout under DR-0007.

If something goes wrong

• Wrong number or a failed run? Open a ticket on the Issues tab. I read every one and reply within 2 business days (Japan time).
• You never get a fake "empty" result. If the site can't be read, the run fails and says so.
• Delivered rows only. One validated unique row is one billable event. Duplicates, summaries, failed acquisition and undelivered rows are not charged.
• Checked every week. An automatic test runs this tool weekly; if the site changes, I fix it.
• Public source data only. No login or member/applicant records. Contact patterns are screened before delivery; prose may still name people.

More tools by the same author

• Mercari Japan Sold Prices — What Items Really Sell For
• Yahoo! Auctions Japan Sold Prices — Median, Range, Bids

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): https://apify.com/jpmarketdata

Disclaimer

Unofficial, independent tool — not affiliated with, endorsed by, or sponsored by Eventbrite. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.