POST
/
search-employees-by-sales-nav-url
curl --request POST \
  --url https://fresh-linkedin-profile-data.p.rapidapi.com/search-employees-by-sales-nav-url \
  --header 'Content-Type: application/json' \
  --header 'x-rapidapi-key: <api-key>' \
  --data '{
  "url": "https://www.linkedin.com/sales/search/people?coach=false&query=(filters%3AList((type%3AREGION%2Cvalues%3AList((id%3A103644278%2CselectionType%3AINCLUDED)))%2C(type%3ACURRENT_COMPANY%2Cvalues%3AList((id%3A82274765%2CselectionType%3AINCLUDED)))))",
  "limit": 25
}'
{
  "message": "Use this request_id to check your search with 'Check Search Status' endpoint",
  "request_id": "0bb8360c779317e5f6fc1722a8bd26a1"
}

Works exactly the same endpoint Search Employees except that it takes a search url as the input. It’s helpful when you already have sales navigator search url(s).

Authorizations

​
x-rapidapi-key
string
header
required

Body

application/json
​
url
string

The LinkedIn Sales Navigator URL for searching employees.

Example:

"https://www.linkedin.com/sales/search/people?coach=false&query=(filters%3AList((type%3AREGION%2Cvalues%3AList((id%3A103644278%2CselectionType%3AINCLUDED)))%2C(type%3ACURRENT_COMPANY%2Cvalues%3AList((id%3A82274765%2CselectionType%3AINCLUDED)))))"

​
limit
integer

Limit the number of results.

Example:

25

Response

200
application/json
Success.
​
message
string
Example:

"Use this request_id to check your search with 'Check Search Status' endpoint"

​
request_id
string
Example:

"0bb8360c779317e5f6fc1722a8bd26a1"