GLEIF LEI Scraper: 15 Data Fields, Up to 1,000 Free Results/Month

You can find legal entity data for 2M+ entities across 200+ countries from the Global LEI Foundation (GLEIF) database. This Actor returns 15 output fields per record, including the LEI, entity name, type, jurisdiction, address, and registration dates. It is free to use without authentication and provides structured output. On Apify's free plan, you can get up to 1,000 results a month. This Actor is for data analysts or financial professionals needing to verify company identities or enrich existing datasets with official LEI information. It is not for anyone who needs real-time transaction data or private company filings, as the Actor provides only public registration details.

Try it: open GLEIF LEI Scraper on Apify, sign in on the free plan and run the prefilled example.

Can you try GLEIF LEI Scraper before paying?

Yes. Apify's free plan includes $5.00 of prepaid usage every month and asks for no credit card. At $0.005 per result, that covers up to 1,000 results of GLEIF LEI Scraper a month, before run-start charges and platform usage.

The example request further down caps maxItems at 50, so a first run returns at most 50 results and costs at most $0.25 in result charges. That is enough to see the real shape of the data before deciding anything.

GLEIF LEI Scraper was last updated on 2026-06-06. It is one of 1,729 Actors CrawlerBros publishes on Apify, which together have 746,619 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

What does it cost to run GLEIF LEI Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

The largest factor affecting your bill is the number of results returned, which is controlled by the "maxItems" input. Each run incurs a run-start fee, but result charges only apply to items written to the dataset. To cheaply determine if this Actor meets your needs, begin with a small "maxItems" value, such as the default of 50 in the example input, which costs at most $0.25 in result charges.

How do you run GLEIF LEI Scraper from the API?

The schema marks 1 of its 6 controls as required: mode. Every value in the payload below comes from the published schema's own prefills, which means you can paste it, swap the token, and get a real result.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~gleif-lei-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","query":"apple","filterStatus":"","maxItems":50}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search",
  "query": "apple",
  "filterStatus": "",
  "maxItems": 50
}

run = client.actor("crawlerbros~gleif-lei-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "search",
  "query": "apple",
  "filterStatus": "",
  "maxItems": 50
}

const run = await client.actor('crawlerbros~gleif-lei-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

That endpoint blocks until the run completes. Fine while you are testing a handful of records, risky once a run takes minutes: a dropped connection loses the response even though the run itself finished. Switch to an asynchronous start with polling or a webhook before you schedule anything.

Which GLEIF LEI Scraper inputs matter, and which can you skip?

The mode control is the only required input and determines whether you are searching by query or retrieving entities by leiCodes. For most initial runs, you'll use mode set to search with a query for a company name or keyword. The filterStatus and filterCountry controls are useful for narrowing results, but you can leave them at their defaults for a first pass.

• mode (string): What to fetch from GLEIF. Default: "search".
• query (string): Company name or keyword to search (mode=search). E.g. 'apple', 'deutsche bank', 'Goldman Sachs'.
• leiCodes (array): List of 20-character LEI codes to fetch (mode=getByLEI). E.g. ['HWUPKR0MPOU8FGXBT394'].
• filterStatus (string): Only return entities with this registration status (leave blank for all). Default: "".
• filterCountry (string): Only return entities registered in this country. Use 2-letter ISO code, e.g. 'US', 'DE', 'GB', 'JP'.
• maxItems (integer): Maximum number of entity records to return. Default: 50.

Fixed-choice controls: mode accepts search (Search entities (by name / keyword)), getByLEI (Get by LEI code (specific entities)); filterStatus accepts 9 values (default ""), including "" (All statuses), ISSUED (active/current), LAPSED (expired renewal), RETIRED.

What does GLEIF LEI Scraper return?

The returned records contain essential details for legal entity identification and verification, such as the 20-character LEI, official entity name, jurisdiction, and registration status. They conspicuously do not include financial statements, corporate hierarchy beyond direct parent/child relationships, or contact information like email addresses or phone numbers. This output is best for compliance checks and data enrichment.

• lei: 20-character Legal Entity Identifier
• entityName: Official legal name of the entity
• entityType: Entity category (GENERAL, FUND, SOLE_PROPRIETOR, etc.)
• jurisdiction: Jurisdiction code (e.g. US-CA, GB, DE)
• country: 2-letter ISO country code
• city: City of legal address
• postalCode: Postal code of legal address
• addressLine1: First line of legal address
• status: Registration status (ISSUED, LAPSED, RETIRED, etc.)
• initialRegistrationDate: Date entity was first registered (YYYY-MM-DD)
• lastUpdated: Date record was last updated (YYYY-MM-DD)
• managingLOUName: Name of the LEI issuing organization
• sourceUrl: GLEIF search record URL
• recordType: Always entity
• scrapedAt: ISO 8601 timestamp

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open GLEIF LEI Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Set "mode" to "search" and provide a "query" with a company name, then run it.
2. Examine the "entityName" and "country" fields of the results to confirm they match your expectations.
3. If the search is too broad, add a "filterCountry" using an ISO 2-letter code to narrow the results.
4. For a more precise search, use "mode" set to "getByLEI" and provide a list of known "leiCodes".
5. Review the "status" field to understand the registration state of the entities, especially distinguishing between "ISSUED" and "LAPSED".
6. Adjust "maxItems" as needed, keeping in mind the 1,000-item limit per run to control output volume.

How do you apply it? Three worked playbooks

These are GLEIF LEI Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: KYC / AML compliance

Outcome: Verify legal entity identity and registration status

Configure: Set "mode" to "getByLEI" and populate "leiCodes" with the specific LEIs you need to verify. Optionally, set "filterStatus" to "ISSUED" to focus on active entities.

Working method: Begin by supplying a single known LEI code and inspecting the returned record's "entityName", "status", and "jurisdiction" to confirm its accuracy. Once confident, expand "leiCodes" to a larger list. Compare the returned details against internal records to verify identity and registration status for compliance purposes.

Deliverable: A spreadsheet or database table of verified legal entity identities, including their official names, LEI codes, and current registration statuses.

Stop condition: Any LEI code that returns an empty record or a status that does not match the expected active registration for compliance.

Use case 2: Business intelligence

Outcome: Research companies by jurisdiction, country, or name

Configure: Set "mode" to "search", provide a "query" for the company name or keyword, and specify "filterCountry" with a 2-letter ISO code to narrow your research.

Working method: Start with a broad "query" like "bank" and a "filterCountry" like "DE" to understand the types of entities listed. Analyze the "entityType" and "jurisdiction" fields. Refine your "query" and country filters incrementally to pinpoint specific companies or industry segments within a region, observing how the search results change.

Deliverable: A dataset containing legal entities matching your search criteria, enriched with their country, jurisdiction, and entity type, suitable for market analysis.

Stop condition: Search results that consistently include irrelevant entity types or jurisdictions, indicating the query or filters are too broad.

Use case 3: Financial data enrichment

Outcome: Link counterparties to their official LEI records

Configure: Set "mode" to "search" and provide a "query" using the counterparty's known name.

Working method: For a specific counterparty, begin with their precise name in the "query" field. Evaluate the "entityName" and "country" in the results to find the correct LEI record. If the search yields multiple potential matches, use additional information like known address details to cross-reference and confirm the correct LEI.

Deliverable: A reconciled list of counterparties, each linked to their unique 20-character LEI code, official entity name, and registration status from the GLEIF database.

Stop condition: A counterparty name returning no matching LEI records, or multiple ambiguous matches where a definitive link cannot be established after cross-referencing.

What breaks, and how do you design around it?

When you encounter the maximum item limit, split your queries into smaller batches or apply more specific filters to reduce the result set per run. If you need to retrieve more than 1,000 items, consider running the Actor multiple times with different queries or LEI code lists. For very large datasets, schedule multiple runs or use distinct filters to ensure complete coverage.

When should you not use GLEIF LEI Scraper?

This Actor is not suitable if you need proprietary company data, such as internal financials, detailed corporate structures beyond direct LEI relationships, or private contact information. The GLEIF database primarily focuses on publicly available legal entity identifiers and associated registration details. For specific jurisdiction-level business registration data that includes officers, registered agents, or more detailed entity history, consider using dedicated state-level scrapers. For instance, if your focus is on Colorado businesses, the Colorado Secretary of State Business Search Scraper would be a more appropriate tool, as it can provide specific registered agent and formation date details not available here. Similarly, for New York, the New York Secretary of State Business Entity Search Scraper or for Mississippi, the Mississippi SOS Business Search Scraper offer deeper insights into state-specific registries.

What should you check before trusting the output?

• Watch for missing "entityName" or "lei" fields in any record, which indicates an incomplete fetch.
• Check that the "country" and "jurisdiction" fields are consistent with the expected geographical context.
• Verify that the "status" field reflects an expected value from the GLEIF API, such as "ISSUED" or "LAPSED", and not an empty string.
• Ensure that the "initialRegistrationDate" and "lastUpdated" fields are present and correctly formatted as YYYY-MM-DD.
• If you are filtering by country, confirm that all returned records have the specified 2-letter ISO "filterCountry" code.
• Confirm that the count of results does not exceed the "maxItems" you set, unless the total available results were fewer.

None of this proves a record is correct. It gives a scheduled GLEIF LEI Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

What is the cost to run the GLEIF LEI Scraper?

The Actor costs $0.005 per result on Apify's free plan, which translates to $5.00 for every 1,000 results. There is also a run-start fee, but result charges only apply to records written to your dataset. You can try it free, as Apify's free plan includes $5.00 of monthly usage, covering up to 1,000 results of this Actor before run-start charges. A first run with the example input will return at most 50 results, costing up to $0.25 in result charges.

How many entities can I search for using this Actor?

The GLEIF database covers 2M+ legal entities. You can search by company name or keyword, or fetch specific entities directly by their 20-character LEI code. The Actor allows you to filter results by registration status and country using ISO 2-letter codes. Each run can return a maximum of 1,000 records, which can be adjusted with the maxItems input control.

What kind of information does a LEI record contain?

Each LEI record contains fundamental details about a legal entity. These include the 20-character Legal Entity Identifier, the official entity name, entity type, jurisdiction, country, and the full legal address. You will also find its registration status (e.g., ISSUED, LAPSED), initial registration and last updated dates, and the name of the managing Local Operating Unit (LOU) that issued the LEI.

Can I filter results by specific countries or registration statuses?

Yes, you can filter the search results. The Actor allows you to specify a filterCountry using a 2-letter ISO code, such as 'US' or 'DE', to narrow down entities to a specific country. Additionally, you can apply a filterStatus to retrieve only entities with a particular registration status, like 'ISSUED' for active entities or 'LAPSED' for those with expired renewals, or leave it blank to see all statuses.

Is there an API key or authentication required to use this scraper?

No, there is no API key, registration, or authentication required to use the GLEIF LEI Scraper. It utilizes the publicly available GLEIF API, making it freely accessible for searching and extracting legal entity data. This simplifies its integration into workflows and allows for immediate use without prior setup.

Where to go next

When you are ready to run it, open GLEIF LEI Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the GLEIF LEI Scraper Actor page for the current input schema, pricing tier, and run history.

Other Actors we maintain for related data:

• GLEIF Legal Entity Scraper: Scrape GLEIF (Global Legal Entity Identifier Foundation), the global standard for identifying legal entities in financial transactions.
• Colorado Secretary of State Business Search Scraper: Search Colorado's official business entity registry by entity name, entity ID, registered agent name, or principal city.
• New York Secretary of State Business Entity Search Scraper: Search New York's free public business entity database by entity name, ID number, registered agent, county, entity type, jurisdiction, city, or officer name.
• Mississippi SOS Business Search Scraper: Search the Mississippi Secretary of State's free public business entity database by business name or exact business ID.

Related guides:

• Iowa SOS Business Entity Search Scraper: $5.00 per 1,000 results
• Mississippi SOS Business Search Scraper: 17 Data Fields per Record
• Texas Franchise Tax Account Status Scraper: 28 Data Fields per Record
• Florida Sunbiz Business Entity Search Scraper: 3 Practical Use Cases
• Australia ABN Business Register Scraper: 3 Practical Use Cases

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-10-06.

• Actor last updated by its maintainers on 2026-06-06.

• Run outcome figures cover the 30 day public window ending 2026-10-06.

• GLEIF LEI Scraper on Apify