Search Facebook Places and Venues
View all Facebook Public Data API endpoints →Supply query and optionally location_uid or cursor for documented place discovery. No response for this route was sampled; venue identities, geographic fields and result shape must be validated. Use locations to evaluate location identifiers when needed, and confirm ambiguous venue matches manually. This route finds candidate public place references, not verified business ownership, accurate opening hours or a guarantee of geospatial completeness.
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/search-place API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/search-place?key=<API_KEY>&query=pizza'
Query Result
Use Cases
- Match submitted venue names to possible public Facebook place records for editorial review.
- Evaluate a location-scoped local-business discovery feature before indexing results.
- Link a confirmed venue candidate to a separate event research workflow.
- Keep ambiguous place matches in a manual reconciliation queue instead of merging businesses automatically.
Frequently asked questions
Is location_uid a latitude and longitude?
No. It is an identifier validated through location lookup, not a coordinate or radius condition.
Does finding a place confirm that it is an official business?
No. Search only provides candidate references. Identity and sources require human checks.
Are accurate opening hours guaranteed in the response?
No. This endpoint has no sample. Specific place fields and their freshness need actual validation.