LinkedIn Profile Enricher: full profile and company data from LinkedIn URLs

Turn LinkedIn profile URLs into complete contact records. For each profile you get the person's title, seniority, headline, summary, skills and location, their business and personal emails with deliverability grades, and their employer's industry, NAICS and SIC codes, headcount and revenue, with optional full job history. The Actor never visits or logs in to LinkedIn: the data comes from the MoltSets API. Powered by MoltSets.

• One call per profile: person, contact details and company firmographics come back together.
• Graded emails: the best business email and personal email, each with an A to F send-safety grade and the date it was last validated.
• Company firmographics: industry, LinkedIn industry, NAICS and SIC codes, employee count and range, revenue and revenue range.
• Job history (optional): every role with title, company, dates and seniority, as JSON.
• Hashed emails included: SHA256 and MD5 of every business email on file, for ad audience matching (SHA256 depends on your plan).
• No LinkedIn account needed: the Actor never visits LinkedIn, so there are no cookies to manage and no account at risk.
• Clean input: profile URLs in any format, or bare slugs. Duplicates, company pages and Sales Navigator URLs are filtered out without spending anything.

Bring your own MoltSets API key

This Actor calls the MoltSets API with your own key, so MoltSets data is billed to your MoltSets account and Apify only charges for compute (the Actor itself is free).

1. Create a free MoltSets account.
2. Copy a key from API keys. Keys start with ms_.
3. Paste it into the MoltSets API key field. Apify stores it encrypted and the Actor never logs it.

What it costs

You only pay for hits. A lookup that finds nothing costs no tokens. It still counts towards your MoltSets Fair Use request limits.

Lookup	MoltSets tool	Cost
Full profile	reverse_linkedin_lookup	1 token per profile found

Costs are read live from your account (get_billing) at the start of every run, and the log shows a worst-case estimate before any lookups are made. If your balance is lower than the worst case the run still starts, because misses are free; if tokens run out it stops gracefully and keeps everything found so far.

Token costs are the published MoltSets rates at the time of writing. A profile is charged once when it is found, whatever fields it carries, and job history costs nothing extra. If you only need an email or a phone number, the LinkedIn Email and Phone Finder charges only when that specific field is found.

Input

Field	Name	Default	Description
apiKey	MoltSets API key		Required. Your MoltSets API key (starts with ms_). No account yet? Sign up free, then copy a key from API keys. MoltSets bills your MoltSets account directly, and only for hits.
linkedinUrls	LinkedIn profile URLs		Profile URLs (https://www.linkedin.com/in/...) or bare profile slugs. Duplicates and company pages are filtered out before any lookup.
datasetId	Read from a dataset		Use the results of another run, for example a LinkedIn search or post scraper. Combined with any URLs above.
datasetField	Dataset column with the profile URL		Column to read, for example linkedinUrl or author.profileUrl (dot paths work). Leave empty to try common names: linkedinUrl, linkedInUrl, profileUrl, linkedin_url, linkedinProfileUrl, url, publicIdentifier.
includeExperience	Include job history	false	Add the person's full job history as JSON in the experience column. Off by default because it makes rows much larger. The current role is always included.
maxItems	Maximum profiles	100	Hard cap on unique profiles processed in this run.
maxRetryWaitSecs	Longest Fair Use wait	120	If MoltSets asks the run to wait for a Fair Use window up to this long, it waits and carries on. Longer waits stop the run gracefully and keep the results so far.

Example input:

{
    "apiKey": "ms_XXXXXXXXXXX",
    "linkedinUrls": [
        "https://www.linkedin.com/in/retentionadam",
        "linkedin.com/in/john-smith-123"
    ],
    "includeExperience": false,
    "maxItems": 100
}

Output

One row per input item, in input order. Each lookup has a <lookup>_status column:

Status	Meaning
found	Data returned (and charged).
not_found	Nothing on file. Free.
restricted	Not included in your MoltSets plan. Nothing charged. See notes.
skipped	Not attempted: invalid input, out of phone tokens, or the run stopped early. See notes.
error	MoltSets could not complete the lookup after retries. Free; worth running again.

Example row:

{
    "linkedin_url": "linkedin.com/in/john-smith-123",
    "linkedin_url_normalised": "https://www.linkedin.com/in/john-smith-123",
    "input_status": "valid",
    "profile_status": "found",
    "full_name": "John Smith",
    "title": "Senior Associate - Technical Director",
    "seniority": "Senior",
    "functional_area": "Engineering",
    "skills": "Data Engineering; Python; PostgreSQL",
    "city": "Denver",
    "country": "United States",
    "business_email": "john.smith@example.com",
    "business_email_risk_score": "A",
    "business_email_validated_at": "2026-09-12",
    "personal_email": "john.smith@gmail.com",
    "personal_email_risk_score": "A",
    "company_name": "MoltSets",
    "company_website": "moltsets.com",
    "company_industry": "Information Technology",
    "company_naics_codes": "518210 Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services",
    "company_employee_count": 9,
    "company_revenue_range": "$1M - $5M",
    "notes": null
}

• The example shows a selection of columns. Every row has all of them; see the All fields view.
• Risk scores grade send safety: A validated deliverable, B known engagement, C catch-all domain, D never send (bounce, complaint or trap), F no signal. Suppress D; treat C and F as unknown rather than bad.
• Personal emails only appear when your MoltSets plan includes personal email. Otherwise notes says they were withheld.
• Lists (skills, interests, other emails, hashes, NAICS and SIC codes) are separated by semicolons so they survive CSV export. Job history is a JSON array in experience.
• connection_count is capped at 500, like LinkedIn's own "500+".

A run summary (hits and misses per lookup, tokens used, skipped lookups and why, stop reason) is saved as SUMMARY in the run's key-value store and shown in the run's status message.

Chaining from a scraper

Point the Actor at the output of any LinkedIn search, post or company-employee scraper. In the Console, choose the run's dataset under Read from a dataset; common column names such as linkedinUrl, profileUrl and url are detected automatically, or set Dataset column with the profile URL (dot paths such as author.profileUrl work).

From code, with the Apify API client:

import { ApifyClient } from 'apify-client';

const apify = new ApifyClient({ token: process.env.APIFY_TOKEN });

const run = await apify.actor('moltsets/linkedin-profile-enricher').call({
    apiKey: process.env.MOLTSETS_API_KEY,
    datasetId: '<dataset from your LinkedIn scraper run>',
    includeExperience: true,
    maxItems: 500,
});

const { items } = await apify.dataset(run.defaultDatasetId).listItems();

To run it automatically after a scraper, add an integration on the scraper that starts this Actor with {"datasetId": "{{resource.defaultDatasetId}}"} plus your key.

Limits

• Person profiles only: company pages, Sales Navigator, Recruiter and old /pub/ URLs are flagged invalid.
• Fair Use: MoltSets limits enrichment records and requests per rolling 5-hour and 1-week window, by plan. Every lookup counts as a request, hit or miss. If MoltSets asks the run to wait less than Longest Fair Use wait (default 120 seconds) it waits and continues; otherwise it stops gracefully, keeps its results and says when the window resets. See the Fair Use Policy.
• Plan-restricted fields: personal emails and SHA256 hashes depend on your plan. Withheld fields are noted in notes.
• Out of tokens: the run stops, keeps everything processed so far and links to billing. Unprocessed rows are marked skipped.
• Maximum profiles caps unique profiles per run (default 100), so a large dataset cannot spend more than you intended.

Other MoltSets Actors

• LinkedIn Email and Phone Finder (coming soon): business and personal emails, mobile phones and hashes from LinkedIn URLs.
• Email Finder by Name and Company (coming soon): business emails from a name and company domain.
• Reverse Email Lookup (coming soon): the person and LinkedIn profile behind an email address.
• IP to Company Lookup (coming soon): the company behind an IPv4 address.
• B2B Lead List Builder (coming soon): lead lists of people or companies by title, industry, location and size.
• LinkedIn Profile Finder (coming soon): LinkedIn profile URLs from an email or a name and company.
• Audience Match Keys (coming soon): hashed emails and mobile ad IDs for customer match audiences.

Support

• MoltSets API docs: developer.moltsets.com
• Account, billing and plan questions: support@moltsets.com
• Bugs in this Actor: open an issue on the Issues tab.