GLEIF LEI Records Scraper

Find and export Legal Entity Identifier (LEI) records from the public GLEIF dataset.

Use this actor to search companies by legal name, fetch exact LEI codes, filter by country or status, and export normalized compliance-ready records.

---

What does GLEIF LEI Records Scraper do?

GLEIF LEI Records Scraper helps you collect public Legal Entity Identifier reference data at scale.

It returns structured records for legal entities, including names, LEIs, registration status, jurisdiction, addresses, renewal dates, Local Operating Unit details, and available financial identifiers.

You can run one quick lookup or a bulk search job.

Typical jobs include:

• 🔎 Search legal entity names such as Apple, Microsoft, or supplier names
• 🧾 Fetch exact 20-character LEI codes
• 🌍 Filter entities by legal address country
• ✅ Filter by registration and entity status
• 📦 Export clean records to JSON, CSV, Excel, Google Sheets, or your own API pipeline

---

Who is it for?

This actor is useful for teams that need reliable public company-reference data.

• 🏦 KYC and AML teams validating counterparties
• 📊 B2B data vendors enriching company profiles
• 🧑‍💼 Sales operations teams cleaning lead and account lists
• 🛡️ Supplier-risk and procurement analysts checking legal entities
• 🧮 Finance teams mapping entities to LEI records
• 🧰 Developers building compliance or enrichment workflows

---

Why use this actor?

GLEIF data is public, but many users need it in an automation-friendly format.

This actor provides:

• Bulk input handling
• Pagination controls
• Consistent field names
• Deduplication by LEI
• Optional raw source record retention
• Apify dataset export formats
• API and integration support
• Pay-per-result pricing

---

What data can you extract?

Field	Description
lei	Legal Entity Identifier
legalName	Registered legal name
entityStatus	Active or inactive entity status
registrationStatus	LEI registration status
jurisdiction	Legal jurisdiction code
legalForm	Legal form identifier
legalAddress	Registered legal address object
headquartersAddress	Headquarters address object
initialRegistrationDate	First registration date
lastUpdateDate	Last update timestamp
nextRenewalDate	Next renewal date
managingLou	Managing Local Operating Unit
bic	BIC codes where available
isin	ISIN values where available
directParentLei	Direct parent LEI when available
ultimateParentLei	Ultimate parent LEI when available
sourceUrl	Source record URL
matchedInput	Input term or LEI that found the record
rawRecord	Optional full source record

---

Pricing

This Actor uses Apify pay-per-event pricing. The prices below come from the current Actor pricing configuration. Apify public plans map to Store discount tiers, so the table shows both the user-facing plan context and the pricing tier name. The final price shown in Apify depends on the user account plan and any custom agreement.

Event	What is charged	Price
start	One-time fee charged when a run starts. Covers fixed startup cost.	$0.005

Event	What is charged	Free / no discount	Starter / Bronze	Scale / Silver	Business / Gold	Custom / Platinum	Custom / Diamond
item	Charged per public GLEIF LEI record saved to the dataset.	$0.0575 / 1,000	$0.05 / 1,000	$0.039 / 1,000	$0.03 / 1,000	$0.02 / 1,000	$0.014 / 1,000

Apify may also charge platform usage for compute, storage, proxies, or data transfer outside this Actor pricing. Check the Actor run and the Apify Pricing tab for the exact cost shown to your account.

Quick start

1. Open the actor on Apify.
2. Enter one or more legal names in Legal names to search, use another filter, or leave the search fields empty for a bounded public-record browse.
3. Optionally add exact LEI codes.
4. Add filters such as country, registration status, or entity status.
5. Set Maximum records.
6. Click Start.
7. Download the dataset when the run finishes.

---

Input options

Legal names to search

Use searchTerms for company names or partial legal names.

Examples:

• Apple
• Microsoft
• Volkswagen
• Acme Holdings

Exact LEI codes

Use leiCodes when you already know the LEI.

The actor fetches these directly. An exact-LEI-only input returns only those requested records; it does not append unrelated browse results.

Browse without filters

If an API, task, or agent starts the Actor without search fields, the Actor returns up to maxItems public GLEIF records instead of failing. Add a name, LEI code, country, or status whenever you need a specific entity set.

Country filter

Use country with a two-letter country code.

Examples:

• US
• GB
• DE
• FR
• IN

Registration status

Use registrationStatus to focus on issued, lapsed, retired, or other record states.

Entity status

Use entityStatus to filter active or inactive legal entities.

Input settings

Setting	API key	What it does
Legal names to search	searchTerms	Searches one or more full or partial legal names.
Exact LEI codes	leiCodes	Fetches known 20-character LEI records directly.
Legal address country	country	Narrows name searches to a two-letter country code, such as US or DE.
Registration status	registrationStatus	Filters records by the GLEIF registration state.
Entity status	entityStatus	Filters records by legal-entity status.
Maximum records	maxItems	Caps the total number of unique LEI records saved by the run.
API page size	pageSize	Sets the number of records requested per page; use smaller values for a first check.
Include raw record	includeRawRecord	Includes the complete public GLEIF record alongside normalized fields.

All search fields are optional. With no search or filter fields, maxItems bounds a general public-record browse.

---

Ready-to-run examples

Use these maintained public example tasks as starting points:

• Exact LEI code lookup
• US company LEI lookup
• Bulk name search starter

---

Example input

{
  "searchTerms": ["Apple", "Microsoft"],
  "country": "US",
  "registrationStatus": "ISSUED",
  "entityStatus": "ACTIVE",
  "maxItems": 25,
  "pageSize": 50,
  "includeRawRecord": true
}

---

Example output

{
  "lei": "549300N1UWZ4871DND44",
  "legalName": "Apple Bank",
  "entityStatus": "ACTIVE",
  "registrationStatus": "ISSUED",
  "jurisdiction": "US-NY",
  "legalForm": "M0ER",
  "legalAddress": {
    "city": "New York",
    "country": "US",
    "fullAddress": "122 E 42nd St Fl 9, New York, US-NY, 10168, US"
  },
  "nextRenewalDate": "2026-10-11T19:37:39Z",
  "managingLou": "529900F6BNUR3RJ2WH29",
  "bic": ["APPAUS33XXX"],
  "isin": [],
  "sourceUrl": "https://api.gleif.org/api/v1/lei-records/549300N1UWZ4871DND44",
  "matchedInput": "Apple"
}

---

Tips for better results

• Use official legal names when possible.
• Combine broad names with a country filter to reduce noise.
• Use exact LEI codes for verification workflows.
• Keep includeRawRecord enabled when you need audit trails.
• Start with a low maxItems value, review output, then scale up.
• Large searches save records progressively. If a run reaches its time limit, it keeps a run checkpoint so the same run can safely continue without duplicating records already saved.

---

Common use cases

KYC checks

Validate whether a counterparty has an active issued LEI record.

Supplier onboarding

Enrich supplier records with jurisdiction, address, and renewal status.

CRM enrichment

Attach LEI identifiers to account records for finance and compliance workflows.

Data vendor pipelines

Create recurring exports of entities by country and registration status.

---

Integrations

Apify datasets can be connected to many downstream tools.

Useful workflows include:

• Send new LEI records to Google Sheets
• Export CSV files to S3 or Google Drive
• Trigger webhooks after a compliance enrichment run
• Call the actor from a CRM enrichment service
• Schedule recurring country/status exports

---

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });

const run = await client.actor('fetch_cat/gleif-lei-records-scraper').call({
  searchTerms: ['Apple'],
  country: 'US',
  registrationStatus: 'ISSUED',
  entityStatus: 'ACTIVE',
  maxItems: 25
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])

run = client.actor('fetch_cat/gleif-lei-records-scraper').call(run_input={
    'searchTerms': ['Apple'],
    'country': 'US',
    'registrationStatus': 'ISSUED',
    'entityStatus': 'ACTIVE',
    'maxItems': 25,
})

items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~gleif-lei-records-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"searchTerms":["Apple"],"country":"US","maxItems":25}'

---

MCP integration

Use this actor from MCP-compatible tools through Apify MCP.

MCP URL:

https://mcp.apify.com/?tools=fetch_cat/gleif-lei-records-scraper

Claude Code setup:

$claude mcp add apify-gleif-lei-records "https://mcp.apify.com/?tools=fetch_cat/gleif-lei-records-scraper"

Claude Desktop JSON configuration:

{
  "mcpServers": {
    "apify-gleif-lei-records": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/gleif-lei-records-scraper"
    }
  }
}

Example prompts:

• "Find active US LEI records for Apple and summarize renewal dates."
• "Look up this LEI and return the legal address."
• "Export active issued LEI records for Microsoft-related entities."

---

Scheduling

You can schedule recurring runs in Apify.

Examples:

• Daily checks for a watchlist of LEI codes
• Weekly supplier list enrichment
• Monthly country-level export refreshes

---

Data quality notes

The output reflects public GLEIF reference data at run time.

Some optional identifiers, parent relationships, or financial codes may be missing for some entities.

Always review registrationStatus, entityStatus, and nextRenewalDate for compliance decisions.

---

Limits

The actor is designed for public reference-data extraction.

Very large jobs should use sensible maxItems and pageSize settings.

If a search term is broad, the actor may return many legally distinct entities with similar names.

---

Legality

This actor collects publicly available LEI reference data.

You are responsible for using the data in accordance with applicable laws, internal compliance policies, and the terms of the source data provider.

Do not use the output as the only basis for a regulated decision without appropriate review.

---

FAQ

Why did I get multiple companies for one name?

Legal names are often shared across subsidiaries, jurisdictions, and similarly named entities. Add a country or status filter to narrow the results.

Why are some parent LEI fields empty?

Not every public record exposes parent relationship values in the same way. Keep rawRecord enabled if you need to inspect all relationship metadata.

Why did my run return zero items?

Check spelling, remove overly strict filters, or try an exact LEI code if you have one.

Can I export to CSV or Excel?

Yes. Open the run dataset and choose CSV, Excel, JSON, XML, or RSS export.

---

Related scrapers

Other actors from the same developer that may help with company and compliance workflows:

• SEC EDGAR Company Filings Scraper
• GitHub Profile Scraper
• GitHub Repository Search Scraper

---

Support

If a run fails or the output looks wrong, open an issue from the actor page. Include the Apify run ID or run URL, the input JSON, the expected output, the actual output, and one reproducible public URL, such as https://api.gleif.org/api/v1/lei-records/5493001KJTIIGC8Y1R12. If you need a field that is present in public GLEIF records but not normalized in the dataset, describe the field you need.

Privacy and data handling

This Actor runs with Apify limited permissions and only processes data needed for the documented run. It uses the inputs you provide and the public records needed to produce the documented dataset to produce the output dataset and sends requests to GLEIF public LEI records endpoints; results are stored in Apify run storage for your account. FetchCat does not use your inputs or outputs for advertising, does not use them for model training, and does not retain them outside the Apify run except for transient support debugging when you explicitly share run details. You are responsible for using the Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs.