# /linkedin/sn_search/users

`POST /api/linkedin/sn_search/users`

Price: 150 credits

Linkedin Sales Navigator Search Users

## How to use it

Advanced user search via Sales Navigator filters. More filters than standard search.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keywords` (string) — Any keyword for searching in the user page.With the params result count will be small.Use other params to obtain a lot of results (default: ""; examples: "Director")
- `first_names` (array) — Search for exact first names (examples: ["Bill"])
- `last_names` (array) — Search for exact last names (examples: ["Gates"])
- `current_titles` (array) — Search for exact word in the current title (examples: ["Director"])
- `location` (union) — Location URN, can be obtained in /linkedin/search/locations, only geo urn type is allowed. Or location name. (examples: ["urn:li:geo:103689695"])
  - `type` (string, required) (one of: "geo")
  - `value` (string, required)
- `education` (union) — Education URN, can be obtained in /linkedin/search/educations, only fsd_company urn type is allowed. Or education name. (examples: ["urn:li:company:96"])
  - `type` (string, required) (one of: "company")
  - `value` (string, required)
- `languages` (array) — Profile Language (one of: "Arabic", "English", "Spanish", "Portuguese", "Chinese", "French", "Italian", "Russian", "German", "Dutch", "Turkish", "Tagalog", "Polish", "Korean", "Japanese", "Malay", "Norwegian", "Danish", "Romanian", "Swedish", "Bahasa Indonesia", "Czech"; examples: "Arabic")
- `past_titles` (array) — Search for exact word in the past title (examples: ["Director"])
- `functions` (array) — Job functions (one of: "Accounting", "Administrative", "Arts and Design", "Business Development", "Community and Social Services", "Consulting", "Education", "Engineering", "Entrepreneurship", "Finance", "Healthcare Services", "Human Resources", "Information Technology", "Legal", "Marketing", "Media and Communication", "Military and Protective Services", "Operations", "Product Management", "Program and Project Management", "Purchasing", "Quality Assurance", "Research", "Real Estate", "Sales", "Customer Success and Support")
- `levels` (array) — Job level (one of: "Entry", "Director", "Owner", "CXO", "Vice President", "Experienced Manager", "Entry Manager", "Strategic", "Senior", "Trainy")
- `years_in_the_current_company` (array) — Years in the current company (one of: "0-1", "1-2", "3-5", "6-10", "10+")
- `years_in_the_current_position` (array) — Years in the current position (one of: "0-1", "1-2", "3-5", "6-10", "10+")
- `company_sizes` (array) — Sizes of the current company (one of: "Self-employed", "1-10", "11-50", "51-200", "201-500", "501-1,000", "1,001-5,000", "5,001-10,000", "10,001+")
- `company_types` (array) — Types of the current company (one of: "Public Company", "Privately Held", "Non Profit", "Educational Institution", "Partnership", "Self Employed", "Self Owned", "Government Agency")
- `company_locations` (union) — Company Location URN, can be obtained in /linkedin/search/locations, only geo urn type is allowed. Or location name. (examples: ["urn:li:geo:103689695"])
  - `type` (string, required) (one of: "geo")
  - `value` (string, required)
- `current_companies` (union) — Current company URN, only company urn type is allowed. Or company name. (examples: ["urn:li:company:1441"])
  - `type` (string, required) (one of: "company")
  - `value` (string, required)
- `past_companies` (union) — Past company URN, only company urn type is allowed or company name. Or company name. (examples: ["urn:li:company:1441"])
  - `type` (string, required) (one of: "company")
  - `value` (string, required)
- `industry` (union) — Industry URN, can be obtained in /linkedin/search/industries, only industry urn type is allowed. Or industry name. (examples: ["urn:li:industry:96"])
  - `type` (string, required) (one of: "industry")
  - `value` (string, required)
- `is_posted_on_linkedin` (boolean, nullable) — Users who have recently published content on the platform
- `count` (integer, required) — Max result count (min: 1; max: 2500)
- `company_keyword` (string) — Keyword for current company text filter in Sales Navigator. (default: ""; examples: "Microsoft")
- `past_company_keyword` (string) — Keyword for past company text filter in Sales Navigator. (default: ""; examples: "Google")

## Response

### 200 — Successful Response

- `@type` (string) (default: "LinkedinSalesNavigatorSearchUsersUser")
- `internal_id` (object, required)
  - `type` (string, required) (one of: "fsd_company", "fsd_group", "fsd_profile", "fsd_skill", "activity", "comment", "company", "group", "geo", "pulse", "member", "industry", "ugcPost", "job", "message", "conversation", "media", "share", "linkedInArticle")
  - `value` (string, required)
- `urn` (object, required)
  - `type` (string, required) (one of: "fsd_company", "fsd_group", "fsd_profile", "fsd_skill", "activity", "comment", "company", "group", "geo", "pulse", "member", "industry", "ugcPost", "job", "message", "conversation", "media", "share", "linkedInArticle")
  - `value` (string, required)
- `name` (string, required)
- `url` (string, required)
- `image` (string, nullable)
- `headline` (string, nullable)
- `location` (string, nullable)
- `is_premium` (boolean) (default: false)
- `current_companies` (array) (default: [])
  - `@type` (string) (default: "LinkedinSalesNavigatorSearchUsersCurrentCompany")
  - `company` (union, nullable)
    - `@type` (string) (default: "LinkedinSalesNavigatorSearchUsersCompany")
    - `urn` (object, required) (see schema LinkedinURN_Literal_company__)
    - `url` (string, required)
    - `name` (string, required)
    - `image` (string, nullable)
    - `industry` (string, nullable)
  - `position` (string, required)
  - `description` (string, nullable)
  - `joined` (integer, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The entity was not found, or a precondition failed

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.