Resolve LinkedIn Location Geocodes
View all LinkedIn Data API endpoints →Supply a human-readable keyword such as a city or country name. The documented JSON response has success, message, process_time and data entries containing location and geocode. Choose the intended location from possible matches before using its code. Job search accepts geocode, while people search names its location filter geocode_location; do not substitute display labels for codes.
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/linkedin-scraper/search-location API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/search-location?key=<API_KEY>&keyword=New+York'
Query Result
Use Cases
- Power a location selector that stores a selected geocode.
- Resolve a user-entered city before constructing a job-search request.
- Translate a country label into a people-search location filter.
- Keep display labels and reusable location IDs separate in a search form.
Frequently asked questions
Can I send the location name directly to job search?
Job search expects geocode. Use this lookup to obtain candidate codes, then choose the intended location and pass its geocode.
Is the location parameter named the same in people search?
No. The selected code is sent as geocode_location in search-people and as geocode in search-jobs.