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

Named-location identifier discovery Starts with a place-name query rather than requiring a preexisting location_uid.
Country-qualified disambiguation Including a country can help distinguish locations with the same or similar names.
Alternate-spelling guidance Documentation suggests trying names without diacritics when results are unexpected.
Downstream location-key validation Check the returned identifier before using it in Page, post, event or place searches.

Live API Demo

GET /api/project/facebook-scraper/locations

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/locations?key=<API_KEY>&query=<query>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →