linkedin/
search-people

The LinkedIn Search People API discovers candidate public LinkedIn profiles from people-search URLs with normalized identity, description, images, location, website, account signals, and available metrics.

LinkedIn Search People API

Search URL input
Name-oriented discovery
Canonical accounts
1 credit / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

LinkedIn Search People

LinkedIn Search People turns the keywords value in each submitted people-search URL into a name-oriented provider query. Results are candidate public profiles for identity review, not proof that a profile belongs to the intended person, and the endpoint does not replay company, school, location, industry, or connection filters encoded in the URL.

LinkedIn Search People API Features

  • People-search URL inputSubmit one or more public LinkedIn URLs whose paths begin with /search/results/people.
  • Explicit name mappingThe LinkedIn Search People API decodes keywords, maps its first whitespace-delimited token to first_name, and joins the remaining tokens as last_name.
  • Candidate profile discoveryReceive public profile URLs and identity context that can support manual matching or later profile-specific collection.
  • Canonical account recordsReturn stable identity, description, image, website, account-state, location, metric, and collection fields.
  • Nullable source fidelityLeave unavailable fields null and avoid inferring private contact details, work history, education, skills, or identity certainty.

LinkedIn Search People API Parameters

ParametersRequiredDescription
urlsRequiredRequired list of public http or https LinkedIn URLs. Each host must be linkedin.com or a LinkedIn subdomain, and each path must begin with /search/results/people. Include keywords for reliable name-oriented behavior.

How to Use the LinkedIn Search People API

Prepare name-oriented people-search URLs, submit them to the LinkedIn Search People API as an asynchronous task, and review every returned candidate.

  1. Create a LinkedIn people-search URL with a keywords query value containing the person's name.
  2. POST urls to /v1/linkedin/search-people and save the returned task_id.
  3. Poll /v1/tasks/{task_id} until the task reaches a terminal status.
  4. On success, process data.results.items and follow next_cursor whenever has_more is true.
curl -X POST "https://api.socq.ai/v1/linkedin/search-people" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.linkedin.com/search/results/people/?keywords=Aakash%20Gupta"]}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

LinkedIn Search People API Use Cases

  • Profile URL discovery: Find candidate public LinkedIn profile URLs before using a profile-specific collection endpoint.
  • Manual identity resolution: Compare names, descriptions, locations, images, and URLs across candidates while retaining uncertainty.
  • Public directory intake: Feed candidate accounts from the LinkedIn Search People API into a review queue without promising contact enrichment or private attributes.
  • Name-variant research: Run carefully selected name spellings separately and compare the public candidates produced at each collection time.

LinkedIn Search People API Pro Tips

  • Always include a meaningful keywords query value; a valid URL without it creates an empty name row whose provider behavior is not reliable.
  • Remember that Mary Jane Smith is mapped to first_name Mary and last_name Jane Smith, not treated as a general keyword expression.
  • Do not assume that location, company, school, industry, or connection filters in the URL are honored; the current adapter discards them.
  • Use the public profile URL plus multiple corroborating attributes before identifying a person.
  • Deduplicate repeated candidates by stable profile URL when multiple submitted searches overlap.
  • The LinkedIn Search People API has no caller-controlled result limit, so design billing and review workflows around actual stored results.

Beyond the LinkedIn Search People API, use these APIs when you need a different type of public LinkedIn data.

  • LinkedIn Profiles API — Normalize public profile identity, roles, location, visible audience counts, experience, education, and skills from profile URLs.
  • LinkedIn Companies API — Normalize public company descriptions, websites, logos, visible audience and employee counts, industries, locations, and specialties.
  • LinkedIn Posts API — Collect public post text, authors, visible engagement, media, publication time, type, and hashtags from supported URLs.
  • LinkedIn Jobs API — Normalize public job titles, companies, descriptions, locations, qualifications, employment details, application links, and available salary fields.
  • LinkedIn Profile Posts API — Discover public posts associated with LinkedIn profile URLs, with author context, media, hashtags, timestamps, and visible engagement.
  • LinkedIn Search Posts API — Discover Google-indexed public LinkedIn posts by keyword and optional date string, returning normalized content, authors, media, tags, timestamps, and visible engagement.

Explore other platforms

Combine LinkedIn data with public data from other supported social platforms.

LinkedIn Search People API — FAQ

LinkedIn Search People API is a programmatic interface for discovering candidate public LinkedIn profiles from people-search URLs. It maps the URL's keywords value into a name-oriented provider query and returns normalized public account records for review.

Each value must be a complete http or https URL on linkedin.com or a LinkedIn subdomain, with a path beginning with /search/results/people.

After decoding, the value is split on whitespace. The first token becomes first_name and all remaining tokens are joined as last_name.

No. The current adapter does not map encoded location, company, school, industry, connection-degree, or other search filters.

No. This endpoint exposes no caller-controlled result limit and stores the records produced by the discovery source for each submitted URL.

No. Names are not unique. Treat each result as a candidate and corroborate the public URL, name, description, location, and other visible attributes.

Each successfully stored profile result costs 1 SocQ credit, with no base charge. Planning estimates use 100 results per URL, empty result sets have no result charge, and actual usage can vary because no result cap is exposed.