GLEIF LEI Scraper

GLEIF LEI Scraper

Scrape the Global LEI Index for any legal entity by name or LEI code, up to a million records per run. Every record returns the entity's full LEI record, registered address, parent relationships, and registration status. No API key required. Export to CSV, JSON, Excel, or XML.

The Global LEI Index is the only open, standardized registry of legal entities worldwide, but its web search and API can be slow for bulk lookups. This Actor reads the public GLEIF search and LEI record endpoints directly, letting you pull entity data by company name, LEI code, country, or registration status. It returns each match in one flat, predictable schema so you can build KYC pipelines, compliance checks, or master data sets without writing a connector.

Who uses it	What they scrape GLEIF for
Compliance officers	Verify a counterparty's LEI and registration status before onboarding.
Data analysts	Build a master company database with standardized legal entity identifiers.
Risk managers	Pull parent-subsidiary relationships to map ultimate beneficial ownership structures.
Financial institutions	Batch-validate LEI codes against the GLEIF registry for regulatory reporting.

What it does

This Actor collects legal entity records from the GLEIF LEI index by name search or direct LEI code lookup and returns each entity as a flat row.

• 🔎 Name search: enter a company name like 'Apple' and get every matching legal entity worldwide.
• 🆔 LEI lookup: paste a 20-character LEI code to pull the full record for one specific entity.
• 🌍 Jurisdiction filter: restrict results to a single country with a 2-letter ISO code.
• 📋 Status filter: return only active, lapsed, retired, merged, duplicate, or annulled LEIs.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with GLEIF data

🏦 Automate client onboarding checks.

A compliance team runs the Actor with a list of company names, filters for ISSUED status, and exports the LEI records to their KYC system before opening accounts.

📊 Build a jurisdiction-specific entity watchlist.

A risk analyst scrapes all active entities in a high-risk country, then cross-references the parent relationships against internal sanctions lists.

🔗 Map corporate ownership trees.

A data engineer pulls LEI records for a portfolio of companies, extracts the direct and ultimate parent LEIs, and builds a graph of control relationships.

📋 Validate LEI codes in bulk for regulatory filings.

A financial institution runs a batch of LEI codes through the Actor before submitting a derivatives trade report, flagging any lapsed or retired identifiers.

Why choose this scraper

	What you get
No API key	Reads the public GLEIF search and record endpoints with no registration.
Flat schema	Every entity returns the same fields: name, LEI, address, status, and parent data.
Bulk ready	Collect up to 1,000,000 entities in a single run.
Standard export	Save results as CSV, JSON, Excel, or XML for any downstream system.

How it compares

This Actor focuses on raw GLEIF data extraction at scale, while the GLEIF LEI Lookup competitor adds a risk-decision layer on top of the same source.

Feature	ParseForge	GLEIF LEI Lookup
Bulk name search	Yes, up to 1M entities per run	Not listed
Direct LEI code lookup	Yes	Yes
Country and status filters	Yes, ISO-2 country and 6 registration statuses	Not listed
Parent relationship data	Yes, direct and ultimate parent LEIs	Not listed
Risk scoring and onboarding verdicts	Not listed	Yes
No API key required	Yes	Not listed

Configure the run

Drive the Actor from a company name or a 20-character LEI code, and narrow results by country and registration status so only matching entities land in your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "maxItems": 10,
  "query": "Apple"
}

A larger pull:

{
  "maxItems": 200,
  "query": "Apple"
}

Pricing

Pay-per-result: $0.02667 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$2.67
1,000 results	$26.67
10,000 results	$266.70

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the GLEIF LEI Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to GLEIF through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/gleif-lei-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results for my company name search?

GLEIF search is exact on the legal entity name. Try a shorter or partial name, check for special characters, or use the LEI code field if you have the 20-character identifier.

Why does my LEI code lookup return an error?

An LEI must be exactly 20 characters. Verify the code on the GLEIF website, check for leading or trailing spaces, and confirm the LEI has not been retired or annulled.

The Actor stopped before reaching my maxItems limit.

GLEIF returns results in pages. If the total matching records are fewer than your maxItems setting, the Actor finishes early. Try broadening your search or removing country and status filters.

I am getting duplicate entities in my dataset.

GLEIF may return the same entity across multiple search pages. Use the Apify platform deduplication feature or filter by LEI code in your downstream processing.

FAQ

Question	Answer
What is an LEI?	A Legal Entity Identifier is a 20-character alphanumeric code that uniquely identifies a legal entity participating in financial transactions. It is issued by GLEIF-accredited Local Operating Units and is required for many regulatory filings worldwide.
Do I need an API key to scrape GLEIF?	No. This Actor reads the public GLEIF search and LEI record endpoints. No registration, no API key, and no authentication are required.
Can I look up a single LEI code?	Yes. Paste a 20-character LEI code into the LEI code field and the Actor will return the full record for that specific entity, including its parent relationships and registration details.
How do I filter by country?	Enter a 2-letter ISO country code like 'US', 'GB', or 'DE' in the country field. The Actor will return only entities registered in that jurisdiction.
What registration statuses can I filter on?	You can filter by ISSUED (active), LAPSED, RETIRED, MERGED, DUPLICATE, or ANNULLED. Leave the field on 'All' to get every status.
How many entities can I collect in one run?	You can set the maximum up to 1,000,000 entities per run. The Actor stops when it reaches your limit or when GLEIF has no more matching records.
Does this Actor return parent company information?	Yes. Each record includes direct and ultimate parent LEI data when GLEIF publishes it, so you can trace ownership and control relationships.
What export formats are supported?	You can export your dataset as CSV, JSON, Excel, or XML from the Apify platform. The schema is the same regardless of format.
Is the data real-time?	The Actor reads the live GLEIF index on each run. The data reflects the current state of the registry at the moment of scraping.
Can I search by company name instead of LEI code?	Yes. Enter a company name in the query field and the Actor will search the GLEIF index and return every matching legal entity, up to your maximum limit.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Global Legal Entity Identifier Foundation. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.