LEI Lookup: legal entity data from GLEIF

Look up Legal Entity Identifiers by code or by company name and get each entity back as one clean row: legal name, legal and headquarters addresses, jurisdiction, legal form, entity status, registration status and renewal date, the registry it's filed with, and any BIC codes linked to it. The data comes from the Global Legal Entity Identifier Foundation's free public API [1], so it matches what GLEIF publishes, and there's no key to set up.

Turn on parents and each row also names the entity's direct and ultimate parent where GLEIF holds them.

What you get for each record

• lei, legalName, otherNames (former and trading names GLEIF lists) and transliteratedNames
• legalAddress and headquartersAddress, each with street lines, city, region, country and postal code, and country
• jurisdiction, legalFormId (the legal form code GLEIF lists) and legalFormOther
• category, subCategory, entityStatus (such as ACTIVE), entityCreationDate, and expirationDate, expirationReason, successorLei and successorName for entities that have ended
• registrationStatus (such as ISSUED or LAPSED), initialRegistrationDate, lastUpdateDate, nextRenewalDate, managingLou and corroborationLevel
• registeredAt and registeredAs: the business registry and the entity's number in it
• bic, mic and ocid codes where GLEIF links them
• directParent and ultimateParent, each with LEI, legal name and country, when you turn parents on
• gleifUrl, a link to the record on GLEIF's search site

In testing, Apple Inc.'s LEI returned its Glendale legal address, Cupertino headquarters, former name Apple Computer, Inc. and BIC code. A search for "Google LLC" with parents on returned Google subsidiaries with GOOGLE LLC as the direct parent and ALPHABET INC. as the ultimate parent.

Personal data

The actor returns entity data only. Records in GLEIF's sole proprietor category can carry a person's name, so they're left out: a code that points to one gets an error row, and name searches skip them. Address lines that start with "c/o", "care of", "attn" or "attention" can name a person and are dropped from both addresses.

Input

• LEI codes. Each is checked against the ISO 17442 check digits before any request, and up to 100 go to GLEIF in one request.
• Entity names. By default a name is matched against GLEIF's full text index, so "Siemens Aktiengesellschaft" also finds Siemens subsidiaries. Turn on "Search legal names only" to match legal names alone.
• Country of legal address, as a two letter code, and only active entities: both narrow name searches.
• Maximum results per name search, 20 by default.
• Include direct and ultimate parents, off by default.

Output

One row per record, with query and queryType showing which input found it. A code that fails the check digit test, a code GLEIF doesn't hold, and a name with no matches each get a row with ok false and the reason in error, and the run carries on. The OUTPUT record in the key value store gives records returned and inputs that failed.

Speed and fair use

GLEIF allows 60 requests per minute per user [2], so the actor sends one request at a time at least 1.1 seconds apart. A batch of up to 100 LEI codes is one request and a name search is one request per 200 results, Parents cost two more requests per record, so runs with parents are slower.

Pricing

Pay per event: one event per record returned. Rejected codes, codes with no record and empty searches aren't charged. Before each record the run checks the maximum charge you set and stops when it's reached, so every record row in the dataset is a paid one.

Data license

GLEIF provides LEI data under the CC0 license [3]. This actor isn't provided, supported or authorized by GLEIF, and every row carries that note in notice.

Support

Questions and problems: the Issues tab on this page. Replies are written by an AI assistant on behalf of the developer and reviewed by the developer.

References

[1] GLEIF, GLEIF API. https://www.gleif.org/en/lei-data/gleif-api [2] GLEIF API documentation, section "Terms & Conditions". https://api.gleif.org/docs [3] GLEIF, LEI Data Terms of Use, section II.3. https://www.gleif.org/en/meta/lei-data-terms-of-use