GLEIF LEI records API: access card
Every endpoint on this page was live-probed on 2026-07-29 by the Aidenix Atlas catalog.
What is the global LEI register?
GLEIF LEI records API is the global register of Legal Entity Identifiers — the cross-border join key between company registries, published by Global Legal Entity Identifier Foundation. Coverage: Global; scale: every LEI ever issued worldwide. In our data — the Aidenix Atlas catalog, where every source is live-probed — this endpoint answered HTTP 200 on 2026-07-29. What the card gives you:
- The exact endpoint and a working request you can copy.
- Authentication and rate limits: none — no API key required.
- The query keys the source accepts and the fields it returns, verified against the live endpoint.
Key facts at a glance
A key-facts table is the 30-second version of this card: every LEI ever issued worldwide in scope, 3 query facets, 5 field groups out. Every row comes from our own probe run of 2026-07-29, not from vendor marketing:
| Question | Answer |
|---|---|
| Provider | Global Legal Entity Identifier Foundation |
| Coverage | Global |
| Records | every LEI ever issued worldwide |
| Authentication | none — no API key required, according to GLEIF API documentation |
| Query by | legal name, LEI code, registration filters |
| Returns | LEI, legal name, legal address, registration status, parent relationships |
| Last probe | 2026-07-29 — HTTP 200 |
| Cost | $0 — open data, no license fee |
How do you query it?
A working query is one plain HTTP request — in our data this exact request form was verified on 2026-07-29:
curl "https://api.gleif.org/api/v1/lei-records?filter%5Bentity.legalName%5D=Apple&page%5Bsize%5D=5"
Notes from the catalog recipe:
- Auth: none — no API key required, according to GLEIF API documentation.
- The response is plain JSON — no SDK and no signup required.
- Substitute the placeholder in the endpoint with your own value.
When should you use this source?
A source fit is a match between what you already know and what the endpoint accepts — 3 query facets here, according to our probe of 2026-07-29. In our data, the decision goes like this:
- If the company is registered in Global → this is the authoritative record, filed with Global Legal Entity Identifier Foundation.
- If you can search by legal name → this source resolves it directly; other facets need a different registry.
- If you need fields it does not return (LEI, legal name, legal address, registration status, parent relationships is the full list) → follow the related sources below rather than forcing this one.
What does it accept and return?
The interface contract is a short one: 3 query facets in, 5 field groups out. Every row below was checked against the live endpoint on 2026-07-29:
| Facet | Value |
|---|---|
| Endpoint | https://api.gleif.org/api/v1/lei-records?filter[entity.legalName]={name} |
| Auth | none — no API key required, according to GLEIF API documentation |
| Query by | legal name, LEI code, registration filters |
| Returns | LEI, legal name, legal address, registration status, parent relationships |
| Provider | Global Legal Entity Identifier Foundation |
| Coverage | Global |
| Last probe | 2026-07-29 — HTTP 200 |
Related sources
A related source is a dataset that joins to the global LEI register through a shared key — 2 of them in our catalog of nearly 4,000 sources, each probed on the same schedule as this card, according to our run of 2026-07-29:
- UK Companies House API — United Kingdom.
- SEC EDGAR submissions API — United States (federal).
The workflow this source belongs to is covered in the full guide: Free Clearbit alternative — company enrichment from open data.
Frequently asked questions
Three questions cover most of what people ask about this source. Answers below reflect our probe of 2026-07-29:
Is the global LEI register free to use? Yes — $0 license fee, every LEI ever issued worldwide in scope, authentication: none — no API key required. The cost of using it is engineering time and rate-limit patience, not money.
How current is the data? The records are as current as Global Legal Entity Identifier Foundation makes them — registries update on filing schedules, not news cycles. What we verify is the endpoint: it answered on 2026-07-29, and this card carries that date so you can tell a fresh claim from a stale one.
Can I use this commercially? Public records generally allow commercial use, but terms are set per publisher, not universally. Query-and-enrich workloads are uncontroversial; verify Global Legal Entity Identifier Foundation's specific terms before redistributing bulk copies.
How we verify this card
Our verification method is a live probe, not a citation chain — the status on this card comes from a real request we sent on 2026-07-29. What the probe run covers, in our data:
- Endpoint liveness: this source is one of the nearly 4,000 the Aidenix Atlas catalog tracks, re-probed on schedule.
- Contract checks: the accepted query facets and returned field groups above are read from the live response, not from documentation.
- Honest failures: when a source stops answering, this card says so and its date freezes — we do not publish a fresh-looking date over a dead endpoint.
- Freshness contract: the «last probe» date above is the promise; it moves only when the source actually answers.
Source card generated from the Aidenix Atlas catalog; facts as probed on 2026-07-29.
Find these guides useful? Add Aidenix as a preferred source on Google — our pages will surface in your AI Overviews.