Refresh a Public Event by ID

View all Facebook Public Data API endpoints →

Supply a confirmed event_id to request the documented event-detail record. This route was not sampled, so exact fields and equivalence with URL-based event lookup remain unverified. Use only identifiers reconciled from actual event references, and retain observation times when refreshing stored records. An unavailable response does not establish cancellation; validate the returned information or check the public source before changing a published calendar.

API Features

Known-event refresh input Uses a stored event_id rather than a submitted event link.
ID-route validation boundary The exact event response must be tested independently of the URL-based route.
Observation-time retention A client can retain when each event record was fetched to support freshness review.
No automatic cancellation verdict An unavailable event lookup alone does not justify labeling an event cancelled.

Live API Demo

GET /api/project/facebook-scraper/events-details-by-id

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/events-details-by-id?key=<API_KEY>&event_id=<event_id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Where should event_id come from?

Use an identifier validated from an actual public event reference. Confirm that it belongs to the same event before saving it; do not invent or interchange identifiers.

Are ID-based and URL-based event details guaranteed to match?

No. The fields and envelopes for the two routes need independent validation.

Can I mark an event as canceled when a refresh returns no result?

No. Unavailability does not prove cancellation. Check the business status and latest public source, and have a person review the outcome.

Related operations

Guides

View Subscription Plans →