GLEIF LEI KYB Lookup – Company Name to LEI & Parent

What does GLEIF LEI KYB Lookup do?

GLEIF LEI KYB Lookup queries the official GLEIF LEI API (https://api.gleif.org/api/v1/) to resolve company legal names and/or LEI codes into a flat, KYB-friendly dataset. It is built for compliance, AML/KYB agencies, sales ops, and counterparty enrichment — without scraping or API keys.

Use it as a structured LEI lookup / company name to LEI / GLEIF parent hierarchy enrichment step in your pipelines.

Why use this Actor?

Store LEI Actors often stop at a basic name match. This Actor focuses on KYB workflows:

• Bulk name → LEI and exact LEI → record resolve
• Registration status and next renewal date for freshness checks
• Direct parent LEI and ultimate parent LEI when GLEIF publishes the relationship
• Legal + headquarters addresses (organization-level only — no personal officer PII)
• Registration authority code and local registered ID for cross-registry joins
• Public GLEIF API — no API key, no login, no captcha

Features

• Keyless GLEIF JSON API (JSON:API)
• Defaults optimized for Apify Store auto-test (secret-free, non-empty dataset in seconds)
• Dedupes by LEI across names
• Optional registration-status filter (ISSUED, LAPSED, …)
• Pay-per-event ready (lei-result per dataset item when monetization is configured)
• Runs on Apify: scheduling, API, webhooks, integrations, monitoring

What data can GLEIF LEI KYB Lookup extract?

Field	Type	Description
lei	string	20-character Legal Entity Identifier
legalName	string	Entity legal name from GLEIF
entityStatus	string	Entity status (e.g. ACTIVE)
registrationStatus	string	Registration status (ISSUED, LAPSED, …)
nextRenewalDate	string	Next LEI renewal timestamp
jurisdiction	string	Entity jurisdiction (e.g. US-WA, BE)
entityCategory	string	e.g. GENERAL
registrationAuthority	string	GLEIF RA code
registeredAs	string	Local registry identifier
managingLou	string	Managing LOU LEI
directParentLei	string	Direct parent LEI when reported
ultimateParentLei	string	Ultimate parent LEI when reported
legalAddress / legalCity / legalRegion / legalCountry / legalPostalCode	string	Legal address fields
hqAddress / hqCity / hqRegion / hqCountry / hqPostalCode	string	Headquarters address fields
bic	string	Associated BIC code(s), if any
gleifUrl	string	Link to the record on GLEIF search
queryName / queryLei	string	Which input query produced the row

How to look up LEIs

1. Open the Actor in Apify Console or on the Store page.
2. Keep the default searchNames ["Microsoft"] for a quick test, or paste your company list.
3. Optionally add exact leis (20-character codes).
4. Set maxResults / maxResultsPerName (defaults are small and Store-safe).
5. Leave includeParents on to enrich direct/ultimate parent LEIs.
6. Click Start and download JSON, CSV, Excel, or HTML.

How much will it cost?

This Actor calls the free public GLEIF API. Platform cost is mainly Apify compute units. Small name lists finish in seconds on 256–1024 MB. If the publisher enables pay-per-event pricing, the primary event is lei-result (one charge per dataset item) — check the Store pricing tab.

Input

See the Input tab for the full form. Main fields:

• searchNames — list of legal names (default ["Microsoft"])
• leis — optional list of exact LEI codes
• maxResults — total cap (default 10, max 500)
• maxResultsPerName — per-name cap (default 5)
• includeParents — include parent LEIs (default true)
• registrationStatus — optional filter (e.g. ISSUED)

Output

Example item (shape may vary by entity):

{
  "lei": "INR2EJN1ERAN0W5ZP974",
  "legalName": "MICROSOFT CORPORATION",
  "entityStatus": "ACTIVE",
  "registrationStatus": "ISSUED",
  "nextRenewalDate": "2027-05-04T00:00:00Z",
  "jurisdiction": "US-WA",
  "entityCategory": "GENERAL",
  "registrationAuthority": "RA000641",
  "registeredAs": "600 413 485",
  "managingLou": "213800WAVVOPS85N2205",
  "directParentLei": null,
  "ultimateParentLei": null,
  "legalCountry": "US",
  "hqCity": "REDMOND",
  "hqCountry": "US",
  "gleifUrl": "https://search.gleif.org/#/record/INR2EJN1ERAN0W5ZP974",
  "queryName": "Microsoft"
}

Tips

• Prefer the official legal name when possible; GLEIF matching is substring-based and common brands can return many local entities.
• Use leis for exact KYB refresh of known counterparties.
• Filter to ISSUED when you only want currently renewed registrations.
• Combine with company-register Actors (e.g. UK Companies House) using registeredAs / jurisdiction.

FAQ & disclaimer

Is an API key required?

No. The GLEIF LEI API is public and keyless for these lookups.

Does this export personal data / officers?

No. Output is organization LEI Level 1 reference data and parent LEI links. Personal officer names are not requested.

Source & accuracy

Data comes from GLEIF golden copy / LOU submissions. Always verify critical compliance decisions against primary sources and your policy.

Our Actors are ethical and do not extract private user data beyond what GLEIF publishes for legal entities. You should not process personal data unless you have a legitimate reason. If unsure, consult your counsel. GDPR and other privacy laws may apply depending on your use case.

Support

Open an issue on the Actor page in Apify Console or contact the publisher.