Partiful Scraper: Events, Cities & Organizers avatar

Partiful Scraper: Events, Cities & Organizers

Pricing

from $1.70 / 1,000 event or organizer saveds

Go to Apify Store
Partiful Scraper: Events, Cities & Organizers

Partiful Scraper: Events, Cities & Organizers

Find public Partiful events in nine cities or extract event and organizer URLs. Filter by local date, keyword and going count. Export schedules, venues, hosts and public RSVP counts as JSON/CSV. No login required.

Pricing

from $1.70 / 1,000 event or organizer saveds

Rating

0.0

(0)

Developer

Software Production Labs

Software Production Labs

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

Find public Partiful events for local newsletters, event calendars, venue research and community discovery. Supply cities or Partiful event/organizer URLs and get structured records with source links. No Partiful login, cookies or external API subscription is required.

Quick start

Collect five detailed New York events:

{"cities":["nyc"],"maxItems":5,"getEventDetails":true}

Filter a city snapshot for a newsletter:

{"cities":["London"],"keyword":"music","startDateFrom":"2026-09-11","startDateTo":"2026-09-30","maxItems":20,"maxRequests":200}

Change the example dates for your run. Date filters use each event's published timezone. The end date is inclusive. Keyword matching checks title, description and venue; it does not perform a platform-wide search.

Extract a public event directly:

{"urls":["https://partiful.com/e/QaHfjVa0FI6sWdWYlZdI"],"maxItems":1}

Extract a public organizer and its published event snapshot:

{"urls":["https://partiful.com/u/2KgDoRZix3CnC9fcdYUz"],"includeHostEvents":true,"maxItems":20}

Use includeHostEvents: false to return only the organizer. Date and attendance filters exclude organizer records; keyword filtering checks their name and public bio.

Cities and URLs

Nine public Explore cities: New York (nyc), Los Angeles (la), San Francisco (sf), Boston (bos), Washington DC (dc), Chicago (chi), London (lon), Miami (mia), Austin (atx). City names and slugs both work. cities: ["all"] visits all nine, subject to your result/request limits.

Supported URLs: /explore, /explore/city, /e/eventID, and /u/hostID on https://partiful.com. Up to 50 URLs. Query tracking parameters are removed. Tagged Explore URLs, short links and unsupported cities produce a clear input error. API callers may use startUrls with URL strings or { "url": "..." } objects as an alternative to urls.

What you get

One dataset row per distinct event or organizer, with recordType distinguishing them.

Event fieldsMeaning
id, sourceUrl, discoveredFromStable event ID, canonical source and discovery page
title, descriptionPublished event text
startDate, endDate, timezone, localStartDateSource timestamps and calendar date in the event's timezone
city, region, venueName, addressLines, neighborhoodDiscovery city and displayed venue information where available
goingGuestCount, approvedGuestCount, interestedGuestCount, maybeGuestCount, waitlistGuestCountSeparate public counters; hidden/missing counts are null
hostsPublic host names, profiles, public bios and photo links, when full details expose them
status, rsvpsEnabled, atCapacityPublic status and RSVP flags, when provided
coverImageUrl, shortUrl, publishedAt, updatedAtPublished metadata where available
placementsDiscovery sections and positions on the fetched page; not a global ranking
coverage, schemaVersion, retrievedAtListing/detail level, schema version and extraction timestamp

Organizer rows include id, sourceUrl, name, public bio, photoUrl and isManaged. Missing optional values remain null. Source timestamps are preserved. An explicit event URL has no inferred discovery city.

getEventDetails: false returns faster city/organizer listing snapshots. Direct event URLs always fetch details. Full-detail failures are reported instead of silently substituting incomplete records.

Controls and cost

InputDefaultLimit
maxItems201–1,000 total saved records
maxRequests1001–1,100 page requests
getEventDetailstrueEnrich discovered events
includeHostEventstrueInclude published organizer-page events
keywordnoneCase-insensitive phrase
startDateFrom, startDateTononeInclusive event-local start date
minGoing0Filter guests marked going; zero disables

Base price: $2.00 per 1,000 saved results, plus $0.00025 per GB for Actor start (minimum one GB). Event and organizer records each count as one result. Duplicate, filtered, private and failed records have no result charge. A run returning no results can still incur the start charge.

Apify planPrice per 1,000 results
Free$2.00
Bronze$1.90
Silver$1.80
Gold / Platinum / Diamond$1.70

The Store's “from” price is the lowest eligible plan price. Use Apify's maximum charge setting to cap your run. Platform usage is included in this pay-per-event price. Five results at the base price and the minimum start unit cost $0.01025.

Coverage and failure handling

  • City pages contain trending sections, other curated sections and the initial feed. The actor deduplicates event IDs across them. This is the public HTML snapshot, not every Partiful event or the complete infinite-scroll feed.
  • Organizer pages can include old events and expose a partial published-event history. Use dates to select the period you need.
  • Public event pages only: password-protected, nonpublic and unavailable events are rejected. No login, RSVP, guest list collection, private address recovery or access-control bypass is performed.
  • Hidden counts and host lists remain hidden. Addresses use displayed address lines, not a more precise address embedded in map metadata.
  • The actor does not infer ticket prices or availability from descriptions. Attendance counters are not summed into an ambiguous total.
  • Results follow source order. With a low global maxItems, an earlier city can consume the cap before later cities. Separate runs are appropriate when you need a quota per city.
  • maxRequests excludes robots.txt checks and one transient retry per failed request. Requests are paced. No paid proxy is required in tested runs.
  • SUMMARY records source counts, filters, request/result limits and errors. ERRORS lists failed URLs and reasons. A wholly failed run fails explicitly. A valid search with no filter matches succeeds with zero results. Partial failures preserve successful rows and remain visible in both records.

Use with AI agents and automation

Example prompt: “Use softprodlabs/partiful-scraper to find public New York events starting this weekend. Return title, local date, venue and source URL. Check SUMMARY for coverage limits before describing the list as complete.”

Connect via Apify API, MCP, schedules, Make, Zapier or n8n. Use the Store's API tab for generated calls using this actor's actual schema. Export the dataset as JSON, CSV or Excel. Schedule repeated snapshots and compare event IDs in your destination to track changes; this version does not keep a persistent change history.

Built by Software Production Labs. Report a problem in the actor's Issues tab with the run URL and expected result. Independent tool; not affiliated with Partiful.