How to Find a Company's LinkedIn Page by Name

The problem: a name, and no URL

Every enrichment job I have run starts the same way: a spreadsheet of company names and a blank column where the LinkedIn page should go. Filling each URL by hand means a search, a squint at the results, and a copy-paste, times a few hundred rows. I built the LinkedIn Company API so that column fills itself.

The LinkedIn Company API is a LinkedIn company URL finder and enrichment tool: hand it a list of company names and it resolves each one to its most popular public company page, then returns the firmographics as one clean JSON row per company.

What the scraper returns

Each row carries the fields a logged-out visitor can see on a public company page:

• Name, plus the requested name it resolved from

• Industry and specialties

• Company size band and headquarters

• Follower count and website

• Public LinkedIn URL and companyId

Names that match nothing come back as an error row, not a charge, so one bad name does not sink a 500-name batch.

Run it in three steps

Open the LinkedIn Company API, click Try for free, and paste your company names or page URLs. Run it, then export the dataset as JSON or CSV when it finishes.

Use it as a REST API

Every run is reachable over REST, so you can trigger it from your own code and read the dataset back: pass a list of company names or URLs, poll the run, and pull the rows. The LinkedIn company data API for Python task ships a runnable apify-client script if you would rather copy than write.

Wire it into Claude with MCP

Connected through Apify's MCP server, the API becomes a tool that Claude, Claude Code, and Cursor can call. Ask "find the LinkedIn pages for these ten companies and pull their size and industry" and the agent runs it, no scraping code. The Get LinkedIn company data in Claude via MCP task walks through setup.

What people build with it

RevOps teams stamp every CRM account with a current size and industry. Researchers map a sector into a firmographics sheet. Sales teams turn a raw name list into enriched leads. The full set of runnable patterns lives on the examples page and the project page.

FAQ About the LinkedIn Company Scraper

Where does the LinkedIn company scraper get its data?

Only from public company pages, the same fields a logged-out visitor sees: name, industry, size band, headquarters, followers, specialties, and the public URL. No employee lists and no login-gated content.

How do I call the scraper as an API?

Send a POST to the run endpoint with your company names or URLs, then read the dataset as JSON or CSV. Billing is per company returned, about half a cent each, so a 1,000-name batch runs around five dollars.

Can I run the LinkedIn scraper from Claude or Cursor?

Yes. Over MCP it shows up as a callable tool in Claude, Claude Code, and Cursor, returning the same rows as a console run.

Can an AI agent pay for this scraper in USDC with x402?

Yes. The LinkedIn Company API supports agentic payments via the x402 protocol, so AI agents and MCP clients can pay for runs in USDC on Base with no Apify account or API token. Point your agent at the Apify MCP server and it can discover, pay for, and run the scraper autonomously; the Apify x402 announcement has the details.

Issues get a same-day reply. Point the LinkedIn Company API at your name list and the URL column fills itself.