# rc.searchPeople

Search for candidates in LinkedIn Recruiter Lite by keyword, with Advanced Search filters, or from a Recruiter search URL.

> The API Reference is also the SDK and CLI reference. Consecutive code fences marked `tab=HTTP`, `tab=Node`, `tab=Python` and `tab=CLI` are the same call on each surface (a fence marked `tab=HTTP,CLI` is the same text for both), and a block between `:::surface <names>` and `:::` applies only to the surfaces it names. Identifiers in the text are written as in Node and in HTTP JSON (camelCase); the Python SDK spells methods, parameters and result attributes in snake_case (`sendMessage` → `send_message`, `reconnectionLink` → `reconnection_link`), while names inside HTTP JSON stay camelCase.

Search for candidates in LinkedIn Recruiter Lite: by keyword, with Recruiter's Advanced Search filters, or by running a search you set up in Recruiter yourself. Add [rc.doForPeople](/docs/action-rc-do-for-people) to open each candidate's profile or save them to a project.

The account needs a Recruiter Lite seat and Linked API's Plus plan, and a search with `filter` needs a [supported LinkedIn interface language](/docs/recruiter-lite-overview#seat-requirements) – see [Recruiter Lite](/docs/recruiter-lite-overview).

:::surface node,python
In the SDK this is the `rcSearchPeople` method. It takes the parameters below except `label` and `then`, which exist only in workflow JSON, and returns the result below in `data`. To run actions for each candidate with [rc.doForPeople](/docs/action-rc-do-for-people), pass the whole workflow to [`customWorkflow`](/sdks/custom-workflow), as in the [usage example](#usage-example).
:::

:::surface cli
The command is `linkedin recruiter person search`. Its flags are listed below. To run actions for each candidate with [rc.doForPeople](/docs/action-rc-do-for-people), pass the whole workflow to [`linkedin workflow run`](/cli/workflows#workflow-run), as in the [usage example](#usage-example).
:::

## Constraints

> ⏺️ **Root Start:** allowed.

> ⬆️ **Parent Actions:** N/A.

> ⬇️ **Child Actions:** [rc.doForPeople](/docs/action-rc-do-for-people).

## Parameters

```json tab=HTTP
{
  "actionType": "rc.searchPeople",
  "label": "backendSearch",
  "term": "kubernetes",
  "limit": 50,
  "filter": {
    "jobTitles": ["Backend Engineer", "Platform Engineer"],
    "jobTitlesScope": "current",
    "locations": ["Berlin, Germany"],
    "skills": ["Go", "PostgreSQL"],
    "yearsOfExperience": { "from": 3, "to": 10 },
    "seniority": ["senior", "manager"],
    "profileLanguages": ["en", "de"],
    "hidePreviouslyViewed": true
  },
  "then": { ... }
}
```

```typescript tab=Node
const workflow = await linkedapi.rcSearchPeople.execute({
  term: "kubernetes",
  limit: 50,
  filter: {
    jobTitles: ["Backend Engineer", "Platform Engineer"],
    jobTitlesScope: "current",
    locations: ["Berlin, Germany"],
    skills: ["Go", "PostgreSQL"],
    yearsOfExperience: { from: 3, to: 10 },
    seniority: ["senior", "manager"],
    profileLanguages: ["en", "de"],
    hidePreviouslyViewed: true
  }
});

const { data, errors } = await linkedapi.rcSearchPeople.result(workflow.workflowId);
```

```python tab=Python
from linkedapi import RcSearchPeopleParams

workflow = linkedapi.rc_search_people.execute(
    RcSearchPeopleParams(
        term="kubernetes",
        limit=50,
        filter={
            "job_titles": ["Backend Engineer", "Platform Engineer"],
            "job_titles_scope": "current",
            "locations": ["Berlin, Germany"],
            "skills": ["Go", "PostgreSQL"],
            "years_of_experience": {"from": 3, "to": 10},
            "seniority": ["senior", "manager"],
            "profile_languages": ["en", "de"],
            "hide_previously_viewed": True,
        },
    )
)

result = linkedapi.rc_search_people.result(workflow.workflow_id)
```

```bash tab=CLI
linkedin recruiter person search \
  --term kubernetes \
  --limit 50 \
  --job-titles "Backend Engineer,Platform Engineer" \
  --job-titles-scope current \
  --locations '["Berlin, Germany"]' \
  --skills Go,PostgreSQL \
  --years-of-experience-from 3 \
  --years-of-experience-to 10 \
  --seniority senior,manager \
  --profile-languages en,de \
  --hide-previously-viewed \
  --json
```

In AI assistants, the MCP tool is `rc_search_people`. The n8n action is **Search people in Recruiter Lite**; the Make module is **Search People in Recruiter Lite**.

| Parameter | Description |
| --- | --- |
| `label` | Optional. Label included in workflow completion. |
| `term` | Optional. Keywords, as you would type them in Recruiter's search box. Must contain a character other than a space. |
| `filter` | Optional. Advanced Search filters, see [Filters](#filters). |
| `customSearchUrl` | Optional. URL of a Recruiter search results page, `https://www.linkedin.com/talent/search?…`, copied from the address bar after you set up the search in Recruiter. Runs that search as it is. Cannot be combined with `term` or `filter`. |
| `limit` | Optional. Number of candidates to return, from 1 to 1000. Defaults to 25. |
| `then` | Optional. [rc.doForPeople](/docs/action-rc-do-for-people), to run actions for each candidate. |

Give `term`, a `filter` with at least one value, or `customSearchUrl`. `term` and `filter` can be combined. A request with none of them, or with `customSearchUrl` next to `term` or `filter`, is rejected with `invalidWorkflow`. A scope such as `jobTitlesScope`, or a flag set to `false`, is not a value on its own.

:::surface cli
| Flag | Value | Sets |
| --- | --- | --- |
| `--term` | text | `term` |
| `--url` | Recruiter search URL | `customSearchUrl` |
| `--limit` | 1–1000, default 25 | `limit` |
| `--job-titles` | list | `filter.jobTitles` |
| `--job-titles-scope` | scope | `filter.jobTitlesScope` |
| `--locations` | list | `filter.locations` |
| `--locations-scope` | scope | `filter.locationsScope` |
| `--postal-code` | code | `filter.postalCode.code` |
| `--postal-code-radius-miles` | miles | `filter.postalCode.radiusMiles`; needs `--postal-code` |
| `--skills` | list | `filter.skills` |
| `--has-passed-skill-assessment` / `--no-has-passed-skill-assessment` | – | `filter.hasPassedSkillAssessment` |
| `--companies` | list | `filter.companies` |
| `--companies-scope` | scope | `filter.companiesScope` |
| `--current-companies` | list | `filter.currentCompanies` |
| `--past-companies` | list | `filter.pastCompanies` |
| `--company-sizes` | list | `filter.companySizes` |
| `--schools` | list | `filter.schools` |
| `--graduation-years-from` | year | `filter.graduationYears.from` |
| `--graduation-years-to` | year | `filter.graduationYears.to` |
| `--industries` | list | `filter.industries` |
| `--job-functions` | list | `filter.jobFunctions` |
| `--seniority` | list | `filter.seniority` |
| `--years-of-experience-from` | years | `filter.yearsOfExperience.from` |
| `--years-of-experience-to` | years | `filter.yearsOfExperience.to` |
| `--first-names` | list | `filter.firstNames` |
| `--last-names` | list | `filter.lastNames` |
| `--profile-languages` | list | `filter.profileLanguages` |
| `--recently-joined` | list | `filter.recentlyJoined` |
| `--network-relationships` | list | `filter.networkRelationships` |
| `--is-military-veteran` / `--no-is-military-veteran` | – | `filter.isMilitaryVeteran` |
| `--groups` | list | `filter.groups` |
| `--recruiting-activity-type` | type | `filter.recruitingActivity.type` |
| `--recruiting-activity-period` | period | `filter.recruitingActivity.period`; needs `--recruiting-activity-type` |
| `--projects` | list | `filter.projects` |
| `--notes` | list | `filter.notes` |
| `--hide-previously-viewed` / `--no-hide-previously-viewed` | – | `filter.hidePreviouslyViewed` |

- **Values.** Each flag takes the values its parameter takes, see [Parameters](#parameters) and [Filters](#filters).
- **Lists.** Separate values with commas, or, when a value contains a comma, pass a JSON array of strings: `--locations '["Berlin, Germany","Amsterdam, Netherlands"]'`. Give each list flag once.
- **Ranges.** `--graduation-years-from` and `--graduation-years-to`, and `--years-of-experience-from` and `--years-of-experience-to`, each take one bound or both.
- **Yes/no filters.** The positive form sets the filter to `true`. The `--no-…` form sets it to `false`, which adds no filter.
- **Search criteria.** Give `--term`, `--url`, or at least one filter flag; a scope flag or a `--no-…` flag alone is not enough. `--url` cannot be combined with `--term` or any filter flag. The CLI rejects these cases before it sends anything.
:::

## Filters

All fields are optional. Several values in one field find candidates who match any of them; several fields together narrow the search, as in Recruiter's Advanced Search. Names are matched against Recruiter's suggestions – see [How filters are applied](#how-filters-are-applied).

| Field | Type | Finds candidates |
| --- | --- | --- |
| `jobTitles` | array of strings | with these job titles |
| `jobTitlesScope` | string | whose `jobTitles` are `currentOrPast` (current or past), `current`, `pastNotCurrent` (past but not current) or `past` |
| `locations` | array of strings | in these locations |
| `locationsScope` | string | whose `locations` are `current`, `currentOrOpenToRelocate` (current, or open to relocate there) or `openToRelocateOnly` (open to relocate there only) |
| `postalCode` | object | near a postal or ZIP code: `code` (required) and `radiusMiles` (optional): 1, 5, 10, 25, 50, 100 or 200 |
| `skills` | array of strings | with these skills |
| `hasPassedSkillAssessment` | boolean | `true`: who passed a LinkedIn skill assessment |
| `companies` | array of strings | at these companies |
| `companiesScope` | string | whose `companies` are `currentOrPast`, `current`, `pastNotCurrent` or `past`, as for `jobTitlesScope` |
| `currentCompanies` | array of strings | currently at these companies |
| `pastCompanies` | array of strings | formerly at these companies |
| `companySizes` | array of strings | at companies of these sizes: `selfEmployed`, `1-10`, `11-50`, `51-200`, `201-500`, `501-1000`, `1001-5000`, `5001-10000`, `10001+` |
| `schools` | array of strings | who studied at these schools |
| `graduationYears` | object | who graduated in this range: `from` and `to`, years from 1900 to 2100 |
| `industries` | array of strings | in these industries |
| `jobFunctions` | array of strings | in these job functions, see the list below |
| `seniority` | array of strings | at these seniority levels: `unpaid`, `training`, `entry`, `senior`, `manager`, `director`, `vp`, `cxo`, `partner`, `owner` |
| `yearsOfExperience` | object | with this much experience: `from` and `to`, whole years from 0 to 30 |
| `firstNames` | array of strings | with these first names |
| `lastNames` | array of strings | with these last names |
| `profileLanguages` | array of strings | whose profile is in these languages, as LinkedIn language codes, such as `en` or `es`, see [Profile languages](#profile-languages) |
| `recentlyJoined` | array of strings | who joined LinkedIn recently: `1day`, `2to7days`, `8to14days`, `15to30days`, `1to3months` |
| `networkRelationships` | array of strings | at these network distances from you: `1st`, `2nd`, `3rd+`, `groupMembers` |
| `isMilitaryVeteran` | boolean | `true`: who are military veterans |
| `groups` | array of strings | in these LinkedIn groups |
| `recruitingActivity` | object | with this activity on your seat: `type` (required) and `period` (optional), see below |
| `projects` | array of strings | in these projects of yours, by project name |
| `notes` | array of strings | whose notes on your seat contain these words |
| `hidePreviouslyViewed` | boolean | `true`: leaves out candidates your seat has already viewed, as Recruiter's Hide previously viewed option does |

- **Ranges.** `yearsOfExperience` and `graduationYears` need `from`, `to` or both, with `from` no greater than `to`.
- **`false` flags.** `hasPassedSkillAssessment`, `isMilitaryVeteran` and `hidePreviouslyViewed` set to `false` add no filter.
- **`recruitingActivity`.** `type` is `messages`, `notes`, `projects`, `resumes` or `reviews`. `period` is `anytime` (the default), `pastDay`, `pastWeek`, `pastTwoWeeks`, `pastThreeMonths`, `pastSixMonths`, `pastYear` or `pastTwoYears`.
- **Scopes.** A scope applies to every value of its field. Without it, Recruiter's own default for that filter applies.
- **`jobFunctions`** takes these values: `Accounting`, `Administrative`, `Arts and Design`, `Business Development`, `Community and Social Services`, `Consulting`, `Customer Success and Support`, `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`, `Real Estate`, `Research`, `Sales`.

A value outside these lists or ranges is rejected with `invalidWorkflow` before the workflow starts.

### Profile languages

`profileLanguages` takes LinkedIn's language codes, as Recruiter's Profile languages filter uses them, in lower case. A language name such as `English` is rejected with `invalidWorkflow`. The filter lists these languages:

| Code | Language |
| --- | --- |
| `cs` | Czech |
| `da` | Danish |
| `de` | German |
| `en` | English |
| `es` | Spanish |
| `fr` | French |
| `in` | Bahasa Indonesia |
| `it` | Italian |
| `ja` | Japanese |
| `ko` | Korean |
| `ms` | Malay |
| `nl` | Dutch |
| `no` | Norwegian |
| `pl` | Polish |
| `pt` | Portuguese |
| `ro` | Romanian |
| `ru` | Russian |
| `sv` | Swedish |
| `tr` | Turkish |
| `_o` | Others |

Two codes are not what you might expect: Indonesian is `in`, not `id`, and `_o` is the filter's Others option. A code the filter does not list fails the search with `filterNotApplied`.

### How filters are applied

The action fills in Recruiter's Advanced Search as a person would and clicks Search. Each value must then appear as a filter pill that names it.

- **Companies, schools, skills, groups and projects** take Recruiter's suggestion with exactly the name you gave. Failing that, a suggestion that continues your text at a word boundary is taken, such as `Acme Robotics` for `Acme`. Anything else fails the search.
- **Job titles** take the suggestion with exactly the title you gave. Otherwise the title goes in as free text, which Recruiter searches for as typed: a longer title or LinkedIn's nearest one would be a different job.
- **Locations, industries and postal codes** take the suggestion with the name you gave, or else LinkedIn's first suggestion for the full text.
- **First names, last names and notes** go in as free text.
- **What was sent.** After Search, the action also checks the search request Recruiter sent: the scopes of each value, the postal-code radius, and the recruiting-activity type and period.

A value Recruiter does not offer or did not apply fails the action with `filterNotApplied`, which names the field and the value, and no candidates are returned. Correct or remove the value: retrying the same request fails the same way.

## Results and paging

- **Pages.** Recruiter shows 25 candidates per page. The action reads pages until it has `limit` candidates or the results end.
- **No results.** A search that finds nobody succeeds with an empty `data` array.
- **A later page fails.** The action returns the candidates it has collected so far, as a success. If the failure is one of the [account errors](/docs/recruiter-lite-overview#account-errors), the action fails with that error instead.
- **With child actions.** Under [rc.doForPeople](/docs/action-rc-do-for-people), the child actions run for each candidate in turn, one after another. The search stops at the first child action that fails and returns the candidates collected so far; the last one carries the failed result in `then`. A candidate who was on the results page a moment ago cannot be missing, so a failed child action means a Recruiter page failed – possibly a warning screen that every further page load would make worse. The one exception is an InMail that Recruiter refuses for one candidate (`inMailCreditRequired` or `inMailNotAvailable` from [rc.sendMessage](/docs/action-rc-send-message)): the search goes on with the next candidate.

## Result options

1. **Successful search:**

```json
{
  "actionType": "rc.searchPeople",
  "label": "backendSearch",
  "success": true,
  "data": [
    {
      "name": "Jane Example",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
      "headline": "Senior Backend Engineer at Example Cloud",
      "location": "Berlin, Germany",
      "avatarUrl": "https://media.licdn.com/dms/image/v2/C4D03AQExample/profile-displayphoto-shrink_100_100/0/1600000000000",
      "viewerState": { "connectionDegree": "2nd" },
      "then": [ ... ]
    },
    {
      "name": "Alex Sample",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId2",
      "headline": "Platform Engineer",
      "location": "",
      "avatarUrl": null,
      "viewerState": { "connectionDegree": null },
      "then": [ ... ]
    }
  ]
}
```

| Field | Meaning |
| --- | --- |
| `name` | Candidate's full name. |
| `recruiterProfileUrl` | Candidate's Recruiter profile, `https://www.linkedin.com/talent/profile/…`, without query parameters. Pass it as `personUrl` to [rc.openPersonPage](/docs/action-rc-open-person-page) or [rc.saveToProject](/docs/action-rc-save-to-project). It opens in Recruiter, not on the public LinkedIn site. |
| `headline` | Headline as the results show it, or an empty string. |
| `location` | Location as the results show it, or an empty string. |
| `avatarUrl` | Profile photo URL, or `null` without a photo. |
| `viewerState.connectionDegree` | `1st`, `2nd` or `3rd+`, as Recruiter shows it next to the name, or `null` when it shows none or when the interface language is not [supported](/docs/recruiter-lite-overview#seat-requirements). |
| `then` | Only with child actions: an array with the result of each child action run for this candidate, in order. |

`label` is included only if specified in the action parameters.

2. **Failed search:**

```json
{
  "actionType": "rc.searchPeople",
  "label": "backendSearch",
  "success": false,
  "error": {
    "type": "filterNotApplied",
    "message": "The following filters could not be applied: companies (\"Example Nonexistent Co\": LinkedIn offered no matching option). Remove or correct them and retry."
  }
}
```

Possible `error.type` values:

- `filterNotApplied` – a filter value could not be applied; the message names each field and value. See [How filters are applied](#how-filters-are-applied).
- `recruiterSignInRequired`, `recruiterTwoStepVerificationRequired`, `recruiterMultipleSessionsDetected` – the seat needs attention, see [account errors](/docs/recruiter-lite-overview#account-errors).
- `limitExceeded` – the account reached its `rcSearchQueries` [limit](/docs/recruiter-lite-overview#limits).
- `unexpectedError` – the search could not be completed.

## Usage example

**Workflow** – open the profile of each of the first 2 candidates and read their details:

```json tab=HTTP
{
  "actionType": "rc.searchPeople",
  "term": "kubernetes",
  "limit": 2,
  "filter": {
    "jobTitles": ["Platform Engineer"],
    "locations": ["Berlin, Germany"]
  },
  "then": {
    "actionType": "rc.doForPeople",
    "then": {
      "actionType": "rc.openPersonPage",
      "basicInfo": true
    }
  }
}
```

```typescript tab=Node
const workflow = await linkedapi.customWorkflow.execute({
  actionType: "rc.searchPeople",
  term: "kubernetes",
  limit: 2,
  filter: {
    jobTitles: ["Platform Engineer"],
    locations: ["Berlin, Germany"]
  },
  then: {
    actionType: "rc.doForPeople",
    then: {
      actionType: "rc.openPersonPage",
      basicInfo: true
    }
  }
});

const { data, errors } = await linkedapi.customWorkflow.result(workflow.workflowId);
```

```python tab=Python
workflow = linkedapi.custom_workflow.execute(
    {
        "actionType": "rc.searchPeople",
        "term": "kubernetes",
        "limit": 2,
        "filter": {
            "jobTitles": ["Platform Engineer"],
            "locations": ["Berlin, Germany"],
        },
        "then": {
            "actionType": "rc.doForPeople",
            "then": {
                "actionType": "rc.openPersonPage",
                "basicInfo": True,
            },
        },
    }
)

result = linkedapi.custom_workflow.result(workflow.workflow_id)
```

```bash tab=CLI
linkedin workflow run <<'EOF'
{
  "actionType": "rc.searchPeople",
  "term": "kubernetes",
  "limit": 2,
  "filter": {
    "jobTitles": ["Platform Engineer"],
    "locations": ["Berlin, Germany"]
  },
  "then": {
    "actionType": "rc.doForPeople",
    "then": {
      "actionType": "rc.openPersonPage",
      "basicInfo": true
    }
  }
}
EOF
```

:::surface http
**Completion:**
:::

:::surface node,python
**Completion** – `result()` returns this whole completion in `data`:
:::

:::surface cli
**Completion** – `linkedin workflow run` prints this whole completion as `data`:
:::

```json
{
  "actionType": "rc.searchPeople",
  "success": true,
  "data": [
    {
      "name": "Jane Example",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
      "headline": "Platform Engineer at Example Cloud",
      "location": "Berlin, Germany",
      "avatarUrl": null,
      "viewerState": { "connectionDegree": "2nd" },
      "then": [
        {
          "actionType": "rc.openPersonPage",
          "success": true,
          "data": {
            "name": "Jane Example",
            "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId1",
            "headline": "Platform Engineer at Example Cloud",
            "location": "Berlin, Germany",
            "avatarUrl": null,
            "viewerState": { "connectionDegree": "2nd" },
            "publicUrl": "https://www.linkedin.com/in/jane-example",
            "industry": "Software Development"
          }
        }
      ]
    },
    {
      "name": "Alex Sample",
      "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId2",
      "headline": "Platform Engineer",
      "location": "Berlin, Germany",
      "avatarUrl": null,
      "viewerState": { "connectionDegree": "3rd+" },
      "then": [
        {
          "actionType": "rc.openPersonPage",
          "success": true,
          "data": {
            "name": "Alex Sample",
            "recruiterProfileUrl": "https://www.linkedin.com/talent/profile/AEMAAB0xExampleProfileId2",
            "headline": "Platform Engineer",
            "location": "Berlin, Germany",
            "avatarUrl": null,
            "viewerState": { "connectionDegree": "3rd+" },
            "publicUrl": "https://www.linkedin.com/in/alex-sample",
            "industry": null
          }
        }
      ]
    }
  ]
}
```
