GLEIF LEI Scraper — Legal Entity Identifier Records

---

🎯 What this scrapes

The LEI is the one identifier that ties a legal entity to its regulatory record worldwide, which makes GLEIF the reference file for KYC, AML and counterparty onboarding. Its API is JSON:API — every useful value sits two or three levels down under data[].attributes.entity, and the address arrives as an array of lines. This Actor flattens all of it into one row per entity so a counterparty list becomes a spreadsheet.

🔥 What we handle for you

flattens JSON:API's three-level nesting into one row per entity joins the registrar's address-line array into a readable field retries transient 429/5xx responses instead of failing the whole run

💡 Use cases

• Resolve counterparty names to LEI codes for KYC and AML onboarding.
• Screen a client list for lapsed LEI registrations before a reporting deadline.
• Map a corporate group's registered entities across jurisdictions.
• Enrich a CRM with authoritative legal names, forms and registered addresses.

⚙️ How to use it

1. Click Try for free at the top of the page.
2. Fill in the input form — most fields have sensible defaults.
3. Click Start. Output streams into the run's dataset.
4. Export from Storage → Dataset as JSON, CSV, or Excel — or fetch via the API.

📥 Input

Field	Type	Required	Default	Notes
legalName	string	no	'Equinor'	Match entities whose registered legal name contains this text.
country	string	no	'—'	Two-letter ISO country code of the legal address, e.g. NO. Leave empty for every country.
status	string	no	'ANY'	Filter by entity status.
maxResults	integer	no	100	Stop after this many entities. Each entity is one billed result row.
proxyConfiguration	object	no	{'useApifyProxy': False}	GLEIF is a public API and does not need a proxy. Leave this off unless your account requires egress through Apify Proxy.

Example input

{
  "legalName": "Equinor",
  "maxResults": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

📤 Output

Every row is one dataset item.

Field	Type	Notes
lei	string	20-character Legal Entity Identifier.
legal_name	string	Registered legal name.
status	string	Entity status: ACTIVE or INACTIVE.
legal_form	string	Legal form code, when published.
jurisdiction	string	Registration jurisdiction code.
category	string	Entity category, e.g. FUND, BRANCH.
address	string	Legal address lines, joined.
city	string	Legal address city.
region	string	Legal address region code.
country	string	Legal address country code.
postal_code	string	Legal address postal code.
registered_as	string	Local business-register identifier.
bic	array	Associated BIC/SWIFT codes.
initial_registration_date	string	First LEI registration date.
last_update_date	string	Last record update.
next_renewal_date	string	Date the LEI must be renewed.
registration_status	string	LEI registration status, e.g. ISSUED, LAPSED.
url	string	GLEIF search page for this LEI.

Example output

{}

💰 Pricing

Pay-Per-Event — you pay only when these events fire:

Event	USD	What it is
actor-start	$0.05	One-off warm-up charge per run
result	$0.002	Per dataset item

Example: 1 000 results at the rates above ≈ $2.05. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

🚧 Limitations

• Returns the LEI register record only — no ownership hierarchy or financial data.
• BIC codes are present only for entities that have registered them with GLEIF.

❓ FAQ

Do I need an API key?

No. GLEIF publishes the register openly and needs no credentials.

Can I look up one specific LEI?

Search by legal name and filter the result, or set the name to the exact entity — the API matches on the registered legal name.

Why are some addresses missing a street?

GLEIF stores address lines as an array that some registrars leave sparse. The Actor joins whatever lines exist and leaves the field empty rather than inventing one.

💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an issue on the Actor's Issues tab on Apify Console — we ship fixes weekly and we read every report.

---