LinkedIn Company API

LinkedIn Company API is a linkedin company profile scraper that turns one public company URL into a 25-field JSON snapshot with firmographics, people, activity, Life content, and optional job details.

• One run processes exactly one public LinkedIn /company/ URL and returns at most one company row.
• The sparse Dataset contract exposes 25 possible top-level fields without inventing missing source values.
• Job collection is optional from 0 to 100 requested details, and only retained jobs are billed.
• A failed optional route or image can be omitted while the valid company profile remains usable.

Run a one-company test · View the API

The smallest useful FREE-tier test uses the prefilled Microsoft URL with max_jobs: 1; the company Result and Actor Start cost $0.085, while a retained job adds $0.0035 and source availability can return no job.

What does LinkedIn Company API do?

LinkedIn Company API converts a public company page into one traceable JSON object for enrichment, research, hiring context, or monitored company panels. The result can contain company identity, About text, slogan, website, industry, employee range, company type, headquarters, address, specialties, employee and follower counts, public locations, highlighted people, update samples, Life sections, and optional jobs.

The Actor keeps source boundaries visible. linkedin_url identifies the requested page, processed_at records the snapshot time, and optional keys appear only when values are available. It does not search by company name, accept a list of URLs, sign into LinkedIn, verify corporate facts, discover private contacts, or turn highlighted people into a complete employee roster.

The supported source is LinkedIn's public company surface. LinkedIn controls what a visitor can see and how the page changes over time, so the Actor is a structured observation tool rather than a legal-entity registry or guaranteed historical database.

How do I run LinkedIn Company API?

LinkedIn Company API runs from one company URL and an optional job-detail cap.

1. Open the Actor input page.
2. Keep the prefilled Microsoft company URL or replace it with another public HTTPS /company/ URL.
3. Leave max_jobs at 1 to test one optional job, or use 0 for a company-only row.
4. Start the run, wait for the terminal message, and inspect the default Dataset independently of the run status.
5. Save the run ID, Dataset ID, canonical URL, item count, and processing timestamp with any downstream record.

{
  "linkedin_url": "https://www.linkedin.com/company/microsoft/",
  "max_jobs": 1
}

The job value is a ceiling per run, not a promise. LinkedIn can expose fewer links, a detail request can fail, and a maximum-total-charge policy can retain fewer jobs than requested.

What data does LinkedIn Company API return?

LinkedIn Company API returns one sparse company object with up to 25 top-level fields and nested arrays for locations, people, activity, Life content, and jobs.

Group	Possible fields	Interpretation
Identity	platform, type, linkedin_url, name	Source and canonical company identity
Profile	about, slogan, website, industry, company_size, company_type, founded	Public company text, source labels, and founding year
Place	headquarters, address, locations	Headquarters text and public location records
Signals	specialties, employee_count, follower_count	Declared specialties and dynamic snapshot counts
Media and people	logo_url, featured_employees	Stored logo and source-highlighted people when available
Activity	updates, life, jobs	Update samples, Life sections, and retained job details
Processing	status, processor, processed_at	Result state, producing Actor, and UTC timestamp

This abbreviated example omits nested arrays; a real row can contain all 25 top-level fields when the source supplies them.

{
  "platform": "LinkedIn",
  "type": "company",
  "linkedin_url": "https://www.linkedin.com/company/microsoft/",
  "name": "Microsoft",
  "industry": "Software Development",
  "company_size": "10,001+ employees",
  "company_type": "Public Company",
  "founded": 1976,
  "headquarters": "Redmond, Washington",
  "employee_count": 233189,
  "status": "success",
  "processor": "https://apify.com/truefetch/linkedin-company-api",
  "processed_at": "2026-08-12T18:45:00+00:00"
}

A nested job can include its LinkedIn URL, title, posted text, location and work mode, applicant count, full description, job level, employment type, function, industries, the posted salary range with its currency and period, and the company logo. A nested highlighted person can include name, public profile URL, stored image, subtitle, and a source-provided influencer flag. Missing keys remain absent instead of being replaced with guessed values.

What inputs can I configure?

LinkedIn Company API exposes one required URL and one optional integer; there are no cookies, credentials, proxy settings, or hidden request filters.

Parameter	Type	Required	Range or format	Behavior
linkedin_url	string	Yes	https://www.linkedin.com/company/{slug}/	Selects one public company page; the runtime canonicalizes the host, slug case, slash, query, and fragment
max_jobs	integer	No	0 through 100	0 skips the Jobs tab; a positive value requests up to that many details and can return fewer

The runtime rejects HTTP URLs, foreign hosts, credentialed URLs, personal-profile paths, extra company subpaths, booleans, negative job caps, and values above 100. Separate runs are required for separate companies.

What platforms and markets does LinkedIn Company API cover?

LinkedIn Company API covers the public www.linkedin.com/company/ path without a country or language selector. Companies from different markets can be requested when their public page is reachable, but labels, locations, languages, available tabs, and field density vary by organization and response.

The Actor does not claim complete geographic coverage or a localized taxonomy. A company can have multiple pages, a showcase page can differ from its parent organization, and a headquarters label is the source's presentation rather than an independently verified registered office. URLs outside the strict /company/{slug}/ contract are rejected.

Why use LinkedIn Company API?

LinkedIn Company API is useful when a workflow needs a stable sparse envelope around a changing public page. A Dataset item is easier to validate, export, join, and monitor than copied page text because the canonical URL, named fields, status, producing Actor, and processing time travel together.

Jobs remain opt-in. A company enrichment workflow can use max_jobs: 0 and avoid Job events, while a hiring-context workflow can request a small number without changing the profile schema. Separate Result and Job events make the billing unit visible.

The omission policy is equally important. An absent headquarters, count, image, person subtitle, or job field is not silently converted into a zero or an empty factual claim. Downstream systems can route sparse records for review rather than accepting fabricated completeness.

Who is LinkedIn Company API for?

LinkedIn Company API is for developers, revenue operations teams, researchers, recruiters, and analysts who already know the company page they want to observe.

CRM teams can attach industry, company_size, company_type, headquarters, website, and specialties to an existing account while storing the source URL and time. Researchers can collect repeated snapshots for a defined panel and compare present keys, counts, locations, or Life sections cautiously. Talent teams can request a small job cap to place hiring information beside company context.

It is not suitable as a sole source for identity verification, regulated eligibility decisions, exact workforce accounting, a complete vacancy feed, private contact discovery, or bulk prospect-list generation from company names. Those workflows need additional authoritative sources, permission checks, or a different product contract.

How can I use LinkedIn Company API through the API or MCP?

LinkedIn Company API can be called by stable Actor ID zSJMwA6pZ817yodN3 or name form truefetch/linkedin-company-api, then consumed from defaultDatasetId after the run finishes.

curl -X POST "https://api.apify.com/v2/acts/zSJMwA6pZ817yodN3/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"linkedin_url":"https://www.linkedin.com/company/microsoft/","max_jobs":1}'

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("zSJMwA6pZ817yodN3").call(run_input={
    "linkedin_url": "https://www.linkedin.com/company/microsoft/",
    "max_jobs": 1,
})
items = list(client.dataset(run["defaultDatasetId"]).iterate_items())

MCP clients can use the same scenario:

{
  "actor": "truefetch/linkedin-company-api",
  "input": {
    "linkedin_url": "https://www.linkedin.com/company/microsoft/",
    "max_jobs": 1
  },
  "callOptions": {"memory": 256, "timeout": 300},
  "waitSecs": 45
}

If a client wait window expires, poll the returned run ID instead of starting a duplicate. Keep Apify tokens in server-side secret storage and do not place them in browser code, logs, Dataset items, or support messages.

How much does LinkedIn Company API cost?

LinkedIn Company API uses pay-per-event pricing: Actor Start is $0.01, a company Result ranges from $0.075 to $0.05625 by plan, and a retained Job ranges from $0.0035 to $0.00263.

Event	FREE	BRONZE	SILVER	GOLD	PLATINUM	DIAMOND
Actor Start	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000	$0.01000
Company Result	$0.07500	$0.06750	$0.06000	$0.05625	$0.05625	$0.05625
Retained Job	$0.00350	$0.00315	$0.00280	$0.00263	$0.00263	$0.00263

The smallest saved FREE-tier company-only run is $0.01 + $0.075 = $0.085; a retained job adds its plan's Job event price. A run that pushes no company row has no Result event, and an unavailable or unretained job has no Job event. Check the live pricing page before setting a maximum-total-charge policy because prices can change.

How does LinkedIn Company API compare with alternatives?

LinkedIn Company API trades breadth for a narrow, traceable one-company contract. Manual review is often better for one high-stakes organization when a person needs visual context, interactive navigation, and immediate interpretation. It is harder to repeat consistently, export as sparse JSON, or connect to a scheduled Dataset workflow.

LinkedIn's own company page is the authoritative presentation surface and is preferable when a person needs the latest visible page experience. A general business database may be preferable when the requirement is normalized industries, legal-entity resolution, historical coverage, or verified facts from other licensed sources.

Choose another workflow if the input must be a company name or domain, if hundreds of URLs must run as one batch, if private or login-only data is required, or if a complete employee roster is essential. This Actor is designed for one known public company URL and source-dependent fields.

What are the limits and troubleshooting steps?

LinkedIn Company API can return sparse data or no row when the public source is unavailable, changed, or missing a parsable company identity.

• No Dataset item: verify HTTPS and the exact /company/{slug}/ path, confirm the public page opens, inspect the terminal message, and retry later.
• Missing field: treat absence as “not observed in this snapshot,” compare another run, and do not substitute a factual zero.
• Fewer jobs than max_jobs: compare the requested cap, returned jobs length, and charged Job events; source links, details, and charge policy can each reduce the array.
• Missing media: keep the valid company data; an image is removed when it cannot be downloaded and stored safely.
• Changing counts: preserve processed_at and require repeated observations before interpreting employee or follower movement.
• Expired client wait: poll the existing run by ID instead of launching a duplicate request.

For support, include the run ID, redacted input, terminal status, Dataset item count, requested and retained job counts, and the exact missing or unexpected key. Never include tokens, proxy credentials, private Dataset content, or unrelated personal data.

Frequently asked questions

LinkedIn Company API answers common questions about one-company extraction, sparse output, billing, and repeat monitoring.

Is this a linkedin company profile scraper for public pages?

Yes. It accepts one public company URL and returns the subset available in a 25-field sparse contract; it does not sign in or access private profiles.

Can a linkedin company profile scraper return job details?

Yes. Set max_jobs from 1 to 100, then compare the returned array with Job event charges because the requested cap can exceed what is retained.

Does every company return all 25 fields?

No. Company pages differ, and optional values are omitted when they are not available in the response used for that run.

Are employee and follower counts verified facts?

No. They are dynamic source snapshots, so important conclusions should use timestamps, repeated observations, and another authoritative source.

Are highlighted employees verified decision-makers?

No. Source-highlighted people do not establish current employment, authority, identity, relationship, or permission to contact.

Can I submit a personal profile, company name, or URL list?

No. The only supported target is one public LinkedIn company URL under /company/.

Can I schedule repeated company snapshots?

Yes. Apify schedules can start repeated runs, but each run handles one company and changes should be confirmed across multiple observations.

What happens when no company row is saved?

No Result or Job event is charged, although Actor Start still applies. Inspect both the terminal message and Dataset count.

Related TrueFetch Actors

LinkedIn Company API pairs with three separate TrueFetch products when the workflow extends from one company profile to people or broader vacancy discovery.

• LinkedIn Profile API — use a public member-profile URL under a separate personal-profile schema.
• LinkedIn Job Listing — focus on LinkedIn vacancy discovery instead of a company snapshot.
• Job Search — search jobs across a broader source set with independent inputs and pricing.

Review each Actor's current input, Dataset contract, source boundary, and pricing before combining records.

Support

LinkedIn Company API support covers valid company URLs, missing fields, optional jobs, event counts, Dataset access, and integration behavior; open an Issue with reproducible details.

Include the run ID, redacted input, terminal message, Dataset item count, observed key set, and requested versus retained job count. Do not send credentials, tokens, private Dataset content, or unrelated personal information.

Run a one-company test · View the API

Last Updated: August 12, 2026