Home › Guides › Company ID crosswalk
Company ID crosswalk: one company name in, the join keys out
Company data lives in a dozen systems that do not share a key. This actor takes a company name or Wikidata Q-ID and returns the identifiers recorded for it on Wikidata — the LEI, the ISIN and ticker, the SEC CIK, the VAT number, national registry numbers, and the OpenCorporates, Crunchbase and LinkedIn handles: the join keys that let the rest of your stack agree on who a company is.
Who it is for
- Data engineers and RevOps teams — resolving the same company across CRM, finance and vendor datasets that each use a different key.
- Enrichment pipelines — that need one identifier before they can call the next source.
- Analysts mapping corporate structure — who want a first-pass parent and subsidiary tree.
What you get
One row per matched organization, in the same column layout as the other foXLabs company datasets:
| Group | Fields |
|---|---|
| Identifiers | lei, isin, ticker, stockExchanges, secCik, taxNumber (VAT), nationalRegistryIds (by scheme), openCorporatesId, crunchbaseId, linkedinId, rorId |
| Identity | companyName (English label), registrationNumber (Wikidata Q-ID), description, legalForm, incorporatedOn, website, industry |
| Size | employees, revenue and totalAssets (each with currency) |
| Location | city (headquarters), countryName |
| Structure and people | parentCompany, subsidiaries, chiefExecutive |
| Provenance | sourceUrl (Wikidata entity page), query, scrapedAt, and error when a lookup fails |
An example row for Siemens:
{
"companyName": "Siemens",
"registrationNumber": "Q81230",
"description": "German multinational conglomerate company",
"lei": "W38RGI023J3WT1HWRP32",
"isin": ["DE0007236101"],
"taxNumber": "DE129274202",
"rorId": "059mq0909",
"openCorporatesId": "de/F1103R_HRB12300",
"crunchbaseId": "siemens",
"linkedinId": "siemens",
"website": "https://www.siemens.com/",
"industry": "electrical engineering",
"employees": 370000,
"revenue": "75636000000 EUR",
"incorporatedOn": "1847-10-01",
"city": "Munich",
"countryName": "Germany",
"sourceUrl": "https://www.wikidata.org/wiki/Q81230"
}
Use cases
- Entity resolution. Map a name to LEI, ISIN, CIK and VAT so your systems can agree who a company is.
- Enrichment fan-out. Get the CIK, then pull SEC financials; get the LEI, then pull ownership; get the VAT number, then validate it in VIES.
- Ownership mapping. Parent and subsidiary links give you a first-pass corporate tree.
How to run it
Give the actor company names or Wikidata Q-IDs. This is the prefilled input:
{
"queries": ["Siemens", "Novo Nordisk", "Q81230", "Shopify"],
"maxResultsPerQuery": 5
}
queries— company names or Q-IDs. Names are matched against Wikidata’s own search and filtered to organizations.maxResultsPerQuery— caps how many rows one query may produce.
No API key and no login are needed. Results export to CSV, Excel, JSON, XML or HTML, or can be pulled through the Apify API.
You pay only for delivered rows. A query that finds nothing still returns a row carrying your query and an error explaining why — and that row is not charged.
Honest limits
- Coverage follows Wikidata. It is best for listed and well-known companies. A small private firm may have no Wikidata item at all — you get an explanatory row, not a wrong match.
- Not every company has every key. A row carries only the identifiers Wikidata records for that item, so expect gaps for less prominent companies.
- Community-edited figures. Identifiers such as LEI, ISIN and CIK are reliable because they are externally validated. Financial figures are as good as the last editor and carry the year they refer to.
- Names can match several items. A name query returns up to
maxResultsPerQueryorganizations; checkdescriptionandcountryName, or query the Q-ID directly. - Labels, not Q-IDs. Entity-valued fields such as industry, headquarters and parent are resolved to English labels in one batched extra request.
Where the data comes from
Wikidata publishes its structured data through a documented open API with no key, and releases it into the public domain under CC0, explicitly for reuse. Every run queries it live; Wikidata is edited continuously.
Related data and guides
- Browse the company and organization datasets on the home page.
- SEC filings, enforcement and the LEI — what the CIK and LEI unlock once you have them.
- KYB company verification — checking an identified company against its national register.
- ROR research organization data — the same crosswalk idea for universities, hospitals and research institutes.
Frequently asked questions
Where do the identifiers come from?
From Wikidata, which publishes its structured data through an open API with no key, under a CC0 public-domain dedication.
How reliable are the IDs?
Identifiers such as LEI, ISIN and CIK are reliable because they are externally validated. Financial figures are community-edited — as good as the last editor — and carry the year they refer to.
What happens if a company is not on Wikidata?
Coverage is best for listed and well-known companies. A small private firm may have no Wikidata item at all: you get a row explaining why, not a wrong match, and that row is not charged.
Can I search by Wikidata Q-ID?
Yes. Put the Q-ID, such as Q81230, in queries alongside company names.
What do I do with the IDs next?
Fan out: use the CIK to pull SEC financials, the LEI to pull ownership, and the VAT number to validate in VIES.
Start with the prefilled input — Siemens, Novo Nordisk, a Q-ID and Shopify — and export the identifiers to CSV, Excel or JSON.
Open Company ID Crosswalk on Apify →