LinkedIn Profile Lookup avatar

LinkedIn Profile Lookup

Pricing

from $0.15 / result

Go to Apify Store
LinkedIn Profile Lookup

LinkedIn Profile Lookup

LinkedIn profile lookup API for one public member URL. Export a sparse 24-field person snapshot with identity, roles, experience, education, articles, activity, counts, and provenance.

Pricing

from $0.15 / result

Rating

5.0

(2)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

2

Bookmarked

77

Total users

4

Monthly active users

6 days ago

Last modified

Share

LinkedIn Profile Lookup is a linkedin profile lookup api that turns one public member URL into a sparse 24-field person snapshot with career, education, article, activity, count, and provenance data. It is designed for candidate review, CRM enrichment, professional research, and monitored profile panels where a traceable Dataset row is more useful than copied page text.

Apify Users Apify Runs $0.05 / profile 24-field snapshot API + MCP ready

  • One run accepts exactly one public LinkedIn /in/ URL and returns at most one matching profile row.
  • The Dataset contract exposes 24 possible top-level fields and leaves unavailable optional values absent or null according to the schema.
  • The requested slug, final URL, and page canonical URL must identify the same member.
  • Images are kept only when they can be stored successfully; one failed image does not remove the profile row.

The smallest useful FREE-tier run uses the prefilled Andrew Ng URL and costs $0.01 for Actor Start plus $0.05 for one Profile Result, or $0.06 total when a row is saved.

Why Choose LinkedIn Profile Lookup

One-row professional snapshot. A successful row can include the person's name, headline, About text, displayed location, country code, follower and connection counts, job titles, affiliations, work experience, education, languages, awards, articles, and recent activity.

Identity-safe lookup. The Actor does more than detect generic Person markup. It checks that the requested /in/ slug agrees with both the final response URL and the canonical profile URL embedded in the page, so an unrelated valid member page is not accepted as the requested person.

Sparse, source-dependent output. Missing values are not replaced with guessed memberships, zeros, credentials, or private contact data. Consumers can distinguish a value observed in this snapshot from something the response did not provide.

Traceable processing. linkedin_url, processor, processed_at, status, platform, and type travel with the profile fields, making repeated snapshots easier to compare and investigate.

Quick Start Guide

Step 1: Configure

Open the input form and keep the working Andrew Ng prefill, or replace it with another public HTTPS LinkedIn member URL whose path is /in/{slug}/.

Step 2: Run

Start the Actor and wait for the terminal message. A successful process can still have no Dataset item when LinkedIn does not return the requested public profile, so inspect the Dataset count separately.

Step 3: Collect

Open the default Dataset and inspect the single row. Export it as JSON, CSV, Excel, XML, or RSS, or read it by Dataset ID through the Apify API.

Input Parameters

LinkedIn Profile Lookup exposes one required input.

ParameterTypeRequiredDescriptionExample
linkedin_urlstringYesPublic HTTPS LinkedIn member URL whose path is exactly /in/{slug}/; query noise is removed during normalizationhttps://www.linkedin.com/in/andrewyng/
{
"linkedin_url": "https://www.linkedin.com/in/andrewyng/"
}

The Actor does not accept a person-name query, URL list, company page, Sales Navigator URL, cookie, credential, email, phone number, or hidden filter. Run each member separately so the input, result charge, identity check, and timestamp remain independently traceable.

Output Data Schema

Each Dataset item is one sparse person snapshot with up to 24 top-level fields.

GroupFieldsMeaning
Identityplatform, type, linkedin_url, nameSource and canonical person identity
Profileheadline, about, location, country_code, profile_image_urlPublic summary, displayed place, and stored image
Counts and rolesfollower_count, connection_count, job_titles, affiliationsDisplayed counts and source-derived current role context
Backgroundexperiences, education, languages, skills, awards, publicationsPublic career, education, language, skill, award, and publication sections
Contentarticles, activitySampled public articles and recent activity cards
Processingstatus, processor, processed_atResult state, producing Actor, and observation time
{
"platform": "LinkedIn Profile Lookup",
"type": "person",
"linkedin_url": "https://www.linkedin.com/in/andrewyng/",
"name": "Andrew Ng",
"headline": "DeepLearning.AI, AI Fund and AI Aspire",
"location": "Palo Alto, California, United States",
"country_code": "US",
"follower_count": 2590667,
"connection_count": 500,
"job_titles": ["Founder", "Managing General Partner"],
"status": "success",
"processor": "https://apify.com/agentx/linkedin-profile-lookup",
"processed_at": "2026-08-12T17:42:16-07:00"
}

Nested arrays are also sparse. A missing key means it was not retained from this response; it does not prove the real-world value is empty, current, complete, or independently verified.

Integration Examples

Use Actor ID CUf5sseg9cEozOyhU or name form agentx/linkedin-profile-lookup from HTTP, an SDK, an automation platform, or MCP.

curl -X POST "https://api.apify.com/v2/acts/CUf5sseg9cEozOyhU/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"linkedin_url":"https://www.linkedin.com/in/andrewyng/"}'
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("CUf5sseg9cEozOyhU").call(run_input={
"linkedin_url": "https://www.linkedin.com/in/andrewyng/",
})
items = list(client.dataset(run["defaultDatasetId"]).iterate_items())
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('CUf5sseg9cEozOyhU').call({
linkedin_url: 'https://www.linkedin.com/in/andrewyng/',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
{
"actor": "agentx/linkedin-profile-lookup",
"input": {"linkedin_url": "https://www.linkedin.com/in/andrewyng/"},
"callOptions": {"memory": 128, "timeout": 300},
"waitSecs": 60
}

If a client wait window expires, poll the returned run ID instead of starting a duplicate. Store Apify tokens in server-side secrets rather than browser code, logs, Datasets, or support messages.

Pricing

LinkedIn Profile Lookup uses pay-per-event pricing. Actor Start costs $0.01 and a saved profile Result ranges from $0.05 to $0.0375 by plan.

EventFREEBRONZESILVERGOLDPLATINUMDIAMOND
Actor Start$0.01000$0.01000$0.01000$0.01000$0.01000$0.01000
Profile Result$0.05000$0.04500$0.04000$0.03750$0.03750$0.03750

Actor Start is one time per run. The Profile Result is charged once only when the row is pushed to the default Dataset. A FREE run with one saved row is $0.01 + $0.05 = $0.06; a run with no saved row has no Result event. Prices can change, so check the current pricing page before setting a maximum-total-charge policy.

Use Cases

Candidate dossier preparation. Attach public role, experience, education, language, award, and activity fields to an identified candidate record while preserving the profile URL and observation time for human review.

CRM enrichment. Add headline, displayed location, job titles, affiliations, and activity cues to an existing person record. The Actor does not discover private contact details or grant permission to contact someone.

Executive and market research. Build a defined panel of known public profiles and compare present keys, roles, counts, or content cautiously across scheduled observations.

Data-quality review. Use canonical identity, timestamps, source-dependent arrays, and key presence to distinguish a sparse page response from a downstream parsing or integration problem.

Alternatives

Manual review is appropriate for one consequential profile when a person needs the current page context and can record the URL and time. It becomes difficult to repeat consistently across a panel, and copied values lose their structured provenance.

LinkedIn's own member page is the authoritative presentation surface and is preferable when a person needs the latest visible context or interactive navigation. Licensed professional-data providers may be preferable when a workflow requires verified identity resolution, contracted coverage, historical records, or contact data under separate permissions.

Choose another workflow if the input must be a name search, a bulk URL list in one run, a company page, private or login-only data, verified employment, or a complete activity archive.

Limits and Troubleshooting

  • No Dataset row: confirm HTTPS and the exact /in/{slug}/ path, open the public page manually, inspect the terminal message, and retry later.
  • Identity mismatch: LinkedIn returned a different canonical member page; the Actor rejects it instead of labeling that person as the requested profile.
  • Missing field: treat absence as “not observed in this snapshot,” compare another run, and do not substitute a factual zero.
  • Missing media: keep the valid text data; an image is removed when it cannot be downloaded and stored safely.
  • Changing counts: preserve processed_at and require repeated observations before interpreting follower or connection movement.
  • Expired client wait: poll the existing run by ID instead of launching a duplicate.

For support, include the run ID, redacted input, terminal status, Dataset item count, expected field, and observed key set. Never include tokens, credentials, private Dataset content, or unrelated personal data.

Trust and Reliability

Apify supplies run isolation, storage, API access, schedules, webhooks, and Dataset exports. The Actor declares a 24-field Dataset contract and charges the Profile Result only when one row is retained.

Output values come from the public source response plus processing metadata; absent source values are not invented. LinkedIn controls page availability, visibility, and markup, so source changes can affect field density or whether a row is produced.

Public-data scope. The Actor reads information presented on a public member page and does not accept credentials or cookies. Public visibility does not remove privacy, intellectual-property, database-right, employment, or contractual obligations.

Responsible use. Establish a lawful purpose, minimize retained personal data, protect Datasets and tokens, honor deletion and suppression obligations, and add human review before consequential employment, credit, housing, insurance, or eligibility decisions.

Platform terms. Review LinkedIn's User Agreement and the Apify General Terms before production use. Do not use the Actor to bypass access controls or process data you are not permitted to use.

Frequently Asked Questions

What is a linkedin profile lookup api?

A linkedin profile lookup api converts a known public member URL into structured fields that software can consume. This Actor accepts one URL and returns at most one sparse 24-field snapshot.

Does every run return all 24 fields?

No. Optional source values are absent or null when they are not available, so consumers should test key presence.

Are experience and education entries verified?

No. They are parsed observations from the public response, not independent employment, identity, degree, or background verification.

Is connection_count exact?

It is the displayed source value retained for that snapshot and can be capped, rounded, unavailable, or changed later.

Does this return emails, phone numbers, or private account data?

No. The input and output contracts do not include login credentials, private account data, email discovery, or phone-number discovery.

Can I submit many profile URLs in one run?

No. The Actor accepts one URL per run. A client can orchestrate separate runs while preserving each run's price, status, and Dataset ID.

Why can a successful run have no row?

Process completion and source extraction are different outcomes. Inspect the Dataset count and terminal message rather than relying on the run status alone.

Can I schedule profile monitoring?

Yes, but each scheduled run still handles one known URL and any apparent change should be confirmed across repeated observations and appropriate sources.

Closest to this Actor:

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about member URLs, sparse fields, identity mismatches, pricing events, or integrations in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and exact input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 12, 2026