AllEvents Events Scraper
Pricing
from $0.12 / 1,000 item extracteds
AllEvents Events Scraper
Export public AllEvents listings by city, category, keyword or listing URL, with event dates, venues, ticket links and available organizer information.
Pricing
from $0.12 / 1,000 item extracteds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
9
Total users
3
Monthly active users
15 days ago
Last modified
Categories
Features
Share
Export public AllEvents event listings by city, category, keyword, or city/category listing URL. AllEvents Events Scraper returns event titles, dates, venues, addresses, organizer names, interest counts and ticket links when available, ready for JSON, CSV or Excel export.
Use the dataset for local event research, newsletters, venue research and marketing. This is a listing-data tool, not an attendee/contact finder or an individual event-detail scraper. Optional fields can be empty.
Quick start
- Enter a city or paste a public AllEvents city/category listing URL. If using the form, remove its prefilled listing URL before choosing a different city.
- Start with a small result limit:
{"city": "new york","category": "all","maxItems": 25}
- Open the run's dataset and export the results. The limit applies across the whole run, not separately to each URL.
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
What you get
One row per saved public event, with its title and event link, plus available dates, venue, ticket and organizer information. Dates may be timestamps or source display text. Keep source URLs for manual checking, and leave missing optional fields unknown.
Who is it for?
- Local newsletter editors preparing event shortlists for a city audience.
- Community and business researchers reviewing events around a defined topic.
- Venue researchers organizing available venue and organizer names with public event links.
- Data teams combining public event exports with other sources in their own workflow.
How you can use the data
- Prepare a London business-event shortlist. Search London business events with the keyword
startupand a small result cap. Exporttitle,startDateTime,endDateTime,venueNameandeventUrl, then verify dates and ticket details before publishing a recommendation. - Build a New York music review sheet. Use the public city/music listing URL from the input example. Keep event links and venue addresses with each row so an editor can check whether an event fits their audience.
- Organize venue research. Group available
venueNameandvenueAddressvalues in your own spreadsheet, retaining the associatedeventUrl. Blank venue details remain unknown rather than implying an online event. - Compare public interest cautiously. Keep
interestedCountbeside the event and collection time as a source-reported signal. It is not an attendance total, ticket-sales count or organizer contact detail.
Input settings
Music listings by URL
{"startUrls": [{ "url": "https://allevents.in/new-york/music" }],"maxItems": 25}
Business events matching a keyword
{"city": "london","keyword": "startup","category": "business","maxItems": 20}
These are input recipes, not links to saved tasks. Use listing URLs, not individual event-detail URLs. Invalid, non-HTTP(S), credential-bearing or non-AllEvents URLs are skipped with a warning; valid URLs in a mixed batch are preserved. If all supplied URLs are invalid, the run succeeds with an empty dataset and an explanation in RUN_SUMMARY, without silently searching the default city.
More input
| Setting / API key | Purpose |
|---|---|
Listing URLs — startUrls | Public city/category pages. These take precedence over City. |
City — city | Location when no listing URL is supplied. |
Keyword — keyword | Search within the selected city/category. |
Category — category | Category slug. A non-all value overrides a URL's category. |
From / To date — fromDate, toDate | Optional valid YYYY-MM-DD dates passed to the source. |
Maximum events — maxItems | Total saved-event limit, from 1 to 10,000. |
Proxy configuration — proxyConfiguration | Optional explicit proxy settings. Details are in the input help. |
The form defaults to New York and 20 events, with a New York listing URL prefilled. Set the city and result limit explicitly in API requests. Provide at least one of startUrls, city, keyword or category. Keyword/category searches without a city use New York, not a worldwide search.
Output data
Each saved row represents one event. This abbreviated example illustrates the output shape only. It is not a fresh extraction result:
{"eventId": "example-id","title": "Example public event","eventUrl": "https://allevents.in/new-york/example-event/example-id","descriptionSnippet": "Example listing description.","startDateTime": "2026-11-01T18:00:00.000Z","endDateTime": null,"venueName": null,"venueAddress": null,"city": "New York","price": null,"currency": null,"interestedCount": null,"imageUrl": null,"organizerName": null,"category": null,"tags": [],"ticketUrl": null,"latitude": null,"longitude": null,"sourceUrl": "https://allevents.in/new-york/all","scrapedAt": "2026-10-24T10:00:00.000Z"}
| Fields | Meaning |
|---|---|
eventId, eventUrl, title | Source identifier, public event URL and title. |
descriptionSnippet | Available short listing description, not guaranteed full event text. |
startDateTime, endDateTime | ISO timestamps when source numeric times are available. Otherwise source display text or null. |
venueName, venueAddress, city | Available venue and city information. |
price, currency, ticketUrl | Published ticket details. Price is source text, not a normalized numeric amount. |
organizerName, interestedCount | Available organizer name and public interest count, not contact details or attendance totals. |
category, tags | Source category and labels. |
imageUrl, latitude, longitude | Available event image and venue coordinates. |
sourceUrl, scrapedAt | Listing page used and collection timestamp. |
Optional values may be null and tags may be empty. No output sorting option is provided. Results follow the source's ordering rather than a guaranteed chronological order.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
This Actor uses pay-per-event pricing: start is charged once after input validation, before listing requests, and item is charged for each saved event row. An empty search saves no item rows, but the start charge can still apply.
Use maxItems to bound saved results. The form defaults to 20, and the accepted range is 1–10,000. A larger limit does not guarantee enough matching events or complete collection.
See the live Pricing tab for current rates and plan discounts.
Tips for best results
- Clear the prefilled listing URL when using City. Otherwise the URL takes precedence over the city field.
- Check dates before building a calendar. Date preferences go to AllEvents, while results can retain the source's ranking or grouping.
- Keep original event links for editorial checks. Confirm current dates, venue and ticket terms before recommending an event.
- Review
RUN_SUMMARYwith the dataset. Check partial status and request or item errors before treating a search as complete.
Limits and caveats
Listing URLs take precedence over City. With multiple listing URLs, the total result limit is shared and earlier URLs can use it up. Individual event-detail pages are not a supported input mode.
Price, tickets, organizer information, dates and other optional details depend on the listing. No login, private attendee data or organizer email extraction is provided. Interest counts are not attendance totals, and source price text is not a normalized amount.
RUN_SUMMARY in the run's key-value store records saved counts, request/item errors and PARTIAL status. A run can preserve useful results when another listing fails. A completed search with no matches can succeed empty. Requests failing with no saved events fail the run.
Source restrictions, available listings and the run time limit can reduce results. Dates can be source display text or null, and result ordering is not guaranteed to be chronological.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~allevents-events-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \--data @- <<'JSON'{"city": "new york","category": "all","maxItems": 25}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
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/allevents-events-scraper').call(run_input={'city': 'new york', 'category': 'all', 'maxItems': 25})print(client.dataset(run['defaultDatasetId']).list_items().items)
MCP and AI agents notes
Start with {"city":"london","category":"business","maxItems":10}. Retrieve items from the completed run's defaultDatasetId. Inspect optional fields and partial status before summarizing results. This Actor returns event listings, not bookings or attendee contacts.
MCP and AI agents
You can ask your AI assistant to collect data with AllEvents Events Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's AllEvents Events Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/allevents-events-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use AllEvents Events Scraper by Fetch Cat, or give it the identifier fetch_cat/allevents-events-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s AllEvents Events Scraper to collect up to 5 London business events matching startup. Show titles, dates, venues and original event links for an editorial shortlist.”
- “Collect at most 5 events from the public New York music listing URL I provide. Keep ticket links and date text as supplied, marking details I should verify before publishing.”
- “Collect a small sample of 5 London business events. Make a venue research table with venue addresses, organizer names and event links where available, and keep public interest counts separate from attendance claims.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Can I export AllEvents data to CSV or Excel?
Yes. Download the run's dataset in CSV, Excel or JSON from Apify, or retrieve it through the API.
Is this an AllEvents API alternative?
It provides structured public listing data through Apify's API and MCP integration. It is not an official AllEvents API and does not provide account, booking or private attendee features.
Do I need an AllEvents account?
No. The Actor collects public listings without an AllEvents login.
Why are fields missing or results empty?
Listings do not always publish every field. A completed query can have no matches. Check the input location, date filters and RUN_SUMMARY. A failed run or partial status is different from a completed empty search.
Related Actors
- Meetup Events Scraper — Discover listings on another events platform.
- Eventbrite Events Scraper — Research Eventbrite listings.
- Facebook Events Scraper — Collect available public Facebook event information.
- Google Maps Places Scraper — Research venues and local places.
- Google Maps Email Extractor & Lead Finder — Build a complementary local-business prospecting workflow.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥