Domain → Page → Contacts · the company ID is the page, in one number
LinkedIn company ID: how to find it, and why it is the key to store
The short answer
A LinkedIn company ID is the number LinkedIn gives each company page: 1035 for Microsoft, 3650502 for Figma. To find it from a domain, resolve the domain to the company's LinkedIn page, then read the ID from the company record. Store it with the account: a domain can be shared and a page's URL can be renamed, while the ID points to one page.
On this page6 sections
Every company page on LinkedIn has a number. Microsoft’s is 1035; Figma’s is 3650502. You rarely see it, because pages show a readable URL instead. But when you need to tie people to the right company across tools and months, that number is the most reliable value you can hold, and it is the next step after the guide on how to find employees of a company from its domain.
What is a LinkedIn company ID?
A LinkedIn company ID is the number LinkedIn assigns to a company page when the page is created: the company ID LinkedIn uses in its own tools and APIs. It identifies that page and no other. The page’s URL carries a readable name instead, such as linkedin.com/company/microsoft, which the page’s admins chose and can change.
- Definition LinkedIn company ID also called organization ID
- The number LinkedIn assigns to a company page, such as 1035 for Microsoft. It points to one page and stays the same when the page's URL name or its website changes.
PreciselyA LinkedIn company ID is the numeric identifier of a LinkedIn company page, written urn:li:organization followed by the number in LinkedIn's own APIs. In BlitzAPI, Company Enrichment returns it as linkedin_id, and every job in a person's experiences carries the ID of its company page as company_linkedin_id, so people and accounts can be joined on one number.
LinkedIn’s own tools sometimes write the ID as an organization URN, urn:li:organization:1035. It is the same number.
Why store the LinkedIn company ID rather than the domain or the URL?
Because the ID is the only one of the three that points to one page and never moves. Take Microsoft:
- Domainmicrosoft.com
- Typed into a website field
- Given by many pages, Sabena’s among them
- Microsoft’s own page lists news.microsoft.com
- Page URLlinkedin.com/company/microsoft
- Points to one page
- Its name can be changed by the page
- Lookalike pages exist (/microsoftcompany)
- Company IDThe key to store1035
- Points to one page
- Never changes
- Carried by every job at that page
- The domain is typed into a website field, and any page can type any domain. Sabena’s page gives a microsoft.com page as its website, and Microsoft’s own page lists news.microsoft.com.
- The page URL points to one page, but its name can be renamed, and lookalike pages use close names: a second page answers at linkedin.com/company/microsoftcompany.
- The company ID points to one page and stays with it. It is the matching key in its most compact form.
A domain can be shared. A URL can be renamed. The company ID stays with one page.
How do you find a LinkedIn company ID from a domain?
In two steps. Resolve the domain to the company’s page with Domain to LinkedIn, and check that the name matches the company you meant. Then send the page URL to Company Enrichment, which returns the company record with its linkedin_id, alongside the industry, the size, the headquarters, the domain and the website.
If you manage the page yourself, LinkedIn also shows the ID in the address of the page’s admin view. For the pages of other companies, and for many at once, the record is the faster route.
Where does the company ID show up in your data?
In every job. When a people endpoint returns a person, each position in the person’s experiences carries the company_linkedin_id of its company page. So once your accounts hold their ID, joining people to accounts is a comparison of two numbers.
- Account
- Figma
- Domain
- figma.com
- LinkedIn company ID
- 3650502
Your CRM
- job_title
- Director, Enterprise Sales
- company_linkedin_id
- 3650502
- job_is_current
- true
A person’s job, from any people endpoint
This is what makes the ID useful far beyond one search. People found with Employee Finder, leads resolved from their email, contacts imported from a list: each one points to a company ID, and each account holds one. The lead to account matching page applies it to inbound leads.
For builders
Two calls take you from a domain to the company ID. This part shows them with a real run.
How do you get the LinkedIn company ID with the API?
A company page URL in, the full company record out, with linkedin_id.
Send
company_linkedin_url- The page, from Domain to LinkedIn or from a person’s job.
Read
company.linkedin_id- The company ID: the value to store with the account.
company.linkedin_url, name- The page and its current name.
company.domain, website- The domain and the website the page gives, which can differ.
Each company record is one record; plans and rate limits are on the BlitzAPI pricing page.
A real run
On November 10, 2026, Microsoft’s record, trimmed to the identifiers:
{
"found": true,
"company": {
"linkedin_url": "https://www.linkedin.com/company/microsoft",
"linkedin_id": 1035,
"name": "Microsoft",
"domain": "microsoft.com",
"website": "https://news.microsoft.com"
}
}The same day, a person found among Figma’s employees, trimmed to one job:
{
"job_title": "Director, Enterprise Sales",
"company_linkedin_url": "https://www.linkedin.com/company/figma",
"company_linkedin_id": "3650502",
"job_is_current": true
}The record returns the ID as a number and the job as a string: compare them as text, or cast one side.
Before you ship
- Store linkedin_id, linkedin_url and the domain on each account: the ID to match, the URL to call the API, the domain to read.
- Join people to accounts on company_linkedin_id, and only on jobs where job_is_current is true.
- Normalize the type: linkedin_id comes as a number in the company record, company_linkedin_id as a string in a job.
- Matching accounts on the page URL alone: a renamed page breaks the match.
Sources and method
- Written by
- The BlitzAPI team
- Published
- API calls run on
- Company Enrichment, BlitzAPI API reference
- Domain to LinkedIn URL, BlitzAPI API reference
- Employee Finder, BlitzAPI API reference
The IDs, domains and websites of Microsoft, Figma and Sabena were read with the BlitzAPI API on November 10, 2026. The person in the second diagram is described by job title only.