# /linkedin/search/users

`POST /api/linkedin/search/users`

Price: 1 credit

Linkedin Search Users

## How to use it

Search by keywords, name, title, company. Use first_name + last_name for best results when searching specific people. URN filters (current_company, location, industry) accept raw text — backend auto-resolves. For industry use only valid top-level names (e.g. Technology, Information and Media). For custom terms like fintech or SaaS use company_keywords instead. For well-known people (e.g. Satya Nadella, Sam Altman), ALWAYS add company_keywords (e.g. Microsoft, OpenAI) to disambiguate from namesakes. If you know the person's LinkedIn alias, use /linkedin/user directly instead of searching. Use title for role-based search — it matches the headline, while keywords match the whole profile. A text location resolves to EVERY matching place (Berlin also matches Berlin, New York), so pass a geo URN when the city must be exact. profile_language filters by the language the PROFILE is written in, not by spoken languages. open_to_volunteer means open to volunteering, NOT open to work — open_to_work is a response field, not a filter. After search, verify identity by checking headline and location — famous people typically have descriptive headlines (e.g. 'CEO at Microsoft').

## Working with /linkedin/search

Search LinkedIn users, companies, jobs, posts by keywords and filters. URN filters (current_company, location, industry) accept raw text — backend auto-resolves.

- keywords → /linkedin/search/users → list of LinkedinSearchUser with URN
- keywords → /linkedin/search/companies → list of LinkedinSearchCompany with URN
- company URN from /linkedin/search/companies → current_company filter in /linkedin/search/users

## 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_name` (string) — Search for exact first name. Using first_name or last_name significantly improves result quality (default: ""; examples: "Bill")
- `last_name` (string) — Search for exact last name. Using first_name or last_name significantly improves result quality (default: ""; examples: "Gates")
- `job_title` (string) — Search for exact word in the title (default: ""; examples: "Director")
- `company_keywords` (string) — Search for exact word in the company name (default: ""; examples: "Microsoft")
- `school_keywords` (string) — Search for exact word in the school name (default: ""; examples: "Harvard")
- `current_company` (union) — Current company URN or company name (examples: ["company:1441"])
  - `type` (string, required) (one of: "company")
  - `value` (string, required)
- `past_company` (union) — Past company URN or company name (examples: ["company:1441"])
  - `type` (string, required) (one of: "company")
  - `value` (string, required)
- `location` (union) — Location geo URN or location name (examples: ["urn:li:geo:103689695"])
  - `type` (string, required) (one of: "geo")
  - `value` (string, required)
- `industry` (union) — Industry URN or name. Valid top-level industries: Technology, Information and Media; Professional Services; Manufacturing; Hospitals and Health Care; Retail; Government Administration; Holding Companies; Oil, Gas, and Mining; Real Estate and Equipment Rental Services; Transportation, Logistics, Supply Chain and Storage; Utilities; Wholesale. Text auto-resolves to URN. (examples: ["industry:96"])
  - `type` (string, required) (one of: "industry")
  - `value` (string, required)
- `education` (union) — Education institution URN or name (examples: ["urn:li:fsd_company:96"])
  - `type` (string, required) (one of: "fsd_company")
  - `value` (string, required)
- `profile_language` (array) — Profile language, ISO 639-1 code. Filters by the language the profile is written in, not by the languages the person lists as spoken. (examples: ["de","fr"])
- `open_to_volunteer` (boolean) — Only people marked as open to volunteering. Not the same as open to work. (default: false)
- `is_verified` (boolean) — Only people whose identity LinkedIn has verified (default: false)
- `count` (integer, required) — Max result count (max: 500; >: 0)

## Response

### 200 — Successful Response

- `@type` (string) (default: "LinkedinSearchUser")
- `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)
- `alias` (string, required)
- `url` (string, required)
- `image` (string, nullable)
- `headline` (string, nullable)
- `location` (string, nullable)
- `open_to_work` (boolean) (default: false)

## 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.