GET
/
linkedin
/
geo-id-search
curl --request GET \
  --url https://api.harvest-api.com/linkedin/geo-id-search \
  --header 'X-API-Key: <api-key>'
{
  "id": "<string>",
  "query": {
    "search": "<string>"
  },
  "status": "<string>",
  "error": "<string>",
  "elements": [
    {
      "geoId": "<string>",
      "title": "<string>"
    }
  ]
}
fetch(`https://api.harvest-api.com/linkedin/geo-id-search?search=Australia`, {
  headers: { 'X-API-Key': '<api-key>' },
})
  .then((response) => response.json())
  .then((data) => console.log(data));

​
Search by LinkedIn GeoID

For most of the cases, when specifying full location name, the search by the location parameter should work fine.
However sometimes search by location may not give you what you expect, as LinkedIn have some other location for your text query. For example, NY returns New Zealand as first match instead of New York (it’s based on LinkedIn autocomplete feature, you can try it in UI).

To make sure the location is correct, you can fetch LinkedIn GeoID first and check it. GeoID search is free, it will not count against your quota.

const apiKey = '<api-key>';

fetch(`https://api.harvest-api.com/linkedin/geo-id-search?search=New York`, {
  headers: { 'X-API-Key': apiKey },
})
  .then((response) => response.json())
  .then((data) => {
    console.log('All matches:', data.elements);
    console.log('Closest match GeoID:', data.id);

    // Search for profiles in New York
    const params = new URLSearchParams({
      geoId: data.id,
      apiKey,
    });
    fetch(`https://api.harvest-api.com/linkedin/profile-search?${params.toString()}`)
      .then((response) => response.json())
      .then((data) => console.log(data));
  });

Authorizations

​
X-API-Key
string
header
required

Query Parameters

​
search
string

Location text to search for Geo ID (required)

Response

200
application/json

Geo ID search response

The response is of type object.