Read Past Events for a Page
View all Facebook Public Data API endpoints →Supply page_id with optional cursor and collection_id for the documented past-event collection. No response was sampled, so event fields, ordering and continuation details need validation. Retain any returned collection identifier with its matching cursor. Use this as a source of observed public past-event references; pagination is not a promise of complete history or evidence that every returned event actually occurred as planned.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/facebook-scraper/page-past-events API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/page-past-events?key=<API_KEY>&page_id=<page_id>'
Query Result
Use Cases
- Evaluate a venue's prior public event program for editorial planning.
- Compare observed past-event themes with upcoming announcements in a client dataset.
- Test bounded historical event collection without promising a complete archive.
- Keep planned-event references distinct from independently confirmed attendance or occurrence evidence.
Frequently asked questions
Can past-event and future-event cursors be used interchangeably?
No. They are different collections. Save the cursor and collection_id actually returned by each one separately.
Does a past-event record prove that the event took place?
No. It may be a reference to a public plan. Verify whether it actually took place through other sources.
Can pagination retrieve a complete venue event history?
There is no such guarantee. Fields and continuation still need validation, and public coverage may be incomplete.