AllEvents Events Scraper

Scrape public AllEvents listings by city, keyword, category, or URL for event research, marketing, newsletters, and lead generation.

Data fields

FieldTypeDescription
eventIdstring | nullAllEvents event identifier when supplied.
titlestringPublic event title.
eventUrlstringPublic AllEvents event page.
descriptionSnippetstring | nullShort public event description.
startDateTimestring | nullEvent start time when available.
endDateTimestring | nullEvent end time when available.
venueNamestring | nullPublic venue name.
venueAddressstring | nullPublic venue address.

Input preview

startUrlsAllEvents listing URLs
cityCity
keywordKeyword
categoryCategory
fromDateFrom date
toDateTo date

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

Extract public event listings from AllEvents into a clean dataset for local marketing, event research, newsletters, venue monitoring, and lead generation.

Use it to collect event titles, dates, venues, addresses, organizer names, interest counts, images, ticket links, categories, and source URLs by city, category, keyword, or specific AllEvents listing URLs.

What you can do

  • Track upcoming events in a city such as New York, London, or Dubai.
  • Export music, comedy, business, workshop, nightlife, or free-event listings.
  • Build local event calendars and community newsletters.
  • Monitor venues, agencies, and event organizers for lead generation.
  • Collect structured event URLs for follow-up enrichment.

Who is it for

Event marketers, local SEO teams, tourism and community publishers, venues, agencies, and data teams that need public event listings in JSON, CSV, Excel, or API-ready formats.

Example inputs

Scrape upcoming New York events

{
  "city": "new york",
  "category": "all",
  "maxItems": 25
}

Scrape music events from a listing URL

{
  "startUrls": [{ "url": "https://allevents.in/new-york/music" }],
  "maxItems": 50
}

Search a keyword in a city

{
  "city": "london",
  "keyword": "startup",
  "category": "business",
  "maxItems": 40
}

Input

Field Type Description
startUrls array Optional AllEvents listing URLs, for example city/category pages.
city string City name or slug used when no start URL is supplied.
keyword string Optional keyword to search within the selected city/category.
category string Category slug such as all, music, business, workshops, comedy, concerts, or free-events.
fromDate string Optional start date filter in YYYY-MM-DD format.
toDate string Optional end date filter in YYYY-MM-DD format.
maxItems integer Maximum number of events to save.
proxyConfiguration object Optional proxy settings. Leave disabled unless blocked.

API usage

cURL

curl "https://api.apify.com/v2/acts/fetch_cat/allevents-events-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"city":"new york","category":"all","maxItems":25}'

Get dataset items from a run:

curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=json"

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/allevents-events-scraper').call({
  city: 'new york',
  category: 'all',
  maxItems: 25,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('<ANNA_APIFY_USERNAME>/allevents-events-scraper').call(run_input={
    'city': 'new york',
    'category': 'all',
    'maxItems': 25,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and agents

Use this actor with Apify MCP-compatible agents:

https://mcp.apify.com?tools=fetch_cat/allevents-events-scraper

Add it to Claude Desktop or Claude Code:

claude mcp add apify-allevents-events --url "https://mcp.apify.com?tools=fetch_cat/allevents-events-scraper"

Example MCP server configuration:

{
  "mcpServers": {
    "apify-allevents-events": {
      "url": "https://mcp.apify.com?tools=fetch_cat/allevents-events-scraper"
    }
  }
}

Example prompts:

  • “Find 30 upcoming startup events in London and include venue addresses.”
  • “Export New York music events with event URLs and organizers.”
  • “Create a CSV of free events in Chicago for next weekend.”

Tips

  • Start with maxItems between 25 and 100 to validate your query.
  • Use a city/category URL when you already know the exact AllEvents page you want.
  • Use keyword for focused lead-generation searches such as startup, fitness, or real estate.
  • Leave proxy settings disabled unless AllEvents blocks your environment.

Legality

This actor extracts publicly available event listing data. Use the results responsibly, respect AllEvents terms, and make sure your use case complies with applicable privacy, marketing, and data protection laws.

Limits and notes

  • The actor only extracts publicly available AllEvents listing data.
  • Availability and field completeness depend on what AllEvents exposes for each event.
  • Some events may not include price, currency, tickets, or organizer fields.
  • Date filters are passed to the source when supplied, but AllEvents may still rank or group events by its own relevance rules.

Support

If a run fails or the output looks wrong, use the Actor page to open an issue or report a bug. Include the run URL, input JSON, expected output, actual output, and one reproducible public AllEvents URL.

Common questions

Questions and answers reused from the canonical actor README.

Do I need an AllEvents account?

No. The actor works with public event listing pages.

Can I scrape one specific city?

Yes. Set city, or provide a city listing URL in startUrls.

Can I export to CSV or Excel?

Yes. Apify datasets can be downloaded as JSON, CSV, Excel, XML, RSS, and more.

What should I include in a support request?

Include the run ID or run URL, input JSON, expected output, actual output, and one reproducible public AllEvents URL.