Use Facebook Event Details & New-Event Monitor Scraper with Python

Fetch public Facebook event details by URL, page listing, or keyword/city search, with venue GPS, hosts, ticket links, and a monitor mode that reports only newly-posted events.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "eventUrls": [
    "https://www.facebook.com/events/1855253805343101"
  ],
  "includeOccurrences": false,
  "includePastEvents": false,
  "maxItems": 50,
  "monitorMode": false
}

Download input.example.json and save your reviewed copy as input.json.

Field	Type	Required	Description
`eventUrls`	array	optional	Facebook event URLs or IDs, organizer event pages (e.g. https://www.facebook.com/TED/events, /upcoming_hosted_events, /past_hosted_events), or an events search URL. Group event URLs are skipped because they require login.
`searchQueries`	array	optional	Keywords for Facebook's public events search (e.g. "music festival", "tech conference"). Each query is paginated up to Max results.
`searchLocation`	string	optional	City or place text added to each search query (e.g. "Chicago"). This is a keyword hint, not a strict geographic filter; use Location ID for a strict filter.
`locationId`	string	optional	Optional Facebook place ID or /places/<id>/ URL for a location filter on search. Facebook's place scope can include nearby cities. Text-to-ID lookup requires login, which this actor does not use.
`startDate`	string	optional	Optional search filter lower bound in YYYY-MM-DD format (e.g. 2026-12-01). Applies to search queries only.
`endDate`	string	optional	Optional search filter upper bound in YYYY-MM-DD format. Equal to Start date selects one day.
`category`	string	optional	Optional server-side category filter for search queries. Categories are host-set, so some events have none.
`includePastEvents`	boolean	optional	For organizer pages, fetch the Past collection instead of Upcoming. Ignored for event URLs and search.
`includeOccurrences`	boolean	optional	For recurring events, add every occurrence date and URL to the event record. Uses one extra request only when the event is recurring.
`maxItems`	integer	optional	Maximum events per organizer listing or search query. A direct event URL always returns its one event.
`monitorMode`	boolean	optional	For organizer pages and searches, output only events not seen by an earlier run for the same target. The first run is a baseline. State is a named Apify store, is actor-wide (not per user), and is shared by all runs of this actor for the same target; clearing it or changing the target re-emits all events.

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/xSp7vACk0FpUckkaH/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

Public Facebook event records with dates, venue and GPS (when exposed), hosts, ticket data, recurring occurrences, online links and monitor-filtered results.

Questions before you run

Which inputs are required?

No top-level fields are marked required in the published schema. Conditional requirements can still apply; check the README.

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Open on Apify Full Actor reference

Generated from source build k2U4MYmHDAlszwlFn and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.