# LinkedIn Profile Scraper (`reapx/qa-linkedin-profile-scraper`) Actor Build a clean file of LinkedIn people from profile URLs, public identifiers, or searches. Keep names, roles, employers, locations, audience size, experience, and education together for prospecting and company research. - **URL**: https://apify.com/reapx/qa-linkedin-profile-scraper.md - **Developed by:** [ReapX](https://apify.com/reapx) (community) - **Categories:** Lead generation, Social media, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.01 / 1,000 dataset items This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## LinkedIn Profile Scraper Build a clean file of LinkedIn people from profile URLs, public identifiers, or searches. Keep names, roles, employers, locations, audience size, experience, and education together for prospecting and company research. ![LinkedIn Profile Scraper interface](https://reapx.dev/assets/products/linkedin-profile-scraper/readme.png) ### The record The dataset schema names every field before the run. The first working set is `username`, `fullName`, `firstName`, `lastName`, `headline`, `currentTitle`, `currentCompany`, `companyWebsite`, `companyHeadcount`, `companyIndustry`, `location`, and `country`. Dataset views keep related fields together without changing the underlying row. #### Captured row ```json { "companyHeadcount": 232991, "connectionsCount": 500, "country": "US" } ``` ### Input LinkedIn Profile Scraper accepts source URLs, public identifiers, and searches. Run controls stay in the same form. | Field | What it controls | Starting value | | --- | --- | --- | | `startUrls` | Paste exact LinkedIn URLs, one per line. | `["https://www.linkedin.com/in/satyanadella"]` | | `urls` | Paste the LinkedIn URLs to process, one per line. | `["https://www.linkedin.com/in/satyanadella","https://www.linkedin.com/in/williamhgates"]` | | `publicIdentifiers` | Enter the public identifiers to resolve, one per line. | `["williamhgates","satyanadella","jeffweiner08"]` | | `queries` | Enter the search phrases to run, one per line. | `["Satya Nadella"]` | | `enrich` | Choose the enrichment mode applied to returned records. | `"off"` | | `maxItems` | Stop after this many dataset rows. | `10` | | `includeHistory` | Keep history in the returned record. | `true` | | `maxConcurrency` | Set the number of source requests that may run in parallel. | `5` | | `findWorkEmail` | Add the work-email lookup step to this run. | `false` | | `maxSeconds` | Stop after this many seconds and keep completed rows. | `180` | #### Example input ```json { "startUrls": [ "https://www.linkedin.com/in/satyanadella" ], "urls": [ "https://www.linkedin.com/in/satyanadella", "https://www.linkedin.com/in/williamhgates" ], "publicIdentifiers": [], "queries": [], "enrich": "off", "maxItems": 1, "includeHistory": true } ``` ### Price $0.00001 per dataset item. Other Apify plans use the rates shown in the Pricing tab. ![LinkedIn Profile Scraper input and result demonstration](https://reapx.dev/assets/products/linkedin-profile-scraper/demo.svg) ### Console, API, schedules, and exports Runs can begin in Apify Console, from a saved task, or through the Actor API. A schedule can reuse the same input. Completed rows remain in the run dataset for API retrieval and Apify dataset exports. ```text POST https://api.apify.com/v2/acts/JhXpCI1Re4ltZYSZd/runs GET https://api.apify.com/v2/datasets/{datasetId}/items ``` ### Saved tasks Twenty task pages cover distinct research, comparison, operations, automation, and export jobs. The opening set is: - **LinkedIn profile exact lookup**: Review one LinkedIn record around `username`, `fullName`, `headline`, and `headlineSource`. The saved task uses `startUrls`, `urls`, and `publicIdentifiers` and opens the `overview` view. Configured in LinkedIn Profile Scraper. - **LinkedIn profile account comparison**: Compare LinkedIn profiles using `companyHeadcount`, `country`, `followersCount`, and `connectionsCount`. The `stats` view keeps the differences close together. Configured in LinkedIn Profile Scraper. - **LinkedIn profile source list**: Process a saved LinkedIn input queue with `startUrls`, `urls`, and `publicIdentifiers`. Source and identifier fields remain visible in the `identity` view. Configured in LinkedIn Profile Scraper. - **LinkedIn profile identity index**: Index LinkedIn profiles by `username`, `headlineSource`, `currentTitleSource`, and `companyWebsiteSource`. The saved input keeps the same matching keys from run to run. Configured in LinkedIn Profile Scraper. - **LinkedIn profile contact coverage**: Assemble a LinkedIn register centered on `companyWebsite`, `workEmail`, `phone`, and `emailConfidence`. The task keeps `startUrls`, `urls`, and `publicIdentifiers` visible for later review. Configured in LinkedIn Profile Scraper. - **LinkedIn profile audience benchmark**: Compare numeric and status fields across LinkedIn profiles, led by `companyHeadcount`, `country`, `followersCount`, and `connectionsCount`. Results open as the `contact` table. Configured in LinkedIn Profile Scraper. ### Related products - [LinkedIn Email Scraper](https://apify.com/reapx/linkedin-email-scraper) - [LinkedIn Post Scraper](https://apify.com/reapx/linkedin-post-scraper) - [LinkedIn Search Scraper](https://apify.com/reapx/linkedin-search-scraper) - [LinkedIn Lead Scraper](https://apify.com/reapx/linkedin-lead-scraper) - [LinkedIn Account Scraper](https://apify.com/reapx/twitter-following-scraper) ### Support Include the Actor ID, run ID, saved task name, and affected input when reporting an issue. That is enough to locate the run and its dataset. # Actor input Schema ## `startUrls` (type: `array`): Paste exact LinkedIn URLs, one per line. ## `urls` (type: `array`): Paste the LinkedIn URLs to process, one per line. ## `publicIdentifiers` (type: `array`): Enter the public identifiers to resolve, one per line. ## `queries` (type: `array`): Enter the search phrases to run, one per line. ## `enrich` (type: `string`): Choose the enrichment mode applied to returned records. ## `maxItems` (type: `integer`): Stop after this many dataset rows. ## `includeHistory` (type: `boolean`): Keep history in the returned record. ## `maxConcurrency` (type: `integer`): Set the number of source requests that may run in parallel. ## `findWorkEmail` (type: `boolean`): Add the work-email lookup step to this run. ## `maxSeconds` (type: `integer`): Stop after this many seconds and keep completed rows. ## Actor input object example ```json { "startUrls": [ "https://www.linkedin.com/in/williamhgates", "https://www.linkedin.com/in/satyanadella", "williamhgates" ], "urls": [ "https://www.linkedin.com/in/satyanadella", "https://www.linkedin.com/in/williamhgates" ], "publicIdentifiers": [ "williamhgates", "satyanadella", "jeffweiner08" ], "queries": [ "Satya Nadella" ], "enrich": "off", "maxItems": 10, "includeHistory": true, "maxConcurrency": 5, "findWorkEmail": false, "maxSeconds": 180 } ``` # Actor output Schema ## `results` (type: `string`): Rows returned by this run. ## `json` (type: `string`): Clean JSON records from this run. ## `csv` (type: `string`): CSV export from this run. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ "https://www.linkedin.com/in/satyanadella" ], "urls": [ "https://www.linkedin.com/in/satyanadella", "https://www.linkedin.com/in/williamhgates" ], "publicIdentifiers": [ "williamhgates", "satyanadella", "jeffweiner08" ], "queries": [ "Satya Nadella" ], "enrich": "off", "maxItems": 10, "includeHistory": true, "maxConcurrency": 5, "findWorkEmail": false, "maxSeconds": 180 }; // Run the Actor and wait for it to finish const run = await client.actor("reapx/qa-linkedin-profile-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": ["https://www.linkedin.com/in/satyanadella"], "urls": [ "https://www.linkedin.com/in/satyanadella", "https://www.linkedin.com/in/williamhgates", ], "publicIdentifiers": [ "williamhgates", "satyanadella", "jeffweiner08", ], "queries": ["Satya Nadella"], "enrich": "off", "maxItems": 10, "includeHistory": True, "maxConcurrency": 5, "findWorkEmail": False, "maxSeconds": 180, } # Run the Actor and wait for it to finish run = client.actor("reapx/qa-linkedin-profile-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ "https://www.linkedin.com/in/satyanadella" ], "urls": [ "https://www.linkedin.com/in/satyanadella", "https://www.linkedin.com/in/williamhgates" ], "publicIdentifiers": [ "williamhgates", "satyanadella", "jeffweiner08" ], "queries": [ "Satya Nadella" ], "enrich": "off", "maxItems": 10, "includeHistory": true, "maxConcurrency": 5, "findWorkEmail": false, "maxSeconds": 180 }' | apify call reapx/qa-linkedin-profile-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,reapx/qa-linkedin-profile-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/JhXpCI1Re4ltZYSZd/builds/PVvdNW1C2wAk1QMeW/openapi.json