# Eventbrite City Wise (`xenondev/xenon-eventbrite-city`) Actor

Scrapes public Eventbrite destination pages for a city + date window. Category is optional — omit it to fetch all categories in that city. Same webhook output schema as xenon-eventbrite.

- **URL**: https://apify.com/xenondev/xenon-eventbrite-city.md
- **Developed by:** [XenonDev](https://apify.com/xenondev) (community)
- **Categories:** Developer tools, Automation, Agents
- **Stats:** 1 total users, 1 monthly users, 90.3% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $0.50 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## xenon-eventbrite-city

Apify Actor that scrapes **Eventbrite public destination pages** for feedirl.

**Separate from `xenon-eventbrite`:** here **`category` is optional**. Omit it (or pass blank / `all` / `events`) to scrape **all categories** for a city via:

`https://www.eventbrite.com/d/{state}--{city}/events/?start_date=…&end_date=…`

When `category` is set, behavior matches the original Actor (`/{category}/` path).

Uses Apify **residential proxies** + `CheerioCrawler` with `SessionPool`.
Output shape matches `xenon-eventbrite` / `event-ingestion-webhook` (`source: "eventbrite"`).

***

### Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `city` | string | yes | — | Metro name or Eventbrite slug (`ok--oklahoma-city`) |
| `category` | string | **no** | — | Category slug; leave empty for all events |
| `startDate` | string | yes | — | `YYYY-MM-DD` |
| `endDate` | string | yes | — | `YYYY-MM-DD` |
| `country` | string | no | `united-states` | Kept for parity |
| `maxPages` | integer | no | `20` | Max listing pages |
| `proxyConfiguration` | object | no | RESIDENTIAL | Keep residential |

#### Example — Oklahoma City, no category

```json
{
  "city": "Oklahoma City",
  "startDate": "2026-08-21",
  "endDate": "2026-08-28",
  "maxPages": 5
}
```

#### Example — with category

```json
{
  "city": "ny--new-york",
  "category": "food-and-drink",
  "startDate": "2026-08-21",
  "endDate": "2026-08-28"
}
```

***

### Local / deploy

```bash
npm install
## Edit INPUT.json
npx apify run   # often blocked locally without residential proxies

apify login
apify push
```

After push, use Actor id `xenondev~xenon-eventbrite-city` (or the Console ID) in runtime / ingest for **city-only** fetches. Keep `xenon-eventbrite` for the existing city × category grid.

***

### vs xenon-eventbrite

| | `xenon-eventbrite` | `xenon-eventbrite-city` |
|--|--|--|
| Category | **Required** | **Optional** |
| No-category URL | n/a | `/d/{slug}/events/` |
| Use for | Weekly ingest grid | Runtime open browse / unmapped interests |

# Actor input Schema

## `city` (type: `string`):

Metro display name (e.g. 'Oklahoma City', 'New York') OR Eventbrite location slug (e.g. 'ok--oklahoma-city', 'ny--new-york'). Format for slugs: {state}--{city} lowercase with hyphens.

## `category` (type: `string`):

Eventbrite category slug (e.g. 'food-and-drink', 'arts'). Leave blank to scrape ALL categories for the city (uses /events/ destination path). Prefill is a single category so Store tests stay under 5 minutes.

## `startDate` (type: `string`):

Start of date range in YYYY-MM-DD. Optional — if omitted, uses today (UTC).

## `endDate` (type: `string`):

End of date range in YYYY-MM-DD. Optional — if omitted, uses 7 days from today (UTC).

## `country` (type: `string`):

Eventbrite country slug (unused in URL today; kept for parity with xenon-eventbrite).

## `maxPages` (type: `integer`):

Maximum listing pages to scrape. Omit to crawl all Eventbrite search pages (capped at 49). Prefill is 1 for a fast Store/console test run.

## `maxItems` (type: `integer`):

Stop after this many unique events. Omit for no item cap.

## `proxyConfiguration` (type: `object`):

Residential proxies are required — Eventbrite blocks most datacenter IPs.

## Actor input object example

```json
{
  "city": "ok--oklahoma-city",
  "category": "food-and-drink",
  "startDate": "2026-08-22",
  "endDate": "2026-08-29",
  "country": "united-states",
  "maxPages": 1,
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

## `events` (type: `string`):

All scraped events as dataset items.

## `run` (type: `string`):

No description

# 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 = {
    "city": "New York",
    "category": "food-and-drink",
    "maxPages": 1,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("xenondev/xenon-eventbrite-city").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 = {
    "city": "New York",
    "category": "food-and-drink",
    "maxPages": 1,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("xenondev/xenon-eventbrite-city").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 '{
  "city": "New York",
  "category": "food-and-drink",
  "maxPages": 1,
  "maxItems": 20
}' |
apify call xenondev/xenon-eventbrite-city --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,xenondev/xenon-eventbrite-city"
        }
    }
}

```

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/XPet3sW1V3vCNcodz/builds/ZvDYMEdWcOEGQZLrS/openapi.json