Social Fetch
Get API key
LinkedIn hub

LinkedIn Company API

Look up a public LinkedIn company page by vanity URL and get structured JSON — name, description, industry, follower and employee metrics, and funding when LinkedIn shows it.

GET /v1/linkedin/companies

1 credit per successful request.

Try in playgroundFull API docs

About this endpoint

Account mapping and competitive research usually start from a company page, not a person `/in/…` URL. You want the public card: legal-ish display name, about text, industry, HQ, follower count, employee range, website. Building that yourself means babysitting LinkedIn HTML and login walls that break on a schedule.

`GET /v1/linkedin/companies` takes one `url` query param: a public company page (`https://www.linkedin.com/company/{slug}`), a bare slug, `company/{slug}`, or `@slug`. Use the vanity slug, not a numeric company id. Branch on `data.lookupStatus` before you write — `found` vs `not_found`. When found, `data.company` holds identity fields (name, handle, description, slogan, website, logo, industry, type, founded year, headquarters, employee range, specialties, location). `data.metrics` has followers and employees. The payload can also include similar companies, featured employees, a few recent posts, and funding when those blocks are public.

This route is company pages only. Person profiles use `GET /v1/linkedin/profiles`. Schools and organization-guest pages use `GET /v1/linkedin/organizations`. For a full company post feed with pagination, use `GET /v1/linkedin/companies/posts`. Pricing is 1 credit per successful request; trust `meta.creditsCharged` on the response.

LinkedIn Company API FAQ

How do I fetch a LinkedIn company page via API?

Call `GET /v1/linkedin/companies` with your Social Fetch API key (`x-api-key`) and a company `url` query param (for example `https://www.linkedin.com/company/shopify/`). Read `data.lookupStatus` and `data.company` in the JSON response. Full parameters are in the API docs.

How much does the LinkedIn Company API cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

What URL format does the LinkedIn company endpoint accept?

Pass a public `/company/{slug}` URL, the vanity slug alone, `company/{slug}`, or `@slug`. Numeric company ids are rejected — use the vanity slug (for example `google`, not a digit-only path segment). Person `/in/…` URLs belong on the profile endpoint.

What fields does the LinkedIn company response include?

When `lookupStatus` is `found`, you get company identity fields (name, handle, description, website, logo, industry, headquarters, employee range, specialties, location), metrics (followers, employees), and optional blocks for similar companies, featured employees, recent posts, and funding when LinkedIn exposes them publicly.

LinkedIn company vs person profile vs organization endpoint?

Use `GET /v1/linkedin/companies` for `/company/…` pages. Use `GET /v1/linkedin/profiles` for `/in/…` person URLs. Schools and organization-guest pages use `GET /v1/linkedin/organizations`. Sending the wrong page type returns a validation error pointing at the correct route.

Does this endpoint return the full company post history?

It may include a small `recentPosts` sample on the company card. For a paginated company post list, call `GET /v1/linkedin/companies/posts` with the same company URL. See the LinkedIn platform hub for both routes.

What happens when a LinkedIn company page is not found?

The call returns a typed `lookupStatus` of `not_found` with no company card to upsert. Keep `meta.requestId` if you need to retry or escalate that row.

Other LinkedIn endpoints