Partiful Events Scraper

Turn public Partiful city calendars and event pages into clean, structured event data. Collect titles, schedules, venues, hosts, cover images, map links, and attendance signals without logging in.

Use the results for event discovery, local market research, community intelligence, lead generation, or recurring calendar monitoring. The Actor uses lightweight HTTP requests, deduplicates events by ID, and supports optional detail enrichment.

What does Partiful Events Scraper do?

• Discovers public events from Partiful Explore city pages.
• Extracts one specific public event from an event URL.
• Returns event dates with the source timezone.
• Captures venues, addresses, neighborhoods, and Google Maps links.
• Exports interested, going, approved, maybe, and waitlist counts when Partiful exposes them.
• Optionally visits each detail page for more complete records.
• Deduplicates events found in more than one source.

Who is it for?

Event marketers can identify active communities and upcoming sponsorship opportunities.

Local lead-generation teams can build prospect lists of event hosts and venues.

Event aggregators can refresh Partiful listings on a schedule.

Community intelligence teams can compare event activity and visible attendance across cities.

Researchers and developers can consume normalized Partiful event JSON instead of maintaining a parser.

Why use this Partiful event extractor?

Partiful pages are designed for people, not spreadsheets. This Actor converts embedded public page data into stable dataset rows that can be exported to JSON, CSV, Excel, XML, RSS, or Parquet.

HTTP-first extraction keeps runs fast and inexpensive. A single run can combine Explore and event URLs while event-ID deduplication prevents duplicate records.

What Partiful event data can I extract?

Field	Meaning
eventId	Stable Partiful event ID
url	Canonical public event URL
eventTitle	Event title
eventDescription	Public event description
startDate, endDate	ISO schedule values
timezone	Event timezone
venueName, address	Venue and formatted address
neighborhood	Neighborhood when available
googleMapsUrl	Direct map search link
hostName, hostIds	Public host information
imageUrl	Cover image URL
guest count fields	Visible attendance breakdowns
status, isPublic	Publication state
sourceUrl, scrapedAt	Provenance and freshness

Optional fields are omitted when Partiful does not expose them.

How much does it cost to scrape Partiful events?

The Actor uses pay-per-event pricing: a small start charge plus a charge for each saved event. The BRONZE rate is $0.000028634 per event, with automatic volume discounts on higher Apify plans. Final live prices are displayed before every run.

You pay for records saved, not pages with no usable event data. Leave detail enrichment disabled for the cheapest discovery workflow.

Quick start

1. Open the Actor input page.
2. Keep the prefilled NYC Explore URL or add your own Partiful URLs.
3. Choose a maximum number of events.
4. Enable detail enrichment only if needed.
5. Click Start.
6. Export the resulting dataset in your preferred format.

Input

{
  "startUrls": [
    { "url": "https://partiful.com/explore/nyc" },
    { "url": "https://partiful.com/e/x82ndPsPYCo1qWGuSMUo" }
  ],
  "maxItems": 100,
  "enrichDetails": false
}

startUrls accepts Partiful /explore/{city} and /e/{eventId} URLs. maxItems is a run-wide unique-event limit from 1 to 10,000.

Discovery versus detail enrichment

Explore pages already expose useful event fields and are the recommended low-cost mode. Set enrichDetails to true when detail pages may contain richer descriptions or locations.

If one detail request fails, the Actor logs a warning and keeps the discovery record. This makes scheduled collection resilient to isolated event-page changes.

Output example

{
  "eventId": "x82ndPsPYCo1qWGuSMUo",
  "url": "https://partiful.com/e/x82ndPsPYCo1qWGuSMUo",
  "eventTitle": "Abbode Sample Sale",
  "eventDescription": "Shop the latest collection at this public sample sale.",
  "startDate": "2026-07-15T15:00:00.000Z",
  "timezone": "America/New_York",
  "address": "108 Madison St, New York, NY 10002",
  "isPublic": true,
  "sourceUrl": "https://partiful.com/e/x82ndPsPYCo1qWGuSMUo",
  "scrapedAt": "2026-07-13T00:00:00.000Z"
}

Scheduling and monitoring

Create an Apify schedule to refresh city calendars daily or weekly. Store each run in a downstream database and compare event IDs, dates, status, or guest counts to detect additions and changes.

For stable monitoring, keep the same source URLs and avoid changing enrichment settings between runs.

Event lead-generation workflow

1. Scrape one or more city Explore pages.
2. Filter upcoming events by neighborhood or attendance.
3. Review venue and public host fields.
4. Enrich only shortlisted event URLs.
5. Send qualified records to a CRM or spreadsheet.

Public event data is not consent to contact people. Apply your own legal basis and outreach rules.

Integrations

Connect datasets to Google Sheets for editorial calendars, Airtable for event operations, Make or Zapier for notifications, and Slack for daily digests.

Use Apify webhooks to trigger a workflow when a run succeeds. Use dataset API endpoints to load records into warehouses, BI tools, or custom event products.

API usage

Run the Actor from JavaScript, Python, cURL, the Apify Console, or MCP. The API examples below use the stable automation-lab/partiful-events-scraper identifier.

JavaScript API example

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/partiful-events-scraper').call({
  startUrls: [{ url: 'https://partiful.com/explore/nyc' }],
  maxItems: 100,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python API example

from apify_client import ApifyClient
client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/partiful-events-scraper').call(run_input={
    'startUrls': [{'url': 'https://partiful.com/explore/nyc'}],
    'maxItems': 100,
})
items = client.dataset(run['defaultDatasetId']).list_items().items

cURL API example

curl -X POST "https://api.apify.com/v2/acts/automation-lab~partiful-events-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"startUrls":[{"url":"https://partiful.com/explore/nyc"}],"maxItems":100}'

Poll the returned run ID or use an Apify webhook, then fetch items from the run's default dataset.

Use with Apify MCP

Connect AI assistants through this actor-specific Streamable HTTP endpoint:

https://mcp.apify.com?tools=automation-lab/partiful-events-scraper

For Claude Code, register it from a terminal:

$claude mcp add --transport http partiful-events "https://mcp.apify.com?tools=automation-lab/partiful-events-scraper"

For Claude Desktop, open Settings → Connectors → Add custom connector, paste the endpoint above, and complete the Apify sign-in. For Claude Desktop installations that expose JSON configuration, Cursor (.cursor/mcp.json), or VS Code (mcp.json), use:

{
  "mcpServers": {
    "partiful-events": {
      "url": "https://mcp.apify.com?tools=automation-lab/partiful-events-scraper"
    }
  }
}

Restart the client after saving the JSON. The first connection opens Apify authentication; approve it before running the Actor.

Example prompts:

• “Find upcoming public Partiful events in NYC and group them by neighborhood.”
• “Extract this Partiful event and summarize its schedule, venue, and visible demand.”
• “Compare visible attendance signals in this week's event dataset.”

Tips for reliable runs

• Use canonical https://partiful.com URLs.
• Combine city pages when you need more than one local market.
• Keep enrichment off for broad discovery.
• Set maxItems close to the volume you actually need.
• Schedule moderate refresh intervals rather than repeatedly scraping unchanged pages.
• Preserve eventId as the primary key in downstream systems.

Limitations

The Actor extracts public data embedded in Partiful pages. Private, invite-only, login-gated, or hidden guest information is not accessible.

Explore coverage and payload shape are controlled by Partiful and may change. A city Explore page can contain fewer events than maxItems. Guest counts appear only when the event exposes them.

The Actor does not RSVP, message hosts, bypass access controls, or retrieve private attendee identities.

Legality

Is it legal to scrape Partiful events?

Public event facts can often be collected for legitimate purposes, but laws and website terms vary by jurisdiction and use case. Only collect data you are authorized to use. Avoid personal-data profiling, spam, harassment, and attempts to access private events.

You are responsible for retention, outreach, privacy, and compliance decisions in downstream workflows.

Troubleshooting

Why did the run save fewer events than maxItems? The source pages contained fewer unique public event IDs. Add another city Explore URL or event URLs.

Why is a venue or count missing? Partiful did not expose that optional value on the source page. Try detail enrichment.

Why was my URL rejected? Only Partiful Explore city and public event URL patterns are accepted. Remove tracking redirects and use the canonical URL.

Why did a detail warning appear? One enrichment request failed. The Actor keeps the discovery record rather than losing the event.

FAQ

Does it require a Partiful account?

No. The Actor reads anonymously accessible public pages.

Can I scrape one event?

Yes. Provide its /e/{id} URL and set maxItems to 1.

Can I scrape multiple cities?

Yes. Add several Explore URLs to startUrls; duplicate events are merged by ID.

Does it reveal guest identities?

No. It exports public aggregate counts where available, not hidden attendee lists.

Can I export to Excel or CSV?

Yes. Use the dataset Export menu or API format parameter.

Related scrapers

Explore more event and lead-generation tools from Automation Labs. Combine this Actor with public website contact extractors, geocoders, or calendar-processing Actors when those workflows have an appropriate legal basis.

Support

If a valid public Partiful URL stops producing expected records, open an Actor issue with the URL, run ID, expected result, and a short description. Do not include private invitation links, credentials, or personal information.