LinkedIn Company Lookup: linkedin company scraper from $5/1k avatar

LinkedIn Company Lookup: linkedin company scraper from $5/1k

Pricing

from $3.80 / 1,000 company founds

Go to Apify Store
LinkedIn Company Lookup: linkedin company scraper from $5/1k

LinkedIn Company Lookup: linkedin company scraper from $5/1k

LinkedIn company scraper with no cookies and no account. Give it public LinkedIn company page links and get one flat row each: name, tagline, industry, company size, employees on LinkedIn, headquarters, founded, website, specialties, followers and logo. Nothing found, nothing charged.

Pricing

from $3.80 / 1,000 company founds

Rating

0.0

(0)

Developer

Adrian Voss

Adrian Voss

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

LinkedIn Company Lookup: LinkedIn Company Scraper, No Cookies

Hand this actor a list of public LinkedIn company page links and it fetches each one the way a signed-out browser does, then returns a flat row per company: name, tagline, the About paragraph, industry, the size band the company claims, how many members actually list it as their employer, headquarters, founding year, ownership type, website, specialty tags, follower count and logo. No login. No cookies. No li_at session token to paste in, no account of yours at risk, and nothing read from behind LinkedIn's sign-in wall.

Most of each row comes from the schema.org Organization block LinkedIn itself publishes in the page source, so it is the company's own structured description of itself rather than text scraped off a layout that changes every quarter. When LinkedIn decides a request should sign in first, the actor says so in the row's status and charges you nothing.

Who it's for

Account executives working an ABM list who need every target company's headcount, industry and headquarters in the same spreadsheet the links came in on. RevOps teams filling the empty firmographic columns behind a CRM field that only ever stored a LinkedIn URL. Investors and analysts sizing a market by pulling founding year, ownership type and employee count across forty portfolio candidates at once. Recruiters qualifying which employers on a longlist are actually 200 people rather than the 2,000 their careers page implies. And anyone wiring an agent or a workflow that already holds a company page link and needs the organisation behind it in a shape a script can read, with no logged-in LinkedIn session kept alive anywhere.

If you do not have the company links yet, this is the wrong tool. It looks up companies you already name; it does not search LinkedIn for companies matching a description.

Why this one

  • Two headcount numbers, not one, because they disagree. companySize is the band the company picked for itself. employeesOnLinkedIn is how many members actually list it as their employer. Stripe reports "5,001-10,000 employees" while 16,949 members name it. Tools that collapse these into one number throw away exactly the signal that tells you a company has outgrown its own About page.
  • No cookies, no session token, no account. Every request is the plain public page. You are never asked for a li_at cookie, and no LinkedIn account of yours can be restricted because of a run here.
  • Read from LinkedIn's own structured data. Name, About text, employee count, address, logo, tagline and website come out of the schema.org Organization block in the page source. The five fields LinkedIn does not put there are read from stable data-test-id hooks, not from CSS classes chasing a redesign. Field names stay put, which is what an agent or a Clay column needs.
  • A block is a labelled miss, not a silent hole. If LinkedIn asks the request to sign in, the row says status: BLOCKED with a plain explanation and costs nothing. A page that no longer exists says NOT_FOUND. A member profile pasted by mistake says BAD_FORMAT without ever spending a request.
  • Never charged for a miss. Billing fires only on a row where a real company came back.
  • Schools and showcase pages work too. /company/, /school/ and /showcase/ links all parse, because a pasted CRM column has all three mixed in.
  • Residential proxy by default. LinkedIn's sign-in wall is driven by the reputation of the IP asking, so the actor ships with residential proxy already selected and retries a blocked request on a fresh address rather than handing you the failure.

What you get

One row per company you submit. Every row opens with the same five bookkeeping fields (query, found, status, message, scrapedAt), then the company itself:

FieldWhat it is
companyUrl, slugCanonical page link, and the stable identifier after /company/. slug is your join key.
name, taglineCompany name, and the one-line tagline under it.
descriptionThe full About-us paragraph the company wrote about itself.
industryLinkedIn's industry label, e.g. "Technology, Information and Internet".
companySizeThe employee band the company reports for itself, as text: "5,001-10,000 employees".
employeesOnLinkedInHow many members actually list this company as their employer, as a number.
headquarters, founded, companyTypeLocation as printed, founding year as a number, and ownership type ("Privately Held", "Public Company").
websiteThe company's own site, unwrapped from LinkedIn's tracking redirect.
specialtiesSpecialty tags from the About section, as an array. Empty for companies that publish none, which is common.
followerCount, logoUrlExact follower count, not the rounded "1.7M" the signed-in UI shows, and the logo URL.
source, maskedWhether the row came from the page's structured data or the HTML fallback, and whether LinkedIn trimmed the page.

Two things worth knowing before you rely on a column. specialties is genuinely empty for many companies: Stripe publishes none, Shopify publishes twenty. And followerCount is read from the top card and the page's own meta description rather than pattern-matched across the page, because a company page also carries the follower counts of the "similar pages" in its sidebar.

Pricing

$5 per 1,000 companies, plus a $0.00005 start fee. Misses (found:false) are never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~linkedin-company-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
-X POST \
-H "Content-Type: application/json" \
-d '{"companies":["https://www.linkedin.com/company/stripe","shopify"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~linkedin-company-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"companies":["https://www.linkedin.com/company/stripe","shopify"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~linkedin-company-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"companies":["{{company}}"]}, mapping the row's company into the companies array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "LinkedIn Company Scraper, No Cookies | Apify" — the agent will find and run this actor.

How to use

  1. In the Apify Console. Open the actor page and click Start — the companies field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
  2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:
    curl "https://api.apify.com/v2/acts/accountable_eel~linkedin-company-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"companies":["https://www.linkedin.com/company/stripe","shopify"]}'
  3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
"companies": [
"https://www.linkedin.com/company/stripe",
"shopify"
]
}

One company per line. Paste the full company page link, or just the part after /company/. Accepted formats: https://www.linkedin.com/company/stripe, linkedin.com/company/stripe, stripe.

Optional fields: onlyFound drops the misses, includeKeywords / excludeKeywords filter rows by the text they contain, maxResults caps a trial run, testRun processes only the first five, and columns picks which fields come back. Concurrency and proxy live under Advanced.

Output

One row per item, for example:

queryfoundstatuscompanyUrlslugnametaglinedescriptionindustrycompanySizeemployeesOnLinkedInheadquartersfoundedcompanyTypewebsitespecialtiesfollowerCountlogoUrlsourcemaskedscrapedAt
stripetrueOKhttps://www.linkedin.com/company/stripestripeStripeHelp increase the GDP of the internet.Stripe builds programmable financial services. Millions of companies—from the world’s largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Headquartered in San Francisco and Dublin, the company aims to increase the GDP of the internet.Technology, Information and Internet5,001-10,000 employees16918South San Francisco, California2010Privately Heldhttps://stripe.com[]1687463https://media.licdn.com/dms/image/v2/D560BAQE2ZfJyfn-VCg/company-logo_200_200/B56ZlyKwpUKIAI-/0/1758557047806/stripe_logojsonldfalse2026-09-08T17:42:24.662Z

A miss comes back as a row with "found": false and is never charged.

Tips

  • slug is the join key, not name. Companies rebrand and rename their display name; the identifier after /company/ is what survives, and it is what you should key your table on.
  • Compare employeesOnLinkedIn against companySize rather than picking one. A company whose member count sits well above its stated band is either growing fast or has not updated its About page in years, and either one is a useful thing to know before a call.
  • Treat an empty specialties array as "publishes none", not as an error. Plenty of large companies fill in nothing there.
  • A wave of BLOCKED rows means the addresses you are running from are being asked to sign in. Lower Max concurrency, leave residential proxy on, and re-run those rows later. They cost you nothing the first time.
  • Feed the website field straight into a domain-based enrichment step. It is the clean destination URL, already unwrapped from LinkedIn's redirect, so it joins cleanly to anything keyed on domain.
  • Store founded as a number and companySize as text. The size band is a display string with a comma and a hyphen in it, and forcing it into a numeric column loses it entirely.

vs. alternatives

What it costsWhat you getTrade-off
This actor (linkedin-company-lookup)$0.005 per company found at the FREE tier, less on paid tiers, $0.00005 actor start, nothing for a missOne flat row per public company page: name, tagline, About text, industry, self-reported size band, employees on LinkedIn, headquarters, founding year, ownership type, website, specialties, followers and logoPublic company pages only. No funding, revenue or employee lists, because the logged-out page does not publish them. It looks up companies you name; it does not search for them.
HarvestAPI's linkedin-companyListed at $4 per 1,000 companiesThe category leader by some distance: 5,011 users in the last 30 days at a 4.48 rating, inside the store's top 50, and part of a family that also covers people search and postsCheaper per row and far more proven. Pick this one for the two-number headcount split, the free misses, and a start fee of $0.00005 rather than a per-run floor.
Clay$0.08 to $0.40 per enriched row in credits, on top of a seatA whole enrichment workspace: waterfalls across dozens of providers, plus the table and the sequencing around itIf you want one place that does everything and you are not counting rows, that is Clay. This is one column, priced per column, callable from Clay via its HTTP step.
Doing it yourselfYour time, plus residential proxy spend, plus keeping up with a sign-in wall that movesThe same fieldsWhat this absorbs: pulling the real Organization node out of a JSON-LD graph that also contains eight post-author stubs, unwrapping a website URL whose dots are percent-encoded, reading a follower count without catching the sidebar's other companies, and retrying a blocked address instead of failing the row.

Prices for third-party tools are their published list prices as of September 2026 and are not tracked here. Check the vendor before relying on the comparison.

FAQ

Do I need a LinkedIn account, or to paste in a cookie? No. It reads the public company page exactly as a signed-out browser gets it. You are never asked for credentials, a session cookie or an li_at token, and no account of yours is put at risk.

Why are there two headcount fields? Because LinkedIn publishes two different numbers and they mean different things. companySize is the band the company selected for its own About section. employeesOnLinkedIn counts the members who list it as their employer. For Stripe those are "5,001-10,000 employees" and 16,949. Keeping both is the honest answer; picking one for you would be a guess about which question you are asking.

Why did a row come back with found: false? One of four reasons, and status says which. BLOCKED: LinkedIn asked that request to sign in instead of serving the page. NOT_FOUND: no public company page exists at that address any more. BAD_FORMAT: the input was not a company page, most often an /in/ member profile pasted by mistake. REQUEST_FAILED: the request did not complete after retries. None of the four is charged.

Why is specialties empty for some companies? Because those companies publish none. The specialties list is an optional field the company fills in itself, and plenty of large, well-run pages leave it blank. An empty array means "nothing listed", never "we could not read it".

Does it return funding, revenue or a list of employees? No. None of those are on the logged-out company page. Employee-level data in particular sits behind the sign-in wall, and this actor does not go there.

What is masked? It is a guard carried over from the member-profile side of LinkedIn, where the site sometimes serves a trimmed page with values replaced by rows of asterisks. No company page captured while building this actor behaved that way, so expect false. If LinkedIn ever does trim a company page, the asterisks are stripped rather than passed through and the row is flagged so you can re-run it instead of importing placeholder text.

Can I pass a school or a showcase page? Yes. /company/, /school/ and /showcase/ links all use the same public template and all parse. A member profile (/in/) does not, and is rejected as BAD_FORMAT before a request is spent.

Am I charged for a miss? No. Billing fires only when a real company page was read. Blocked pages, missing pages and malformed input all produce a row explaining themselves, unless you turn on "Hide rows with no result", and none of them cost anything.

Do I need to configure a proxy? It is already configured. Residential proxy is the shipped default because LinkedIn's sign-in wall keys on the reputation of the address asking. You can change the group under Advanced, but lowering it is the most common reason a list comes back mostly blocked.

Is this a live fetch or a stored database? Live. Every run fetches the current page, and nothing is stored between runs. A company that updated its About section yesterday shows the new version today.

Can an AI agent call this directly? Yes. It is on the Apify MCP server, so an agent in Claude, Cursor or any other MCP client can find and run it by name, and the REST endpoint above works from any script or workflow tool.

Personal data, and your responsibility

This actor reads public LinkedIn company pages. Most of what it returns is information about an organisation rather than an individual, but company pages can still carry personal data, and in the EU and UK a small company's details can identify the people behind it. The actor reads nothing behind the sign-in wall and holds nothing between runs: each row is fetched live and written to your own dataset, which only you control.

Whether you may collect, store and use that data is a question about you and your purpose, not about this tool. If the GDPR applies to what you do next, you need a lawful basis, plus the duties around transparency, retention and honouring a request to be erased. LinkedIn's own User Agreement also restricts automated collection, and it binds anyone using it under an account. Nothing here is legal advice, and running this actor is not a determination that your use is lawful. That call, and the compliance work behind it, is yours.