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

Readable-location input keyword accepts a city or country search term rather than requiring an existing code.
Label-and-code pairs The documented entries pair a location label with its geocode.
Location disambiguation step Let the user select among returned matches instead of assuming the first label is the desired region.
Search-filter code handoff Use the selected code as geocode for jobs or geocode_location for people.

Live API Demo

GET /api/project/linkedin-scraper/search-location

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/search-location?key=<API_KEY>&keyword=New+York'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →