Partiful Events Scraper

Scrape public Partiful events by city and export Partiful data to CSV, JSON, or spreadsheet files for research, planning, and market analysis. This actor is a Partiful API alternative for discovering public event listings without signing in.

What data can you extract from Partiful?

Each dataset row represents one public event. The event listing supplies the initial fields; enabling full details adds the public host cards, event timestamps, and RSVP totals from the event page. The output uses stable camelCase names and preserves unavailable optional values as null.

Field	Description	Example
id	Unique identifier for the public event.	B9X0Wtx8YG2XNpRb6Teh
url	Canonical public event page.	https://partiful.com/e/B9X0Wtx8YG2XNpRb6Teh
shortUrl	Share link when the event page provides one.	https://go.partiful.com/1ypqkHeW
title	Event title as displayed in the listing.	Halloween in Brooklyn
description	Public event description, including line breaks where present.	Expect two distinct atmospheres...
city	Full city name corresponding to the requested city slug.	New York City
location	Public venue or address assembled from the event’s displayed address.	20 W 29th St, New York, NY
neighborhood	Neighborhood shown with the event location, when available.	Midtown West
startDate	Start date and time in ISO 8601 UTC format.	2026-11-01T02:00:00.000Z
endDate	End date and time in ISO 8601 UTC format; may be null.	2026-11-01T09:00:00.000Z
timezone	Event’s local timezone identifier.	America/New_York
status	Lowercase publication state.	published
isPublic	Whether the event is marked public.	true
visibility	Visibility value returned by the event page.	public
guestCount	Sum of the available going, interested, maybe, declined, and waitlist counts.	0
goingCount	Number of guests marked as going.	0
interestedCount	Number of guests marked as interested.	0
maybeCount	Number of guests marked as maybe.	0
declinedCount	Number of guests who declined, when that count is available.	0
waitlistCount	Number of guests on the waitlist.	0
attendedCount	Attendance count when the public event data includes it.	null
hosts	Public host cards, including the displayed name, profile identifier, profile link, and photo URL where available.	One or more public host cards
theme	Event page theme setting.	slate
effect	Event page visual effect setting.	handprints
titleFont	Event title font setting, when specified.	null
coverImageUrl	Public cover image URL, when supplied.	https://firebasestorage.googleapis.com/...
publishedAt	Event publication timestamp when supplied.	2026-10-12T19:33:23.383Z
createdAt	Event creation timestamp when supplied.	2026-10-12T19:33:23.383Z
updatedAt	Event’s last update timestamp when supplied.	2026-10-25T16:31:25.305Z
tags	Explore categories attached to the event card.	[]
scrapedAt	UTC timestamp when the actor created the output record.	2026-10-25T16:33:15.235Z

The event page does not expose a guest list through this actor. Guest totals are aggregate values only. A count of zero is retained when the public page returns zero; null means the source did not supply that field.

How to scrape Partiful

1. Select one or more supported city slugs, or keep the default cities.
2. Set the maximum number of events to collect per city. The allowed range is 1 to 500.
3. Choose whether to open each event page for host profiles and additional details.
4. Start the run and review the event rows in the dataset.
5. Export the dataset as JSON, CSV, or a spreadsheet file for downstream analysis.

The actor reads event cards from public city explore pages. It removes duplicate event identifiers when an event appears in more than one explore section. With full details enabled, each event is checked against its public event page before the result is written.

Input

Parameter	Type	Default	Description
cities	array of strings	["nyc"]	City slugs to collect: nyc, la, sf, bos, dc, chi, lon, mia, or atx.
maxEventsPerCity	integer	50	Maximum unique events to return per city, between 1 and 500.
fetchEventDetails	boolean	true	Open each event page for host cards, RSVP totals, and timestamps. Turn off for faster listing-only runs.
proxyConfiguration	object	platform default	Optional proxy settings. Leave the default unless a run needs a specific proxy configuration.

Example input for two cities:

{
  "cities": ["nyc", "la"],
  "maxEventsPerCity": 50,
  "fetchEventDetails": true
}

For a large collection, request one city at a time and keep a practical per-city cap. The public explore feed contains a limited set of featured sections, so asking for 500 does not guarantee 500 events from every city.

Output example

This is a real event record from the golden run. The description is shortened here; the dataset retains the full public text.

{
  "id": "tdWKXXnFRQqtuxOcPz5e",
  "url": "https://partiful.com/e/tdWKXXnFRQqtuxOcPz5e",
  "shortUrl": "https://go.partiful.com/xx3t3nZa",
  "title": "Halloween in Brooklyn",
  "description": "free + diy vibes with midwest emo on aux! respect this space & show up on time! ...",
  "city": "New York City",
  "location": "234 6th St, Brooklyn, NY",
  "neighborhood": "Gowanus",
  "startDate": "2026-10-31T22:00:00.000Z",
  "endDate": null,
  "timezone": "America/New_York",
  "status": "published",
  "isPublic": true,
  "visibility": "public",
  "guestCount": 1220,
  "goingCount": 836,
  "interestedCount": 209,
  "maybeCount": 175,
  "declinedCount": 0,
  "waitlistCount": 0,
  "attendedCount": 836,
  "hosts": [
    {
      "name": "doolittle",
      "id": "nI7omWwvRobNttRDQuWV",
      "profileUrl": "https://partiful.com/u/nI7omWwvRobNttRDQuWV",
      "photoUrl": "https://firebasestorage.googleapis.com/v0/b/getpartiful.appspot.com/o/profileImages%2FN8N9cyiM5xSfXFcwK7bdh?alt=media&token=5b474d1b-cfb0-4756-a778-e7190967105c"
    }
  ],
  "theme": "oxblood",
  "effect": "none",
  "titleFont": null,
  "coverImageUrl": "https://firebasestorage.googleapis.com/v0/b/getpartiful.appspot.com/o/external%2Fuser%2FnI7omWwvRobNttRDQuWV%2FlSCZACJPSHt5ua-mpgbIj?alt=media&token=a1a8149e-3bcf-4e0a-9676-f042e42b4eac",
  "publishedAt": "2026-10-11T17:31:45.564Z",
  "createdAt": "2026-10-11T17:31:45.564Z",
  "updatedAt": "2026-10-25T16:31:58.969Z",
  "tags": [],
  "scrapedAt": "2026-10-25T16:33:14.678Z"
}

Use cases

• Event marketers can compare public event themes, locations, and attendance signals across supported cities before planning a launch or campaign.
• Venue teams can review which neighborhoods and venue types appear in public listings and use that information when building local calendars.
• Community organizers can discover public meetups and recurring event formats that may be relevant to a city or interest area.
• Researchers can create time-stamped snapshots of event titles, schedules, locations, and visible RSVP counts for trend analysis.
• Local media teams can assemble public event calendars and export the records for editorial review.
• Product teams can use public listings as a source for event discovery prototypes, geographic analysis, or a city guide.

The actor is designed for collection and analysis of public event pages. It does not sign in, submit RSVPs, contact hosts, or retrieve guest names.

How much does it cost to scrape Partiful?

The actor is configured at $2.40 per 1,000 event results. The cost is based on records delivered, not the number of event-page requests. Routine platform usage is included in the pay-per-result estimate; a proxy escalation or unusual run can affect the actual run experience.

Results	Estimated result charge
1,000 events	$2.40
5,000 events	$12.00
25,000 events	$60.00

The fast mode still returns one paid result per event; it lowers the number of page requests by skipping event detail pages. If the selected city has fewer public cards than the requested cap, the actor returns the available unique events and charges only for records delivered.

Tips for best results

• Start with one city and a cap of 30 to confirm the response volume and field coverage for your topic.
• Use the supported short slugs exactly as listed in the input description. The actor rejects unknown slugs with a clear error.
• Keep full details enabled when host profile links, profile images, event timestamps, or detailed RSVP counts matter to your workflow.
• Disable full details when you only need titles, descriptions, dates, locations, themes, and explore categories. Listing cards are collected from one city page request.
• Raise maxEventsPerCity only when the selected city’s public feed has enough unique cards. The cap limits collection; it does not create additional pages or expand the site’s featured feed.
• Select fewer cities for a faster run. The actor visits one listing page for each city and, in full mode, requests the public event page for each selected event.
• Deduplicate across multiple runs using id. An event can appear in more than one explore section and may be returned again in a later run.
• Treat scrapedAt as the collection timestamp. Event dates are source values and use the event’s timezone field for local interpretation.
• Preserve null values when importing data. They indicate that a public page did not provide the value and are different from a zero count or an empty string.
• Use city and startDate when building a calendar view. The timestamp is expressed in UTC, while timezone identifies the local event zone.

Limits

Partiful’s public city pages present selected explore sections rather than a complete searchable event archive. The number of unique events varies by city and changes as listings are published or removed. Large caps therefore return up to the available unique events, not a guaranteed number.

Some supported regions have much smaller public feeds than the largest cities. During verification, the Los Angeles and San Francisco pages exposed many section cards, while the London and Miami feeds were smaller. The feed is live and can change, so these observations are not fixed city totals.

Full details are retrieved from each event page. Events can change or disappear between the explore request and the detail request. When a detail page cannot be read, the actor retains the public listing fields and uses null or partial values for detail-only fields. Host photos, end times, attendance, RSVP categories, and theme settings are not available for every event.

RSVP counts are aggregate public fields. The actor does not extract guest lists or personal contact details. Count visibility and completeness are controlled by each event’s public page; an empty or zero value should not be interpreted as proof that no one will attend.

The actor only targets public events available from the supported city pages. It does not access invitation-only events, account data, private event pages, or sign-in protected records. It does not apply keyword or date filters that the public explore page does not expose.

The public pages returned successfully during verification without an interstitial challenge. Site access rules and anti-bot behavior can change. The actor uses the configured proxy route and can retry through an alternate proxy route if the initial request is blocked; this does not guarantee that every future page will be accessible.

Use with AI agents (MCP)

Add this actor to any MCP client (Claude, Cursor, VS Code, n8n and others) with one URL:

https://mcp.apify.com?tools=mlg14/partiful-scraper

The actor returns one dataset item per public event (title, start and end time, location, RSVP counts, hosts, URL). Keep results bounded with maxEventsPerCity.

Prompt 1: "What public Partiful events are happening in New York City?"

{
  "cities": [
    "nyc"
  ],
  "maxEventsPerCity": 30,
  "fetchEventDetails": true
}

Prompt 2: "Compare upcoming Partiful events in San Francisco and Los Angeles, listing only."

{
  "cities": [
    "sf",
    "la"
  ],
  "maxEventsPerCity": 20,
  "fetchEventDetails": false
}

Prompt 3: "Which London Partiful events have the most people going?"

{
  "cities": [
    "lon"
  ],
  "maxEventsPerCity": 40,
  "fetchEventDetails": true
}

FAQ

Is it legal to scrape Partiful events?

This actor reads public event pages only. You are responsible for reviewing the site’s terms, following applicable privacy and data-protection laws, and using the output for a lawful purpose. Do not use public host details to harass, spam, or profile individuals.

Do I need a proxy?

No special proxy input is needed for typical runs. The default proxy configuration is used automatically. If public pages begin returning blocks or timeouts, retry later or configure an appropriate proxy setting. Proxy routing cannot bypass sign-in or private-event restrictions.

How fast is a run?

Listing-only mode makes roughly one explore-page request per selected city, then writes the available records. Full-detail mode also visits the selected event pages, with a small number of requests in parallel. Run time depends on city count, event cap, response time, and any retries.

Can I schedule or monitor collection?

Yes. Save the input as a task or schedule recurring runs, then compare datasets by id and scrapedAt. A recurring job is useful for tracking changing public listings, but each run is a snapshot rather than a complete event-history feed.

Can I export to a spreadsheet?

Yes. Export the default dataset as CSV or a spreadsheet-compatible file, or retrieve JSON for a data pipeline. The output columns are stable and use camelCase field names.

Why is a field empty?

Some event pages omit fields such as endDate, attendedCount, host photos, or theme settings. The actor preserves unavailable values as null. RSVP fields can also be zero when the page reports zero; check the raw value before treating it as missing.

Why did I receive fewer events than maxEventsPerCity?

The limit is a maximum, not a promise. Explore pages have a finite set of public sections, and smaller regions may offer fewer unique events. Duplicate cards are removed before the per-city limit is applied.

Integrations

Use the actor API to start a run and retrieve its dataset, send completion webhooks to downstream services, or connect the output to workflow automation and spreadsheet connectors. Scheduled runs can feed a database or event calendar, while JSON and CSV exports work with common reporting tools.

Support

Open an issue on the Issues tab; we reply within 24h and add fields on request.