- Fetch the full LEI record for any 20-character code: legal name, addresses, registration authority, status and parent relationships
- Search LEI records by LEI, legal name, country or registration-authority id with paging
- Fuzzy name completions for type-ahead entity pickers
- Open data (CC0): no licensing limits on storing or redistributing the records
- Served and logged through Apivom Atlas with per-tenant keys and a global response cache
GLEIF LEI Lookup API
Legal Entity Identifier records from the Global LEI Foundation as a REST API: search by LEI, legal name or country, fetch a full LEI record, or autocomplete names — the global, free-to-reuse key for entity identification.
What you can do
Use cases
- Regulatory reporting and KYC — Validate the LEI a counterparty gave you and pull its current legal name, address and registration status before a trade report or onboarding file is submitted.
- Cross-border entity matching — Resolve a company known only by its national register id (filter[entity.registeredAs]) to a global LEI, then link it across your CRM, ERP and risk systems.
- Group-structure mapping — Read direct and ultimate parent relationships from the LEI record to build or verify corporate hierarchies for credit and sanctions screening.
- Entity pickers in forms — Power a type-ahead field with fuzzy completions so users select a verified legal entity instead of typing a free-text name.
The Legal Entity Identifier is the ISO 17442 code that banks, regulators and reporting regimes (MiFID II, EMIR, SFTR) use to identify legal entities worldwide. Apivom Atlas exposes the GLEIF LEI API as a priced gateway service: fetch a record by LEI, filter the registry by legal name, country or the id the entity carries in its national register, or run a fuzzy completion for autocomplete fields. Responses come straight from GLEIF, are cached server-side so repeat lookups cost nothing, and every call is logged with its full payload in your Atlas portal — one key, one invoice, alongside the other national-registry APIs.
Code sample
Replace YOUR_KEY with the API key issued in Apivom Atlas and run it from your backend.
curl -X POST https://atlas.apivom.com/one/api/ext/gleif-lei/v1/query/lei-record-show \
-H "x-api-key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"params":{"lei":"5493001KJTIIGC8Y1R12"}}'Per-tenant API key (x-api-key header) issued in Apivom Atlas. No upstream account or credential is needed — the public source is called server-side; prepaid balance, per-query pricing.
Frequently asked questions
Does every company have an LEI?
No. LEIs are mandatory mainly for entities active in regulated financial markets, so coverage is strong for banks, funds, issuers and larger corporates and partial for small businesses. Combine it with a national register API (KRS, ARES, Brønnøysund, Mersis…) for full coverage.
How current is the data?
GLEIF consolidates the Local Operating Units daily; the record carries its own registration and next-renewal dates. Apivom Atlas caches successful responses — add ?force=true when you need a guaranteed fresh read.
How is the API billed?
Prepaid and per query: you top up a balance in Apivom Atlas and each successful query debits the route price shown there. Identical repeat queries are served from the server-side cache free of charge ("cached": true in the response); add ?force=true to refresh at the route price. HTTP 402 means the balance needs a top-up.
How do I authenticate and where do I see my usage?
Every request carries your tenant API key in the x-api-key header; keys are issued and rotated in Apivom Atlas. The portal logs every query with the full request and response payload, so finance and engineering share one audit trail.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.