GLEIF LEI Search

Search the official GLEIF Legal Entity Identifier register by organization name, LEI or free text and export 72 flat columns per entity: legal and headquarters addresses, the company's number in its own national registry, legal form and registration authority resolved from codes into words, corporate events such as dissolution and bankruptcy, BIC/MIC/OpenCorporates/S&P cross-reference IDs, and optional parent and subsidiary ownership. No API key is required. Set max_items before each run to keep output and cost predictable.

What data can I extract?

• Official global GLEIF data, published under CC0
• Company-name, free-text and exact-LEI lookup modes
• Legal and headquarters addresses, plus alternative-language and transliterated names and addresses
• registered_as, the company's number in its OWN national registry - the join key to Companies House, SIRENE or the Handelsregister
• Codes resolved to words: legal_form_name ("Private Limited Company"), registered_at_name ("Companies House"), managing_lou_name, country and region names
• Corporate events: dissolution, bankruptcy, liquidation, M&A, name and address changes, with effective dates
• Cross-reference IDs for joining: BIC, MIC, OpenCorporates and S&P Global
• Data-quality columns: corroboration_level, conformity_flag, next_renewal_date
• Optional ownership: direct and ultimate parent, subsidiary count and names, ISINs

Every result is written to the default dataset and can be downloaded as JSON, CSV, Excel, or XML.

All 72 columns

Identity — alternative_language_names, direct_children_names, direct_parent_lei, direct_parent_name, gleif_profile_url, hq_country_name, hq_region_name, legal_country_name, legal_form_name, legal_name, legal_name_language, legal_region_name, lei, managing_lou_name, ocid, other_names, previous_legal_names, registered_at_name, successor_lei, successor_name, trading_names, transliterated_names, ultimate_parent_lei, ultimate_parent_name

Status — category, conformity_flag, event_types, has_direct_children, has_direct_parent, has_isins, has_ultimate_parent, latest_event_status, latest_event_type, registration_status, status, sub_category

Dates — creation_date, initial_registration_date, last_update_date, latest_event_effective_date, next_renewal_date

Location — direct_parent_country, hq_address, hq_city, hq_country, hq_postal_code, hq_region, legal_address, legal_city, legal_country, legal_postal_code, legal_region, other_addresses, ultimate_parent_country

Counts and measures — direct_children_count, event_count, isin_count

Other detail — bic, corroboration_level, direct_parent_exception_reason, hq_mail_routing, isins, jurisdiction, legal_form, legal_form_code, legal_mail_routing, managing_lou, mic, registered_as, registered_at, spglobal, ultimate_parent_exception_reason

Input example

{
  "query": "Tesco",
  "search_mode": "name",
  "country": "GB",
  "status": "ACTIVE",
  "include_relationships": false,
  "max_items": 10
}

Set include_relationships to true to add parent, subsidiary and ISIN columns. Those live on separate GLEIF endpoints, so it adds up to six requests per record and makes runs slower.

The default input is deliberately bounded and produces a small, useful Store test. max_items is a hard output ceiling.

Output example

{
  "lei": "213800JBW23QIB8OWZ72",
  "legal_name": "TESCO HOLDINGS LIMITED",
  "legal_name_language": "en",
  "other_names": "Custody Bank of Japan, Ltd./014152037/203702",
  "previous_legal_names": "QUERCUS INVESTMENT PARTNERS (2014) LIMITED",
  "trading_names": "リニアロジック, Linear logic",
  "alternative_language_names": "TABATA Co., Ltd.",
  "transliterated_names": "Linear Logic Ltd.",
  "status": "ACTIVE",
  "registration_status": "ISSUED",
  "jurisdiction": "GB",
  "category": "GENERAL",
  "sub_category": "LOCAL_GOVERNMENT",
  "legal_form": "H0PO",
  "legal_form_code": "H0PO",
  "registered_as": "00243011",
  "registered_at": "RA000585",
  "creation_date": "1929-10-16T00:00:00Z",
  "legal_address": "TESCO HOUSE, SHIRE PARK, KESTREL WAY",
  "legal_city": "WELWYN GARDEN CITY",
  "legal_region": "GB-HRT",
  "legal_country": "GB",
  "legal_postal_code": "AL7 1GA",
  "legal_mail_routing": "C/O Begbies Traynor(Central)Llp",
  "hq_address": "TESCO HOUSE, SHIRE PARK, KESTREL WAY",
  "hq_city": "WELWYN GARDEN CITY",
  "hq_region": "GB-HRT",
  "hq_country": "GB"
}

44 further columns are omitted here for length — the full list is above, and every column appears in the export whether or not the source populated it.

Common use cases

• Entity resolution and vendor onboarding
• KYC and counterparty research
• Corporate master-data enrichment
• LEI validation and compliance workflows

Use with AI agents and MCP

Apify's MCP server can discover and call this Actor from an AI workflow. Example intent:

Find 10 active UK legal entities matching Tesco and return their LEIs and legal addresses.

Use the JSON from Input example as the tool arguments. The strict input schema rejects unsupported parameters, and the documented dataset schema tells the agent how to interpret each returned field.

Pricing and cost control

Output is billed per result at $0.003 per result (about $3.00 per 1,000 results), plus a $0.0005 Actor-start charge billed once per gigabyte of memory at run start. Use max_items to cap both output volume and charges. The price shown on the Apify Store listing is authoritative.

max_items limits both output volume and result-based charges. Start with 10 records, inspect them, and then scale deliberately.

Reliability

The Actor validates input, bounds pagination, retries transient upstream failures, writes structured records, and fails explicitly when the source cannot produce usable output. A production default-input canary is monitored by the fleet.

Limitations and responsible use

• A name search can return similarly named entities and requires caller review.
• Coverage is limited to entities represented in the GLEIF register.
• Address completeness depends on the submitting registration authority.
• This tool supplies public reference data, not a KYC decision.

Use the data lawfully, respect source terms, and independently validate records before making consequential decisions.

FAQ

Does it need my own API key?

No, the default workflow does not require a customer-supplied API key.

Can I export the results?

Yes. Download the default dataset as JSON, CSV, Excel, or XML, or retrieve it through the Apify API.

How do I control cost?

Set max_items to the most records you want returned. Begin with the bounded default input.

Can an AI agent call it?

Yes. The Actor has strict input and semantic output schemas and can be called through Apify's MCP tooling.

What happens when a source field is missing?

The relevant field is returned as null or an empty normalized value rather than being merged into another field.