Introducing API Playground (and YouTube Monitoring!) Learn more

How to fetch `geo_id` parameter for the Job API?
proxycurl

How to fetch `geo_id` parameter for the Job API?

The geo_id parameter in the Job Listing API and Job Listing Count API represents the ID that LinkedIn prescribes to a region. This article will explain how you get a matching geo_id for a given region you want to target.

Note: Proxycurl API has been sunset. I built Proxycurl, and I am now building NinjaPear. The documentation links above are kept here for historical context because this geo_id workflow is still the part people come here for.

Follow these steps to get the geo_id that you are seeking to match a region to:

  1. Visit this page without being logged into LinkedIn. Use Private Browsing on Firefox or Incognito mode on Chrome.
  2. At the top, there is a search bar with two input fields. Use the input field on the right, the one that allows you to filter jobs by region.
  3. Enter the region that you want to target in the input field mentioned in step #2. An autocomplete dialog will appear. Click on the correct region.
  4. Press Enter and you will be brought to a results page.
  5. Look at the URL bar, and take note of the URL. It should look something like this:

https://www.linkedin.com/jobs/search?keywords=&location=Greater%20Los%20Angeles%2C%20California%2C%20United%20States&locationId=&geoId=100657539&f_TPR=r604800&distance=25&f_WT=3&position=1&pageNum=0 6. What you want is the number that comes after geoId= in the URL. This number will be the input for geo_id in the Proxycurl Jobs API.

That is it.

If you are here because you used Proxycurl in the past, the key thing to preserve in your own code is simple: geo_id is just LinkedIn's region identifier pulled from the jobs search URL, not something Proxycurl invented.

Hope this helps!

Steven Goh | CEO
World's laziest CEO. CEO of NinjaPear. Ex-Founder of Proxycurl (10+M), Steven founded 5 other startups: Gom VPN, Kloudsec, SilvrBullet, NuMoney, and SharedHere.

Featured Articles

Here's what we've been up to recently.

I dismissed someone, and it was not because of COVID19

The cadence of delivery. Last month, I dismissed the employment of a software developer who oversold himself during the interview phase. He turned out to be on the lowest rung of the software engineers in my company. Not being good enough is not a reason to be dismissed. But not

sharedhere

I got blocked from posting on Facebook

I tried sharing some news on Facebook today, and I got blocked from posting in other groups. I had figured that I needed a better growth engine instead of over-sharing on Facebook, so I spent the morning planning the new growth engine. Growth Hacking I term what I do in