# Eventbrite Search Events — Multi-URL Calendar Watchlist (`jpmarketdata/eventbrite-search-event-watchlist`) Actor

Export public Eventbrite city, category and keyword searches into a deduplicated event calendar with local dates, venue city and source provenance. Preserve native filters, paginate and show coverage limits without organizer or attendee contacts. Unofficial.

- **URL**: https://apify.com/jpmarketdata/eventbrite-search-event-watchlist.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Automation, Marketing, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 public event delivereds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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](https://apify.com/jpmarketdata/mercari-japan-price-checker)
- [Yahoo! Auctions Japan Sold Prices — Median, Range, Bids](https://apify.com/jpmarketdata/yahoo-auction-sold-comps)

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.

# Actor input Schema

## `searchUrls` (type: `array`):

One to three public www.eventbrite.com/d/ city/category/keyword search URLs. Native filters are retained; each search begins at page 1. No arbitrary hosts, APIs, checkout or cookies.

## `maxEventsPerSearch` (type: `integer`):

1–500 distinct public source events per search; default 40. The bound is explicit in output and does not imply all events in a city.

## `maxPagesPerSearch` (type: `integer`):

1–25 native search pages per URL, default 2. Requested page caps are reported; exceeding the hard run-time budget fails before delivery.

## Actor input object example

```json
{
  "searchUrls": [
    "https://www.eventbrite.com/d/ny--new-york/technology/"
  ],
  "maxEventsPerSearch": 40,
  "maxPagesPerSearch": 2
}
```

# Actor output Schema

## `results` (type: `string`):

Source local dates, timezone, actual venue city, public event link and bounded search provenance.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchUrls": [
        "https://www.eventbrite.com/d/ny--new-york/technology/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/eventbrite-search-event-watchlist").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searchUrls": ["https://www.eventbrite.com/d/ny--new-york/technology/"] }

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/eventbrite-search-event-watchlist").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchUrls": [
    "https://www.eventbrite.com/d/ny--new-york/technology/"
  ]
}' |
apify call jpmarketdata/eventbrite-search-event-watchlist --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/eventbrite-search-event-watchlist"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HfDmbYHbiXuQqhztv/builds/Gsadm9SJWCGnS39j7/openapi.json