canonical: https://jentic.com/apis/alphaosint.com/alphaosint # Alphaosint LinkedIn People Search API The LinkedIn People Search API finds people on LinkedIn by name, job title, company, school, or location and returns their public profile data as structured JSON, including profile URL, headline, current employer, about text, work history, education, and follower count. It runs as an Apify actor, so a single search request accepts rich filters and an enrichProfiles flag that controls how much profile detail each match carries. No LinkedIn login, session cookie, or account is required. ## For AI agents Search LinkedIn for people by name, job title, company, school, or location and get structured public profiles with work history, education, and current employer. Returns JSON without any LinkedIn login or session cookie. ## Scope Does not handle messaging, connection requests, or company-page data. Use for public LinkedIn people search and profile enrichment only. ## Capabilities - Search LinkedIn for people by first and last name, job title, employer, school, or location - Return structured public profiles with headline, current employer, profile URL, and photo - Enrich each match with about text, full work history, education, and follower counts - Cap a run with maxResults to control how many people and how much cost each search returns - Run free-text keyword searches when you have a skill or industry term but no specific name ## Use cases ### Agent-Driven LinkedIn Prospecting An AI agent researching a sales list calls the LinkedIn People Search API through Jentic to turn a name, company, or job title into structured public profile data: profile URL, headline, current employer, work history, and education. The agent passes search fields such as firstName, lastName, company, and jobTitle, sets maxResults to bound the run, and reads back a clean JSON list without logging into LinkedIn or handling a session cookie. Example prompt: Search for people with jobTitle 'Software Engineer' at company 'Microsoft' in location 'San Francisco' with maxResults 25 and return each profile URL and headline ### Recruiter Candidate Sourcing A recruiting team sources candidates by requiring a job title, employer, and school, then pulls each person's public work history and education to build a shortlist. The LinkedIn People Search API matches people whose public profile mentions the given company, current or past, and the enrichProfiles option adds about text, languages, and connection counts for deeper screening. Results come back as structured JSON, so there is no manual profile scraping. Example prompt: Find people with jobTitle 'Data Scientist', school 'Stanford University', and enrichProfiles true, then return their work history and education ### Contact Enrichment From a Name Given only a first and last name, the LinkedIn People Search API returns a matching public profile with the person's current employer, headline, and profile URL, enriching a thin CRM record with verified role and company data. Turning enrichProfiles off keeps a run fast and cheap when only the headline and employer are needed, while turning it on adds the full history. The exact-phrase name match keeps results tight to the person you asked for. Example prompt: Look up the person 'Jane Doe' with enrichProfiles false and return their current employer, headline, and profile URL ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/acts/johnvc~linkedin-people-search-api/run-sync-get-dataset-items` | Run the search and return the matched people as dataset items | | POST | `/acts/johnvc~linkedin-people-search-api/run-sync` | Run the search and return the output from the key-value store | | POST | `/acts/johnvc~linkedin-people-search-api/runs` | Start a search run and return information about the initiated run | ## Key resources - **Actor Run** — Start the LinkedIn people-search actor and retrieve results, either synchronously as dataset items or as a run record - **Profile Results** — Structured people records returned per search: profile URL, headline, employer, work history, education, and follower counts ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 70 / 100 - AI-Readiness & Agent Experience: 42 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/alphaosint.com/alphaosint/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the LinkedIn People Search API by hand means getting an Apify token, building the actor input body, and choosing between the synchronous dataset endpoint and a plain run you then have to poll. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The actor and its run operations live in the URL path (`/acts/johnvc`~linkedin-people-search-api/...), so a rule can limit your agent to just these search endpoints and nothing else on the Apify host. The search terms travel in the request body, so rules bound which operations the agent may call, not which names it may search for. - **Credential handling:** Your Apify token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find a person on LinkedIn' or 'look up a profile by name', and Jentic returns the matching LinkedIn People Search operation with its input schema so the agent fills in fields like firstName and company without reading the actor docs. ## Related APIs - **Apollo.io** — A B2B contact and company database with its own people search and enrichment, versus a LinkedIn-only public profile search. - **People Data Labs** — A person enrichment API that resolves a profile from partial identifiers across many sources, versus a LinkedIn-focused name search. - **RocketReach** — A contact lookup service that returns emails and phone numbers for a person, versus LinkedIn public profile fields only. - **Hunter** — Finds and verifies work email addresses, which pairs with the name and employer this API returns. ## FAQ ### What authentication does the LinkedIn People Search API use? The LinkedIn People Search API runs on Apify and authenticates with an Apify API token passed as the `token` query parameter on each run request, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs. ### Can I search for people by company and job title with the LinkedIn People Search API? Yes. The search accepts firstName, lastName, keywords, jobTitle, company, school, and location fields, and returns only people whose public profile or search snippet matches the ones you set. Setting enrichProfiles to true adds about text, work history, education, and follower counts to each result, while leaving it off returns just the profile URL, name, headline, and current employer. ### What are the rate limits for the LinkedIn People Search API? The OpenAPI spec does not specify rate limits. The API runs as an Apify actor, so run concurrency and monthly usage follow your Apify account plan; see the Apify platform documentation at https://docs.apify.com for current limits. ### How do I find a LinkedIn profile by name through Jentic? Search Jentic with a query like 'find people on LinkedIn by name', add the LinkedIn People Search API from the directory, and store your Apify token once. Your agent then calls the synchronous run operation with firstName, lastName, and any filters such as company or location, and reads back the matched profiles as dataset items in JSON. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the LinkedIn People Search API? Yes. Write a rule that allows only the search run operations under the `/acts/johnvc`~linkedin-people-search-api path, so the agent can run people searches and read results but cannot reach any other actor or dataset on the Apify host, and every call it makes is logged. Because the search terms ride in the request body, scoping controls which operations run, not which individuals the agent may look up. ### Is there a LinkedIn People Search API MCP server? You don't need an MCP server to give your agent the LinkedIn People Search API. Jentic connects it directly from the API Directory: import it, store your Apify token once, and your agent calls the search operations on demand without loading another server's tool definitions into its context.