Linkedin Profile Search ($0.9 per 1000 results) avatar

Linkedin Profile Search ($0.9 per 1000 results)

Pricing

from $0.70 / 1,000 results

Go to Apify Store
Linkedin Profile Search ($0.9 per 1000 results)

Linkedin Profile Search ($0.9 per 1000 results)

$0.9/1K 🔥 Scrape and extract LinkedIn profile leads fast from keywords. Get names, profile IDs, public LinkedIn URLs, headlines, current title, company, and descriptions for sales, recruiting, sourcing, lead generation, prospecting, and market research.

Pricing

from $0.70 / 1,000 results

Rating

0.0

(0)

Developer

Iñigo Garcia Olaizola

Iñigo Garcia Olaizola

Maintained by Community

Actor stats

0

Bookmarked

5

Total users

2

Monthly active users

a day ago

Last modified

Share

LinkedIn Profiles Scraper

LinkedIn Profiles Scraper is a fast, cost-efficient actor for finding public LinkedIn profile URLs from search keywords. It is designed for teams that need clean lead lists quickly: names, profile IDs, LinkedIn URLs, headlines, current title/company when available, and short public descriptions.

This actor is especially useful when you need high-volume LinkedIn profile discovery without slow deep enrichment. It focuses on the fields that matter most for prospecting and routing, making it cheaper and faster than heavier LinkedIn profile scrapers.

Why Use This Actor

  • Fast LinkedIn profile discovery from any keyword, role, company, niche, or location.
  • Lower cost per result by focusing on lightweight profile search data.
  • Clean names and profile URLs ready for CRM imports, enrichment tools, or outreach workflows.
  • LinkedIn profile IDs extracted from URLs for deduplication and matching.
  • Title parsing that splits common profile titles into name, headline, current title, and current company when the data is present.
  • Clean, simple output focused on lead discovery.

Best Use Cases

  • Build lead lists from keywords like software engineer fintech, founder climate tech, or recruiter openai.
  • Find LinkedIn profile URLs for people in a role, industry, company, geography, or niche.
  • Collect names and LinkedIn IDs for downstream enrichment.
  • Create prospecting datasets for sales, recruiting, partnerships, sourcing, or market mapping.
  • Quickly test audience size and profile availability for a keyword segment.

Input Parameters

FieldTypeRequiredDescription
queryStringNoOptional keyword or phrase used to discover relevant public LinkedIn profiles. Leave empty for a broad profile search on the selected LinkedIn domain.
domainStringNoLinkedIn domain to target. Choose linkedin.com for any LinkedIn domain, www.linkedin.com for main global results only, or one of the localized country-code domains from the dropdown, such as es.linkedin.com, ca.linkedin.com, uk.linkedin.com, fr.linkedin.com, or de.linkedin.com.
maxItemsIntegerYesMaximum number of profiles to save. Set to 0 for unlimited.

LinkedIn Domain

Use domain to choose which LinkedIn domain the actor should target:

  • linkedin.com for broad discovery across any LinkedIn domain, including localized subdomains.
  • www.linkedin.com for main global profile discovery only.
  • Localized country-code domains such as us.linkedin.com, uk.linkedin.com, es.linkedin.com, fr.linkedin.com, de.linkedin.com, ca.linkedin.com, au.linkedin.com, or in.linkedin.com for country-focused discovery.

The actor includes a dropdown with Any LinkedIn domain (linkedin.com), Global main site (www.linkedin.com), and all validated LinkedIn country-code domains. Localized options are labeled with the country or territory name plus the exact domain, for example Spain (es.linkedin.com) or United States (us.linkedin.com).

Example Input

{
"query": "software engineer fintech san francisco",
"domain": "linkedin.com",
"maxItems": 100
}

For a localized search, select one of the country domains:

{
"query": "founder fintech madrid",
"domain": "es.linkedin.com",
"maxItems": 100
}

Output

Each dataset item contains a public LinkedIn profile URL and structured fields derived from publicly visible discovery data.

{
"id": "alex-morgan-123456",
"url": "https://www.linkedin.com/in/alex-morgan-123456",
"name": "Alex Morgan",
"headline": "Software Engineer at Stripe",
"currentTitle": "Software Engineer",
"currentCompany": "Stripe",
"description": "Software engineer with experience building scalable payment systems and developer tools..."
}

Output Fields

  • id: LinkedIn profile identifier from the profile URL.
  • url: Canonical public LinkedIn profile URL.
  • name: Person name parsed from the profile title.
  • headline: Public headline or title text when available.
  • currentTitle: Parsed role when the headline clearly contains a pattern such as Title at Company or Title @ Company.
  • currentCompany: Parsed company when the headline clearly contains a company pattern.
  • description: Short public description associated with the profile.

Tips For Better Results

  • Use role plus context: account executive cybersecurity, machine learning engineer healthcare, founder ai agents.
  • Add geography when relevant: product manager berlin, recruiter new york, founder singapore fintech.
  • Use the LinkedIn domain dropdown for country-specific discovery. Choose linkedin.com for broad results across any LinkedIn domain, www.linkedin.com for main global results only, or a localized domain such as es.linkedin.com, fr.linkedin.com, de.linkedin.com, ca.linkedin.com, uk.linkedin.com, au.linkedin.com, or in.linkedin.com when the target market matters.
  • Run multiple focused queries instead of one very broad query for cleaner segmentation.
  • Increase maxItems when mapping larger markets or building broader lead lists, or set it to 0 to keep collecting until results run out.

Performance Notes

This actor is optimized for speed and cost efficiency. It focuses on profile discovery and lightweight structured fields, which makes it a strong fit for collecting names, LinkedIn IDs, and LinkedIn profile URLs at scale.

For workflows that need emails, full work history, education, or detailed profile enrichment, use this actor as the first step and pass the resulting profile URLs into your enrichment pipeline.