AllEvents Scraper
Pricing
Pay per event
AllEvents Scraper
Extract AllEvents event listings with dates, venues, addresses, interest counts, images, descriptions, and ticket links from public pages.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Stas Persiianenko
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
2
Monthly active users
12 days ago
Last modified
Categories
Share
Extract public event listings from AllEvents city, category, search, and event detail pages.
What does AllEvents Scraper do?
AllEvents Scraper turns public AllEvents pages into structured event records.
It reads listing pages such as https://allevents.in/new-york/all, follows event links when enrichment is enabled, and saves clean dataset rows with dates, venues, ticket links, images, descriptions, and interest counts.
Who is it for?
- ๐๏ธ Event marketers monitoring local calendars.
- ๐๏ธ Tourism teams building city event feeds.
- ๐ฃ Agencies finding sponsorship and partnership opportunities.
- ๐งฒ Lead generation teams prospecting organizers and venues.
- ๐ฐ Publishers creating weekly event roundups.
- ๐งช Data teams comparing event availability across cities.
Why use this actor?
AllEvents pages are useful but not ideal for spreadsheets or automated workflows. This actor extracts event cards and JSON-LD detail data into a dataset that can be exported to CSV, JSON, Excel, Google Sheets, or your own API pipeline.
What data can you extract?
| Field | Description |
|---|---|
eventId | AllEvents numeric event identifier when available |
title | Event title |
url | Canonical event URL |
startDate | ISO start date from detail JSON-LD |
endDate | ISO end date when present |
dateText | Human-readable listing date |
venueName | Venue or place name |
streetAddress | Street address from detail pages |
city | Event city |
region | State or region |
country | Country code or name |
latitude / longitude | Geo coordinates when AllEvents exposes them |
organizerName | Organizer or host name when available |
ticketUrl | Ticket or registration link when present |
priceText | Price label or free indicator |
interestedCount | Count parsed from interested/going text |
imageUrl | Event image or banner |
description | Detail-page description |
sourceUrl | Input page that produced the record |
scrapedAt | Timestamp of extraction |
How much does it cost to scrape AllEvents events?
The actor uses pay-per-event pricing.
You pay a small $0.005 start fee for each run and then a per-record event charge for each saved event.
The default Free-tier item price is $0.0000575 per event, with lower per-event prices on paid Apify plans.
| Example run | Events saved | Estimated Free-plan cost |
|---|---|---|
| Trial city scan | 20 events | $0.0062 |
| Weekly category monitor | 100 events | $0.0108 |
| Larger city export | 1,000 events | $0.0625 |
Formula: $0.005 start + events ร $0.0000575 on the Free plan.
That means the Apify Free plan can usually cover many small test runs; for example, roughly 160 trial runs of 20 events or about 150,000 saved events before Apify platform usage limits and any proxy costs are considered.
Use a small maxItems value for trial runs, then increase the limit for production feeds.
Input options
| Input | Type | Default | Notes |
|---|---|---|---|
startUrls | array | New York all-events page | City, category, search, or event URLs |
maxItems | integer | 20 | Maximum records across all starts |
includeDetails | boolean | true | Fetch event detail pages for richer fields |
proxyConfiguration | object | optional | Use Apify Proxy only if needed |
How to scrape a city page
- Open the actor on Apify.
- Add an AllEvents city URL, for example
https://allevents.in/new-york/all. - Keep
includeDetailsenabled for addresses and descriptions. - Set
maxItemsto a small number for the first run. - Start the actor.
- Download the dataset from the Storage tab.
How to scrape category pages
Use any public AllEvents category or filtered listing URL as a start URL.
The actor detects event cards on the page and saves event records until maxItems is reached.
How to scrape event detail URLs
You can paste direct event URLs too. When a start URL is already an event page, the actor extracts the JSON-LD event object and saves one enriched record.
Output example
{"eventId": "2400028937718757","title": "Phish at Madison Square Garden","url": "https://allevents.in/new-york/phish-at-madison-square-garden/2400028937718757","startDate": "2026-07-22T19:30:00-05:00","venueName": "Madison Square Garden","city": "New York","country": "US","interestedCount": 12,"sourceUrl": "https://allevents.in/new-york/all"}
Tips for better results
- โ Start with one city or category page.
- โ
Keep
maxItemslow during setup. - โ Enable detail fetching when you need addresses, coordinates, and descriptions.
- โ Disable detail fetching for faster lightweight listing scans.
- โ Use specific category URLs when you need niche events.
Integrations
Use this actor to feed:
- CRM lead lists for venue and organizer outreach.
- City guides and local newsletters.
- Sponsorship prospecting dashboards.
- Event monitoring spreadsheets.
- Content calendars for social media teams.
- Internal data warehouses via Apify webhooks.
API usage with Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/allevents-scraper').call({startUrls: [{ url: 'https://allevents.in/new-york/all' }],maxItems: 20,includeDetails: true});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
API usage with Python
from apify_client import ApifyClientimport osclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('automation-lab/allevents-scraper').call(run_input={'startUrls': [{'url': 'https://allevents.in/new-york/all'}],'maxItems': 20,'includeDetails': True,})items = client.dataset(run['defaultDatasetId']).list_items().itemsprint(items)
API usage with cURL
curl "https://api.apify.com/v2/acts/automation-lab~allevents-scraper/runs?token=$APIFY_TOKEN" \-H 'Content-Type: application/json' \-d '{"startUrls":[{"url":"https://allevents.in/new-york/all"}],"maxItems":20,"includeDetails":true}'
MCP usage
Connect the actor to Claude through Apify MCP:
https://mcp.apify.com/?tools=automation-lab/allevents-scraper
Claude Code CLI setup:
$claude mcp add apify-allevents "https://mcp.apify.com/?tools=automation-lab/allevents-scraper"
Claude Desktop JSON config:
{"mcpServers": {"apify-allevents": {"url": "https://mcp.apify.com/?tools=automation-lab/allevents-scraper"}}}
Example prompts:
- "Scrape 20 New York AllEvents listings and summarize the most common venues."
- "Find free public events from this AllEvents category URL."
- "Create a CSV-ready list of upcoming event titles, dates, venues, and ticket links."
Data quality notes
AllEvents exposes more fields for some events than others.
Listing pages usually include title, URL, venue, date text, image, and interest count.
Detail pages often add structured start dates, full address, coordinates, and descriptions.
Optional fields may be null when the source page does not publish them.
Performance notes
The actor uses HTTP requests and Cheerio parsing, not a browser.
This keeps runs lightweight and cost-efficient.
For fastest runs, set includeDetails to false.
For richest data, keep includeDetails true.
Proxy notes
AllEvents public pages usually work without a proxy or with standard Apify datacenter proxy settings. If your location is blocked, configure Apify Proxy in the advanced input section. Residential proxies are not the default recommendation.
Legality
This actor extracts publicly available information from public AllEvents pages. You are responsible for using the data in accordance with applicable laws, AllEvents terms, and privacy rules. Avoid collecting personal data unless you have a lawful basis and a legitimate use case.
FAQ
Why did I get fewer events than maxItems?
The source page may have fewer visible event cards, or duplicate events may have been skipped. Try another city/category page or increase the source coverage with more start URLs.
Why are some fields empty?
Some AllEvents records do not publish every field.
Enable includeDetails to get the richest available data from event detail pages.
Can I scrape multiple cities?
Yes. Add multiple AllEvents city URLs to startUrls and set a higher maxItems limit.
Does it require login?
No. The actor is designed for public pages that can be viewed without an AllEvents account.
Troubleshooting
If a run returns no items, check that the start URL is a public AllEvents listing or event URL.
If a run is slow, lower maxItems or disable detail fetching.
If requests are blocked, enable Apify Proxy and retry with a small limit.
Related scrapers
- https://apify.com/automation-lab/10times-events-scraper
- https://apify.com/automation-lab/eventbrite-scraper
- https://apify.com/automation-lab/google-maps-reviews-scraper
- https://apify.com/automation-lab/website-emails-scraper
Changelog
Initial version extracts AllEvents listing cards and event detail JSON-LD into structured event records.
Support
Open an Apify issue if you find a public AllEvents page that the actor cannot parse. Include the start URL, run ID, and a short description of the expected events.
Storage
Results are written to the default Apify dataset. You can export them as JSON, CSV, XML, RSS, Excel, or HTML from Apify Storage.
Reliability checklist
The actor skips duplicate event URLs. It keeps partial listing data if an individual detail page fails. It records the original source URL for each item. It uses clear null values for unavailable fields.
Version
Current build: 0.1.