GLEIF LEI Scraper — Legal Entity Identifiers

Look up Legal Entity Identifier (LEI) records straight from the official GLEIF registry. Every LEI comes back mapped to its legal entity's name, address, legal form and registration status — filterable by legal name, country, entity status or an exact LEI code. No login, no API key, nothing for you to supply.

What it does

This actor queries the official, keyless GLEIF JSON:API (api.gleif.org/api/v1/lei-records — the Global Legal Entity Identifier Foundation's own registry) and returns one flat, structured record per matching entity. Because the source is the authoritative registry itself (not a scraped third-party mirror), the data is as accurate and current as GLEIF's own records. Typical use: KYC (know-your-customer) checks, counterparty due diligence, supplier/vendor verification, or bulk-enriching a company list with its LEI and registration status.

Input

• Legal name — entity legal name to search for (e.g. Apple, Deutsche Bank).
• Country (ISO-2) — filter by legal-address country, ISO-3166 alpha-2 (e.g. US, DE).
• Entity status — filter by ACTIVE or INACTIVE; empty returns all statuses.
• Exact LEI — look up a single, specific 20-character LEI code directly.
• Max results — cap on how many entities to return (default 100, up to 50,000).
• Proxy configuration — Apify Proxy, RESIDENTIAL group prefilled; the run is billed to your own Apify account, nothing extra to configure.

All filters are optional and combinable — e.g. legal name + country narrows a common name down to entities in one jurisdiction.

Fields returned

Each dataset record includes: lei (the 20-character identifier), legal_name, entity_status (ACTIVE/INACTIVE), legal_form_id (ELF legal-form code), jurisdiction, category, registered_as (local business-registry identifier), legal address (legal_city, legal_region, legal_country, legal_postal_code), headquarters address (hq_city, hq_country), registration_status (ISSUED/LAPSED/etc.), initial_registration_date, last_update_date, next_renewal_date, managing_lou (the Local Operating Unit that issued the LEI), bic (associated SWIFT/BIC code(s), when GLEIF has them on file), and record_url (a direct link to the record on search.gleif.org).

Pricing

Pay-per-result — billed one entity event per returned record. See the Store pricing tab on this actor's page for the current per-result rate.

Notes

GLEIF is the international body behind the LEI standard (ISO 17442), used worldwide for financial-counterparty identification and regulatory reporting. Because this actor reads GLEIF's own free, official API rather than screen-scraping a paywalled or rate-limited source, there's no anti-bot friction and no third-party licensing question — it's a direct, zero-COGS pull from the authoritative registry, well suited to scheduled KYC/compliance enrichment runs.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.