GLEIF LEI (Legal Entity Identifier) Extractor

Pricing

Rating

Developer

Actor stats

Categories

Share

Extract Legal Entity Identifier records from GLEIF — one legal entity per row, with legal name, registered address, registration details, and BIC/MIC codes. The global reference set for KYC/AML, counterparty/entity resolution, and supply-chain due diligence.

Built for compliance and onboarding teams, fintech/regtech, data vendors, and analysts who need a clean company master.

Why use this actor

• 3.3M+ entities (verified) — pull the whole registry, or a slice by country and status.
• One entity per row, with a flat header (lei, legal_name, country, city, entity_status, registration_status) plus the full raw GLEIF attributes preserved.
• No login, no key. Clean JSON:API.

Input

entityStatus and registrationStatus are pick-lists; country is a free ISO-2 code (documented) since the full country set is large.

Output — LEI_RECORD

Envelope + recordType: "LEI_RECORD" + flat header, then the raw GLEIF attributes object:

{
"_input":"country=US; entity=ACTIVE",
"_source":"S1-gleif",
"_scrapedAt":"2026-06-03T10:00:00Z",
"recordType":"LEI_RECORD",
"lei":"5493001KJTIIGC8Y1R12",
"legal_name":"BLOOMBERG L.P.",
"country":"US","city":"New York",
"entity_status":"ACTIVE",
"registration_status":"ISSUED",
"entity":{"...":"..."},
"registration":{"...":"..."},
"bic":null,"mic":null
}

How it works

1. Your country and status filters are applied to the search.
2. The actor automatically pages through all matching results (up to 200 per request).
3. Each entity streams into the dataset.

Known limits

• Public data — no account needed, runs from any connection. Backs off on HTTP 429.
• Page size capped at 200 by GLEIF → large unfiltered pulls are many requests; filter by country/status to scope.
• Verified live 2026-06-03: total 3,331,178; JSON:API data[].attributes with lei, entity, registration, bic, mic.