LinkedIn Company Lookup

Independent LinkedIn data extraction Actor. This tool is not affiliated with, endorsed by, or operated by LinkedIn or Microsoft. It reads information exposed on a public company page; page access, field availability, and values can change without notice.

LinkedIn Company Lookup converts one linkedin.com/company/... URL into a source-dependent company snapshot. The possible contract covers identity, About text, website, industry, company size, type, headquarters, address, specialties, public source links, dynamic employee and follower counts, locations, highlighted people, update samples, Life-tab sections, and optional job details.

• A verified Apple run returned one company row with 20 of the 26 possible top-level keys.
• A second Apple run with max_jobs=1 returned one company Result and one independently charged Job record.
• Every returned row includes the canonical company URL, processing timestamp, status, page type, and Actor provenance.
• Empty values are omitted instead of invented, so downstream systems can distinguish observed data from unavailable data.

This is a snapshot extractor, not a verification service or a complete company database. Counts changed between two valid runs, highlighted people are not guaranteed decision-makers, and a successful cloud run can produce zero company rows if the source cannot be parsed. Review the Dataset before using it for outreach, scoring, hiring, or material decisions.

Run one company lookup · Connect through the Apify API

Why Choose This API

A public LinkedIn company page combines profile data, structured markup, page text, locations, Life content, and job routes. Their availability differs from company to company and over time. This Actor performs the page requests, extracts the available pieces, normalizes field names, removes empty values, and writes one traceable company object when a name can be parsed.

The output is useful for controlled enrichment because it preserves the source boundary. linkedin_url identifies the requested company page, processed_at identifies the snapshot time, and processor identifies the Actor version surface. Fields such as industry, company_size, company_type, headquarters, and specialties remain source labels; the Actor does not map them to an external taxonomy or independently confirm them.

Employee and follower counts are convenient signals, but they are not audited facts. In two Apple baseline runs less than a minute apart, the parsed employee and follower values differed. That may reflect a changing page, different responses, or source presentation. Store the timestamp and compare multiple snapshots before interpreting movement as organizational growth or decline.

Optional job collection is explicit. With max_jobs=0, the Actor skips the Jobs tab. A positive cap requests job links and details, but source access, deduplication, parsing, and the Job charge limit can reduce the returned array. The company Dataset row triggers the Result event; each retained job triggers the separate Job event before the array is written.

Quick Start Guide

Open the Actor input page and begin with one well-formed public company URL. Keep jobs disabled for the first run so you can validate the core profile at the lowest optional-event scope.

{
  "linkedin_url": "https://www.linkedin.com/company/apple/",
  "max_jobs": 0
}

Start the run, wait for a terminal status, and inspect the default Dataset. A populated run should contain at most one company row. If no row is present, check the status and try the source page later; do not assume that SUCCEEDED means a company was extracted.

For a second test, set max_jobs to 1. Confirm that the returned row contains a jobs array only when a job was collected and retained. Also inspect the run's charged-event counts: the verified job scenario produced Actor Start 1, Result 1, and Job 1, while the no-job scenario produced Job 0.

Once the shape is accepted, store the run ID, Dataset ID, input URL, requested job cap, item count, and timestamp together. That evidence makes later source changes and omitted fields easier to diagnose.

Input Parameters

The company URL is required. The job cap is optional and defaults to zero.

Parameter	Type	Range or format	Behavior
linkedin_url	string	https://www.linkedin.com/company/{slug}/	One public LinkedIn company page. The schema rejects non-company paths and unsupported URL forms.
max_jobs	integer	0 to 100; default 0	Requested number of job details. Zero skips the Jobs tab. Positive values can return fewer jobs because of source availability, parsing, deduplication, or charge limits.

The Actor accepts one company per run. It does not accept a list of URLs, a company-name search, an employee URL, a personal profile, a Sales Navigator URL, credentials, cookies, a date range, or a geographic filter. Use separate runs for separate companies and keep each run independently traceable.

The runtime normalizes the URL to lowercase and validates that it contains the LinkedIn company path. The public input schema intentionally requires an HTTPS LinkedIn company URL so malformed values fail before network work begins. The job cap bounds attempted detail collection; it does not promise a matching number of live or complete postings.

Output Data Schema

The possible top-level contract contains 26 keys. The formatter removes null, empty-string, empty-array, and empty-object values, so real rows are sparse. Consumers should test key presence instead of assuming every key exists.

Field group	Possible keys	Important boundary
Provenance and identity	processor, processed_at, status, type, linkedin_url, name	A row is written only when a company name is parsed.
Profile text	headline, about, website, industry, company_size, company_type, founded	Source labels and company-provided text; fields may be omitted.
Place and contact	headquarters, address, locations, phones, social_links	Public source values, not independently verified contact or legal-office data.
Classification and media	specialties, logo_url, life	Company-declared labels and source assets; media URLs may expire.
Dynamic signals	employee_count, follower_count	Parsed snapshots, not audited totals or stable time series.
People and activity	featured_employees, updates	Source-selected samples, not complete rosters, decision-maker lists, or post archives.
Optional hiring data	jobs	Retained job details only; each retained item uses the separate Job event.

This abridged sample uses values from the verified no-job Apple run. It intentionally omits large arrays and absent keys.

{
  "processor": "https://apify.com/agentx/linkedin-company-lookup?fpr=aiagentapi",
  "processed_at": "2026-07-23T21:21:03+00:00",
  "status": "success",
  "type": "company",
  "linkedin_url": "https://www.linkedin.com/company/apple/",
  "name": "Apple",
  "website": "http://www.apple.com/careers",
  "industry": "Computers and Electronics Manufacturing",
  "company_size": "10,001+ employees",
  "company_type": "Public Company",
  "headquarters": "Cupertino, California",
  "employee_count": 206263,
  "follower_count": 18337789,
  "specialties": [
    "Innovative Product Development",
    "World-Class Operations",
    "Retail"
  ]
}

Nested objects are also source-dependent. A location can include is_primary, label, address_lines, and directions_url. A highlighted person can include a name, LinkedIn URL, image URL, subtitle, and source influencer flag. A job can include its LinkedIn URL, title, posted text, location, applicant count, description, employment type, seniority, function, and industries. Any subset can be absent.

Integration Examples

The stable Actor ID is lmgxLM2RjocEgg6m2; the full name is agentx/linkedin-company-lookup. With an Apify client, call the Actor using the input object above, wait for completion, then read defaultDatasetId. Treat an empty Dataset as a supported business outcome, not as a transport error.

For HTTP integrations, POST the JSON input to the Actor run endpoint with an Apify token, poll the returned run ID, and fetch items from the resulting Dataset. Never embed the token in client-side code or logs. Persist the terminal status message because it can explain why a run completed without a row.

MCP clients should fetch current Actor details first, then call the Actor. A minimal company-only payload is:

{
  "actor": "agentx/linkedin-company-lookup",
  "input": {
    "linkedin_url": "https://www.linkedin.com/company/apple/",
    "max_jobs": 0
  },
  "callOptions": {
    "memory": 256,
    "timeout": 300
  },
  "waitSecs": 45
}

If the MCP wait window expires while the run is still active, poll the returned run ID rather than launching a duplicate. After completion, read the Dataset by ID and inspect its top-level keys. For a positive job cap, also inspect charged-event counts and the actual length of jobs; the requested cap and returned count can differ.

For scheduled monitoring, compare snapshots on canonical linkedin_url, but do not treat a missing field as a confirmed real-world change. Page variants and temporary access conditions can remove data from one run. Require repeated observations or another authoritative source before escalating an alert.

Pricing & Cost Calculator

The Actor uses pay-per-event pricing. Four event types are represented locally: metered Actor Usage, Actor Start, the primary company Result, and optional Job details. Prices shown by Apify for your account and run are authoritative.

Event	Trigger	Price
Actor Usage	Runtime, proxy, and storage consumption	$0.00001 per metered usage unit
Actor Start	The Actor starts; platform memory rules can affect counted starts	$0.01
Result — Free	One company row written to the default Dataset	$0.20000
Result — Bronze	One company row written to the default Dataset	$0.19333
Result — Silver	One company row written to the default Dataset	$0.18667
Result — Gold, Platinum, Diamond	One company row written to the default Dataset	$0.18000
Job	Each retained job detail included in the company row	$0.0028

At the Free-tier Result rate, a populated company-only run contributes $0.20000 for Result, plus Actor Start and metered Actor Usage. A populated run with one retained job contributes $0.20280 for Result plus Job, before Start and Usage. A zero-row run has no Result or Job event but can still incur Start and Usage.

Set max_jobs=0 until the company source is known to work. When jobs are needed, raise the cap gradually and leave any maximum-total-charge setting large enough for the company Result, requested Job events, Start, and Usage. A billing cap is not a production limit and can cause fewer jobs to be retained.

Use Cases & Applications

CRM teams can attach source-reported industry, company size, company type, headquarters, website, and specialties to an existing account record. Keep the source URL and processing time, and mark values as observations rather than verified corporate registry data.

Market researchers can collect periodic snapshots for a defined company panel. Employee and follower counts may support directional analysis after validation, but two close runs can differ. Use consistent timing, retain raw observations, and avoid presenting a single delta as confirmed growth or contraction.

Talent and hiring analysts can request a small number of jobs alongside the company profile. The job array can provide titles, locations, posting text, descriptions, and classification fields. It is not a complete vacancy feed, and a missing posting does not prove that the role closed.

Account-based marketing teams can use the company page, declared specialties, public website, and source-highlighted people as research starting points. Do not interpret featured_employees as a verified executive list or permission to contact someone. Apply your organization's data-protection, outreach, and suppression rules.

Change-detection systems can compare present keys, counts, locations, and Life sections across runs. Alerts should tolerate transient omissions, expired media URLs, page restructuring, and an empty Dataset. Require human review for consequential actions.

FAQ

Does this return a complete LinkedIn company profile?

No. It returns the subset exposed and parsed during that run. The contract has 26 possible top-level keys, but the verified company-only Apple row contained 20. Empty values are omitted.

Is employee_count exact and verified?

It is a numeric value parsed from LinkedIn source data, not an audited workforce total. Two valid baseline runs returned different values. Preserve the timestamp and corroborate material conclusions.

Are featured employees decision-makers or contact leads?

Not necessarily. They are people highlighted by the source page. Their inclusion does not confirm current role, authority, relationship, or outreach suitability.

Why are jobs missing when max_jobs is positive?

The setting is a requested cap. The source may expose fewer links, detail requests may fail, duplicates may be removed, or the Job charge limit may retain fewer items.

Can a successful run return no company row?

Yes. If the overview page cannot be fetched or a company name cannot be parsed, the Actor can finish without writing a Dataset item. Check both status and Dataset count.

Does the Actor support personal profiles or company-name search?

No. It accepts one LinkedIn /company/ URL. It does not search names or process /in/ member profiles.

Trust & Certifications

The verified readiness baseline used the current cloud Build with 256 MB memory. One Apple run with jobs disabled wrote one company Result and zero Jobs; a second run with a one-job cap wrote one company Result and one Job. MCP independently returned the sparse top-level object and the nested job record.

No accuracy, completeness, uptime, freshness, employment, identity, contact, privacy, legal-compliance, or third-party certification is claimed. LinkedIn controls the source, Apify controls the cloud platform, and this Actor normalizes what it can observe. Source markup, access behavior, counts, locations, people, posts, and jobs can change independently.

Production consumers should monitor terminal status, Dataset item count, key presence, charged events, runtime, and unexpected value shifts. Protect API tokens and Datasets, set retention rules, restrict access to personal information in highlighted-person or job content, and document the purpose of processing.

Legal & Compliance

Use the Actor only for purposes, data, and volumes permitted by applicable law, contracts, and platform rules. You are responsible for the legal basis, notices, retention, access controls, outreach rules, and decisions applied to the output. Public availability does not remove intellectual-property, privacy, employment, or database-right obligations.

Review LinkedIn's User Agreement and Privacy Policy, plus the Apify General Terms and Conditions, Actor Terms, and Privacy Policy. These links are informational and do not constitute legal advice.

Do not use the output to make automated employment, credit, housing, insurance, eligibility, or similarly consequential decisions without an appropriate legal and human-review process. Do not infer sensitive traits from names, images, locations, specialties, posts, or employment content.

Related Tools

For broader vacancy discovery, use All Jobs Scraper. Add source-dependent local business context with Google Maps Store Scraper, or inspect a public brand profile with Instagram Creator Scraper.

For adjacent research, compare interest with Google Search Trends API, inspect seller-profile candidates with eBay Seller Leads API, or search product sources with All Shopping Scraper. Each Actor has independent inputs, output semantics, pricing, and source risks.

Support & Community

For a reproducible issue, provide the run ID, public company URL, requested max_jobs, terminal status message, Dataset item count, observed top-level keys, and charged-event counts. Never send an Apify token, proxy password, database credential, private Dataset, or unrelated personal information.

Use AgentX support on Telegram for Actor-specific help and the Apify community for platform questions. State whether the issue concerns source access, an omitted field, an unexpected value, Job collection, event charging, or cloud execution.

Last updated: July 23, 2026.