LEI API

The LEI API here searches GLEIF, the public global register of Legal Entity Identifiers, and returns one typed row per entity — the 20-character LEI, the legal name, the entity and registration statuses, the legal and headquarters country and city, the legal form code and the initial-registration and last-update dates, plus the GLEIF record URL.

The LEI is the closest thing finance has to a universal company id — a single, stable key that ties an entity together across regulatory and market datasets — which is exactly why it is worth resolving cleanly. GLEIF is keyless and public; you can search a legal name or look up an exact LEI. As with the rest of the catalogue, you send your QuantumProxies key and get flat rows, with rotation handling volume.

$0.0004 per delivered entity, up to 100 entitys per run. Nothing delivered means nothing charged.

How the LEI API works

You pass a query — a legal name to search, or an exact 20-character LEI to look up — and each matching entity comes back as one flat row.

Inputs

query is required — either a legal name (fuzzy search) or an exact LEI (direct lookup). max_results caps delivery at 100 entities; a name that matches several companies returns several rows, and you pay only for the entities returned.

What one entity looks like

One row per entity. lei is the identifier and the join key; legal_name is the registered name; status and registration_status separate the entity's state from the LEI's lifecycle; legal_country/legal_city and hq_country give location; legal_form is the form code; and the date fields track registration history. url links the GLEIF record.

What the LEI API costs

$0.0004 per delivered entity ($0.40 per 1,000). Nothing delivered means nothing charged, and the $2 monthly free credit covers roughly 5,000 entitys here. Volume tiers take up to 30% off.

$0.0004 per delivered entity — $0.40 per 1,000 — no subscription. The $2/month free allowance is about 5,000 entities with no card.

Per-delivered-row billing suits both patterns: a precise LEI lookup bills one row, while a broad name search bills only the matches it returns. Pair it with the SEC EDGAR API to move from a legal name to its LEI and on to its filings.

LEI API vs the GLEIF API directly

GLEIF publishes its own free, keyless API and a bulk data download, so for occasional lookups you do not need us — go to the source. That is the honest baseline for any open register.

The collector's contribution is operational: rotation so a large batch of name resolutions does not throttle on one IP, a flat one-row-per-entity schema in place of GLEIF's nested JSON:API envelope, and the same key and table shape as your other collectors. When resolving thousands of counterparties to LEIs is a recurring job, that consistency is what you are paying for.

Versus querying GLEIF yourself

GLEIF's API is callable directly, but its JSON:API responses are nested and its fuzzy name search needs handling to turn many partial matches into usable rows. Rolling your own is a paginator, a flattener and a rate-limit handler — modest, and yours to maintain.

If you would rather keep that client, run it over our residential proxies so a bulk resolution job gets stable exits.

What people build with it

Counterparty and KYC enrichment

Resolve a list of legal names to LEIs and attach status, legal_country and legal_form — the backbone of a lightweight know-your-counterparty record.

Cross-dataset entity joins

Use the lei as a stable key to reconcile a company across filings, ownership and market datasets that each spell the name differently.

LEI lifecycle monitoring

Track registration_status on your counterparties to catch LAPSED LEIs, which often signal a company that has stopped maintaining its registration.

Limits, matching and the legal bit

One run delivers up to 100 entities. Name search is fuzzy, so a common name returns several candidates — use legal_country and status to disambiguate, or look up the exact LEI when you already have it. Runs parallelise up to your plan's rate limit (60–1,200 requests/minute by tier).

GLEIF data is open and free to use under its terms; accuracy depends on entities keeping their own registrations current. This is not legal advice.

FAQ

Is the LEI API free?

GLEIF's register is free and keyless, so query it directly for occasional lookups. This collector adds rotation, a flat schema and one key across sources, plus a $2/month free allowance — about 5,000 entities — with no card.

Can I look up an entity by its exact LEI?

Yes. Put the 20-character LEI in the query and it resolves that entity directly. A legal name in the same field runs a fuzzy search and can return several candidate rows.

What is an LEI and why does it matter?

The Legal Entity Identifier is a 20-character global id for a legal entity. It is a stable join key that ties one company together across financial and regulatory datasets that otherwise disagree on its name.

Why is a company's LEI marked LAPSED?

registration_status tracks the LEI's lifecycle separately from the entity's own status. LAPSED means the registration was not renewed — the company may still be active, but its LEI record is no longer being maintained.

Related scrapers