# Companies (/docs/api/companies)



The Companies surface resolves a LinkedIn company slug or numeric ID
into a structured `Company` record — industry, headcount band, HQ,
locations, follower count, last-funding signals where available.
Pair with the employees endpoint for ICP company-list expansion.

<EndpointList topic="companies" />

## Get company by slug [#get-company-by-slug]

<EndpointDemo id="companies-get" />

The slug is the `universalName` — the tail of
`linkedin.com/company/<slug>`. Always lowercase. Cache-first;
extension fills on miss.

## Get company by ID [#get-company-by-id]

<EndpointDemo id="companies-get-by-id" />

Resolves by numeric LinkedIn company ID. Useful when you only have the
ID from a People search (`currentCompany`) or a Company Posts
`actorUrn` and the slug is stale, renamed, or unstable.

## Posts by company [#posts-by-company]

<EndpointDemo id="companies-posts" />

The latest content from a company page. Spot product launches, hires,
earnings notes, and PR pulses — every row carries the same activity ID
shape as [`/v1/posts/:id`](/docs/api/posts), so you can drill in for
reactor lists.

## Employees at company [#employees-at-company]

<EndpointDemo id="companies-employees" />

Paginate employees with role and location filters. Pair naturally with
[`GET /v1/search/people`](/docs/api/search) when you need broader
filters than what this surface exposes; this endpoint is the right
tool for "who works here, paged" while search is right for "who
matches this ICP across companies."

LinkedIn's own people-at-company page caps visible results at \~1,000
regardless of headcount; this endpoint inherits that ceiling.

## Notes [#notes]

* 3 credits per company read; 5 credits per employees page (flat, not
  per employee).
* Company records cache for 14 days; pass `?fresh=true` to force a
  re-capture.
* Companies that have been renamed or merged on LinkedIn surface as
  `301`-style redirects — we follow them transparently.