Peoplerecruiterlite

Search LinkedIn Recruiter Lite

LinkedIn Recruiter Lite Search automates your entire search on LinkedIn Recruiter Lite.

POST/v1/actions/recruiterlite-search-people/run/live

Try it live See pricing

Edges is not related to LinkedIn and is not an official LinkedIn product.

Input

Request parameters

FieldTypeRequired

cursorstringno

Cursor value obtained from the `X-Pagination-Next` response header of a previous request, used to continue pagination. Cursors expire after 24 hours. If a cursor has expired or is invalid, pagination must be restarted from the beginning.

page_sizeintegerno

Maximum number of results per page (read-only; defined by the endpoint, actual count may be lower in some cases like throttling or internal limits).

Input parameters

FieldTypeRequired

linkedin_recruiter_search_urlstringyes

A LinkedIn Recruiter Search URL should start with 'https://www.linkedin.com/talent/hire/{id}/discover/recruiterSearch' or 'https://www.linkedin.com/talent/search'

Integration

FieldTypeRequired

identity_idsarrayyes

Array of identity UUIDs to use for the action

identity_modestringyes

Mode for identity handling: direct, auto, or managed.

Description

What Search LinkedIn Recruiter Lite does

Search LinkedIn Recruiter Lite automates your entire candidate search on LinkedIn Recruiter Lite so you can turn saved projects and filter sets into structured candidate feeds. You get each candidate row — name, headline, profile URL, current role, skills summary — ready to push into your ATS or sourcing CRM. It targets in-house recruiters and sourcing teams that live inside Recruiter Lite and need its results as code-ready data.

The action runs on the Recruiter Lite level and uses your authenticated Recruiter Lite session on Edges.

How it works

You pass a Recruiter Lite search URL or a saved project, and Search LinkedIn Recruiter Lite walks the result pages on your behalf. Edges handles pagination, normalizes the rows, and returns a structured array of candidate records with stable IDs.

Every request is signed with your connected Recruiter Lite session and paced within LinkedIn's activity guidance, so your seat stays in good standing. The action supports async execution — the default choice for any multi-page search or scheduled daily pull.

When to use Search LinkedIn Recruiter Lite

Reach for Search LinkedIn Recruiter Lite when your sourcing happens inside Recruiter Lite and you want its search results as data rather than as a paginated UI. It is the fastest way to drive an ATS sync or a scheduled sourcing feed off the Recruiter filter set you already trust.

For teams whose main jobs-to-be-done are sourcing and enrichment, it plugs into the LinkedIn profile and company data API use case. Recruiters chain it into CRM syncs and enrichment stacks the same way sellers chain LinkedIn people search.

Use cases

ATS seeding. Run a saved Recruiter Lite project nightly and push new candidates into your ATS as fresh sourcing records.
Dashboard-driven sourcing. Materialize Recruiter Lite search output into a warehouse table to power recruiter scorecards and pipeline visibility.
Agency delivery. Agencies servicing multiple roles run Search LinkedIn Recruiter Lite per role and deliver structured candidate lists to clients.
Talent pooling. Snapshot candidates matching an evergreen profile (e.g., "senior ML engineer, EU") weekly and maintain a rolling talent pool.
InMail targeting. Extract a candidate set and chain InMail outreach only on the rows that pass additional scoring rules.

Best practices

Start from a saved project. Saved projects encode hiring-manager-approved filters; pointing Search LinkedIn Recruiter Lite at a saved project keeps sourcing quality consistent across runs.
Run async. Recruiter Lite searches often span many pages; async execution is the default choice for anything beyond a shallow probe.
Chain a profile extractor. Search rows are shallow — follow with Extract LinkedIn Profile to deepen each candidate before outreach.
Stay inside your Recruiter Lite seat pacing. Edges paces requests safely, but combining heavy manual Recruiter usage with large extractions on the same seat should be kept reasonable.

Common questions

How many candidates can I extract per run?

It depends on how deep Recruiter Lite paginates for your search. Well-scoped project queries typically return hundreds to a couple of thousand; very broad queries will hit LinkedIn's pagination ceiling — tighten filters to capture more of the population.

Does Search LinkedIn Recruiter Lite use my Recruiter Lite account or a shared pool?

Your Recruiter Lite account. Every search runs through the authenticated session you connect to Edges, and the candidates returned match what your seat would see in the Recruiter Lite UI.

Can I chain Search LinkedIn Recruiter Lite with other Edges actions?

Yes. Feed the profileId of each candidate into Extract LinkedIn Profile, Extract Linkedin User Contact Info, or LinkedIn Inmail Profile to run the full sourcing-to-outreach sequence.

Get started

Run Search LinkedIn Recruiter Lite from the Edges library, schedule it against your saved projects, or call it directly from the Edges API to drive ATS syncs. Browse the full Actions library to see the extraction and outreach actions that follow.

Request

curl -X POST "https://api.edges.run/v1/actions/recruiterlite-search-people/run/live" \
  -H "X-API-KEY: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
  "identity_ids": [
    "your-identity-uuid"
  ],
  "identity_mode": "direct",
  "input": {
    "linkedin_recruiter_search_url": "https://www.linkedin.com/in/example-profile"
  }
}'

Response

200 OK · application/json

[
  {
    "sales_navigator_profile_id": "example-123",
    "linkedin_profile_url": "https://www.linkedin.com/in/example-profile",
    "linkedin_profile_id": 42,
    "headline": "Software Engineer at Example Corp",
    "first_name": "John",
    "last_name": "Doe",
    "full_name": "John Doe",
    "industry": "example_value",
    "connection_degree": "example_value",
    "profile_image_url": "https://www.linkedin.com/in/example-profile",
    "job_seeker": true,
    "location": "example_value",
    "educations": [
      1,
      2,
      3
    ],
    "experiences": [
      1,
      2,
      3
    ],
    "linkedin_people_post_search_url": "https://www.linkedin.com/in/example-profile",
    "company_name": "Example Name",
    "job_title": "Software Engineer at Example Corp"
  }
]

Build this with your agentMCP

Connect our docs MCP server and your coding agent can search every action and write this call for you.

docs.edges.run/mcp

// Related

Other ways to work with People.

linkedin-extract-connectionsExtract LinkedIn ConnectionsExtracts your LinkedIn connections, refining your outreach strategy.linkedin linkedin-extract-peopleExtract LinkedIn ProfileLinkedIn People Profile extracts all useful information from a specific LinkedIn profile.linkedin salesnavigator-extract-peopleExtract Sales Navigator ProfileSales Navigator People Profile extracts structured person data from a Sales Navigator profile — headline, experiences, contact fields, and recent job-change signals.sales nav linkedin-search-company-employeesSearch LinkedIn Company EmployeesSearch and extract employees from a LinkedIn company page.linkedin salesnavigator-search-company-employeesSearch Sales Navigator Company EmployeesExtract a list of employees on Sales Navigator starting from a company ID and from a set of given criteria.sales nav salesnavigator-search-peopleSearch Sales Navigator PeopleExtract a list of leads from a set of given criteria.sales nav

Try it with 100 free credits.

No card. Copy the snippet, paste your key, hit enter.

Get API key ← Back to library