Partiful Events Scraper & Monitor

Collect public Partiful events from supported Explore cities or exact public event URLs, export stable event records, and safely track NEW, UPDATED, and confirmed ENDED changes. The smallest useful run needs only the default New York Explore scope.

🚀 Start in 60 seconds

1. Choose Collect events.
2. Keep nyc or select another supported Explore city.
3. Start with 25 Core rows.
4. Run the Actor and open the Overview dataset view.

{"workflow":"collect","exploreSlugs":["nyc"],"detailLevel":"core","maxResults":25,"maxResultsPerTarget":50,"maxBuyerChargeUsd":1}

🎯 Choose the right workflow

Goal	Workflow	Result
Build a city feed or event list	Collect events	Current public event rows
Watch a stable public scope	Track changes	NEW, UPDATED, and carefully confirmed ENDED rows
Enrich known public events	Collect + Detailed	One public event page per delivered event

📦 What you get

Each event keeps a stable Partiful event ID and canonical URL, with source-published title, description, dates, location, cover, organizer, public RSVP counts, and ticket signals when available. A free coverage row explains whether the requested public window completed, was capped, filtered, partial, blocked, or failed.

Representative synthetic fixture:

{"recordType":"event","stableId":"partiful:event:public-event-example","eventId":"public-event-example","url":"https://partiful.com/e/public-event-example","title":"Community event","city":"New York","interestedCount":120,"sourceName":"Partiful"}

🎛️ Input guide

• workflow: return current events or compare a repeat run.
• exploreSlugs: supported public Explore city pages: nyc, la, sf, bos, dc, chi, lon, mia, and atx.
• eventUrls: exact public https://partiful.com/e/... URLs. Private or phone-gated activity is not accessed.
• detailLevel: Core uses the public listing surface; Detailed opens each event's public page and uses one mutually exclusive detailed-event charge instead of the Core row charge.
• keywordsAny and excludeKeywords: deterministic post-filters. Filtered monitoring never infers removal.
• stateNamespace: separates independent monitoring baselines.
• maxResults, maxResultsPerTarget, and maxDetailRequests: hard caps; hitting a cap returns CAPPED and withholds removal decisions.
• maxBuyerChargeUsd: refuses the run when the active worst-case event price exceeds your ceiling.

💰 Pricing

The complete formula is: verified target or monitoring scan + delivered Core, Detailed, or change rows. On the Free plan, a 25-row Core collection is $0.00005 + 25 × $0.00215 = $0.0538; 25 Detailed rows are $0.00005 + 25 × $0.00235 = $0.0588. Failed or blocked source work is not charged, and coverage rows are free.

✅ Coverage you can trust

• COMPLETE: every requested public surface was exhausted within the declared scope.
• CAPPED: a declared result, request, byte, or runtime limit stopped traversal.
• FILTERED: the source walk completed, but filters make absence non-comparable.
• PARTIAL: useful rows exist, but at least one target failed or was blocked.
• BLOCKED and FAILED: never presented as empty.
• EMPTY_CONFIRMED: used only when the expected public surface positively confirms no public events.

Monitoring commits state only after confirmed delivery. An event becomes ENDED only after two comparable complete misses; capped, filtered, partial, blocked, or failed runs never remove it.

On the first Track changes run, the default Create baseline only setting stores the current comparable scope and returns no change rows. The next identical run compares against that baseline; choose Return current events as NEW only when you deliberately want first-run change rows and their row charges.

🔌 API and automation

Run the Actor from Apify Console or API and export JSON, CSV, Excel, XML, or HTML. After publication, you can separately create Tasks and Schedules for repeat city feeds or monitoring; no public Task or schedule is bundled with this Actor release.

⚠️ Not yet supported

• Private invitations, hidden locations, login-only content, attendee identities, phone-gated activity, messages, photos, comments, or RSVP actions.
• Arbitrary city search outside the supported public Explore city pages.
• Guaranteed ticket-price fields when Partiful does not publish them on the public page.

❓ FAQ and support

Does this require a Partiful login? No. It reads only deliberately public Partiful pages.

Why are some fields null? Public pages vary. Optional fields remain null instead of being guessed.

What should I send with a support request? Include the Apify run ID, input with secrets removed, and the coverage row.