GLEIF LEI Records Scraper

Search public GLEIF Legal Entity Identifier (LEI) records by legal name or exact LEI code, and export names, addresses, registration status and renewal dates. Use the results for company-reference enrichment and counterparty review. A name match alone is not an identity or compliance decision.

Quick start

Paste this small input into the Actor's JSON editor and start a run:

{
  "searchTerms": ["Apple"],
  "country": "US",
  "maxItems": 5,
  "includeRawRecord": false
}

Open the resulting dataset to review matches and export JSON, CSV or Excel. No GLEIF login or cookies are needed. Company names can match several legally distinct entities. Review the legal name, jurisdiction and address before joining records.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Check lapsed LEI registrations
• Fetch exact LEI records by LEI code
• Look up US company LEI records by legal name

What you get

One row per unique public LEI record, with its legal name and available addresses, jurisdiction, entity and registration states, and source dates. Optional parent identifiers appear only when supplied in returned relationships. The raw public source object is included only when that setting is enabled.

Who is it for?

• Supplier-data teams reviewing legal names and addresses before matching records.
• Account-reference researchers enriching an existing company list with known LEIs.
• Counterparty-data analysts inspecting public entity and registration information.
• Data engineers keeping source-linked reference records for manual review.

How you can use the data

• Review an ambiguous legal-name sample. Use the existing Apple search with the US legal-address country filter and a small cap. Inspect lei, legalName, jurisdiction and legalAddress before joining any match to your company record.
• Retrieve one known identifier. Use the existing exact-LEI recipe with a one-record cap. Exact retrieval runs before searches, and country or status filters do not constrain that known-code lookup.
• Inspect registration status and renewal context. Use a bounded filtered search when reviewing lapsed records, and keep registrationStatus, entityStatus, nextRenewalDate and sourceUrl together for human review. These are reference fields rather than sanctions screening or compliance certification.
• Keep source context in your own joins. Retain source URLs, match labels and optional raw records when needed. Combining exact codes with search filters also starts a filtered search, so distinguish exact-code results from additional search matches under the shared cap.

Input settings

All fields are optional. Exact LEIs are processed first, followed by name/filter searches, with one shared unique-record limit. Country and status filters apply to searches, not exact-LEI retrieval. Exact-LEI-only input does not add unrelated records. Combining exact codes with filters also starts a filtered search.

Setting	API key	Purpose
Legal names	searchTerms	One or more full or partial legal names.
Exact LEI codes	leiCodes	Known 20-character identifiers.
Legal address country	country	Two-letter country code for searches.
Registration status	registrationStatus	Search issued, lapsed or other supported registration states.
Entity status	entityStatus	Search active or inactive entities.
Maximum records	maxItems	Shared result cap. Default 50, form example 10.
Page size	pageSize	Search page size. Default 100, form example 10.
Include source record	includeRawRecord	Add rawRecord. Enabled by default.

Form suggestions are not API defaults. Omit all search/filter fields for a bounded browse of public records. {} saves at most 50 records. Results follow the source's order. There is no sorting control. No proxy or connection setting is supported.

For an exact lookup, use:

{
  "leiCodes": ["HWUPKR0MPOU8FGXBT394"],
  "maxItems": 1,
  "includeRawRecord": true
}

Output data

One dataset row represents one unique LEI. This abbreviated, shape-only example illustrates nullable optional fields. It is not a live company record:

{
  "lei": "EXAMPLE00000000000001",
  "legalName": "Example entity (illustration only)",
  "entityStatus": "ACTIVE",
  "registrationStatus": "ISSUED",
  "jurisdiction": null,
  "legalAddress": null,
  "headquartersAddress": null,
  "nextRenewalDate": null,
  "bic": [],
  "isin": [],
  "directParentLei": null,
  "ultimateParentLei": null,
  "matchedInput": "Example"
}

Fields	Meaning
lei, legalName	Identifier and legal name.
entityStatus, registrationStatus	Entity and registration state.
jurisdiction, legalForm, legalFormOther	Jurisdiction, form code and other-form description.
legalAddress, headquartersAddress	Nullable address objects with language, address lines, city, region, country, postal code and formatted address.
initialRegistrationDate, lastUpdateDate, nextRenewalDate	Available source dates.
managingLou	Managing Local Operating Unit identifier, not a detailed LOU profile.
bic, isin	Available identifier arrays. May be empty.
directParentLei, ultimateParentLei	Parent identifiers only when supplied in the returned relationship data. Often null.
sourceUrl, matchedInput	Source reference and matching name/LEI. matchedInput is null for filter-only browsing.
rawRecord	Full public source object, omitted when includeRawRecord is false.

The run's key-value store also contains RUN_SUMMARY with saved counts, warnings and completion information. Warnings can accompany partial results. Inspect them rather than treating every completed run as a complete match list.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing uses a one-time start charge and an item event for each unique LEI record saved. Empty searches save no rows but can still incur the start charge. Warnings are not paid dataset rows.

Start with a small shared cap and specific names or exact identifiers. See the live Pricing tab for current rates and discounts.

Tips for best results

• Use an exact LEI when you already know it. A legal-name match can identify several distinct entities.
• Review legal address and jurisdiction before matching. Country filters describe legal-address country rather than an identity certificate.
• Keep exact lookups and searches distinct. Filters do not restrict exact codes, and adding filters can also request a search.
• Choose raw-record output deliberately. Disable it when the selected fields suffice, or inspect the returned public object for source context.
• Read summary warnings before calling a match list complete. Shared limits or time stops can leave partial output.

Limits and caveats

Public reference data can change, and a name match alone does not establish entity identity or a compliance decision. The Actor does not perform sanctions screening, certify compliance or infer missing parent companies. Parent IDs are only present when supplied by returned relationship data.

Exact codes run before name or filter searches under one shared unique-record cap. Country and status filters apply to searches rather than exact lookups. Exact-code-only input does not add unrelated records, while combining exact codes with filters also starts a search.

Optional source fields and identifier arrays can be absent or empty. Broad searches are not guaranteed to finish within the run's time limit, while saved rows remain available after an early stop. Inspect RUN_SUMMARY saved counts, warnings and completion information rather than treating completion as an exhaustive match list.

Results follow source order without sorting controls. An input with no search or filter fields makes a bounded browse, not a specific company lookup. No login, cookies, proxy or connection setting is supported. Review source records before using them in a reference-data workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~gleif-lei-records-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "searchTerms": [
    "Apple"
  ],
  "country": "US",
  "maxItems": 5,
  "includeRawRecord": false
}
JSON

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",
  "maxItems": 5,
  "includeRawRecord": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/gleif-lei-records-scraper').call(run_input={'searchTerms': ['Apple'], 'country': 'US', 'maxItems': 5, 'includeRawRecord': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and AI-agent usage notes

The REST request starts a run asynchronously. Wait for it to finish, then use its defaultDatasetId to retrieve dataset items.

MCP and AI agents

You can ask your AI assistant to collect data with GLEIF LEI Records Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's GLEIF LEI Records Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use GLEIF LEI Records Scraper by Fetch Cat, or give it the identifier fetch_cat/gleif-lei-records-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s GLEIF LEI Records Scraper to collect up to 5 legal-name matches for Apple with legal-address country US and raw records off. Show LEIs, legal names, jurisdictions, legal addresses and source links for manual identity review.”
• “Retrieve the exact LEI HWUPKR0MPOU8FGXBT394 with a one-record cap and its public raw source record enabled. Show registration status and available renewal dates without certifying compliance.”
• “Collect up to 5 lapsed LEI registrations using the supported registration-status filter. Keep entity status, legal names and source links, and flag missing parent or address fields rather than inferring them.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I search by company name instead of an LEI?

Yes. Use searchTerms. Add country/status filters when useful. Partial names may match multiple entities, so verify identity rather than selecting the first result automatically.

Does this replace the GLEIF website or API?

It provides a normalized Apify export of public GLEIF reference data. It is not affiliated with GLEIF and does not add private records or verification services.

Why are parent LEIs or financial identifiers empty?

They are populated only from values available in the returned record. The Actor does not fetch additional parent records or securities mappings to fill gaps. rawRecord can help you inspect the source's available metadata.

Why did I get no results or only some requested LEIs?

Check spelling, filters and the run summary. A name search can legitimately have no matches. An unavailable exact lookup can be skipped with a warning. This does not prove that the entity is private or deleted. Other run failures still require attention.

Can I export CSV, Excel or JSON?

Yes, through the run's Apify dataset export controls or dataset API. Optional nested fields are easiest to inspect in JSON.

Related Actors

• SEC EDGAR Company Filings Scraper — US company filing research.
• North Data Company Records Scraper — Adjacent European company research.
• Poland KRS Company Registry Scraper — Polish registry records.
• WHOIS / RDAP Domain Lookup — Domain registration context, separate from legal-entity verification.
• Email MX & Deliverability Verifier — Check email-domain mail configuration alongside company enrichment.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥