Find Location Identifiers
View all Facebook Public Data API endpoints →Supply a place-name query to request documented Facebook location identifiers. If matches are ambiguous, include the country or try an alternate spelling without diacritics. No location-search response was sampled, so exact identifier fields and geographic granularity need validation. Confirm the intended location before using its value as location_uid in supported searches; a text match is not a coordinate-based radius guarantee.
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/locations API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/locations?key=<API_KEY>&query=<query>'
Query Result
Use Cases
- Evaluate a city-selection control for supported location-aware search routes.
- Resolve ambiguous place names with country context before running a venue search.
- Test alternate spelling handling in a multilingual location-input workflow.
- Maintain a human-reviewed mapping from selected place labels to validated location identifiers.
Frequently asked questions
How do I obtain location_uid for a search?
First query locations by place name. Inspect the actual returned fields and geographic scope, then save the corresponding identifier after confirming the intended location.
What if cities share a name or search results are inaccurate?
Add the country to the place name or try a spelling without diacritics, and manually check the results.
Does a location ID guarantee a nearby radius search?
No. Text-based location matching and a latitude-and-longitude radius are different conditions and cannot replace each other.