# GLEIF LEI Scraper — Legal Entity Identifier Records (`devilscrapes/gleif-lei-records-scraper`) Actor

Export Legal Entity Identifier records from the GLEIF global register — LEI code, legal name, entity status, legal form, jurisdiction, registered address, BIC codes and registration dates — as clean JSON, CSV or Excel.

- **URL**: https://apify.com/devilscrapes/gleif-lei-records-scraper.md
- **Developed by:** [DevilScrapes](https://apify.com/devilscrapes) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

<div align="center">
  <img src=".actor/icon.svg" width="160" alt="Devil Scrapes mark" />

## GLEIF LEI Scraper — Legal Entity Identifier Records

**💰 $2.05 / 1 000 results**  ·  pay only for results  ·  no credit card to try

*We do the dirty work so your dataset stays clean.* 😈

Export Legal Entity Identifier records from the GLEIF global register — LEI code, legal name, entity status, legal form, jurisdiction, registered address, BIC codes and registration dates — as clean JSON, CSV or Excel.

</div>

***

### 🎯 What this scrapes

The LEI is the one identifier that ties a legal entity to its regulatory record worldwide, which makes GLEIF the reference file for KYC, AML and counterparty onboarding. Its API is JSON:API — every useful value sits two or three levels down under <code>data\[].attributes.entity</code>, and the address arrives as an array of lines. This Actor flattens all of it into one row per entity so a counterparty list becomes a spreadsheet.

### 🔥 What we handle for you

flattens JSON:API's three-level nesting into one row per entity
joins the registrar's address-line array into a readable field
retries transient 429/5xx responses instead of failing the whole run

### 💡 Use cases

- Resolve counterparty names to LEI codes for KYC and AML onboarding.
- Screen a client list for lapsed LEI registrations before a reporting deadline.
- Map a corporate group's registered entities across jurisdictions.
- Enrich a CRM with authoritative legal names, forms and registered addresses.

### ⚙️ How to use it

1. Click **Try for free** at the top of the page.
2. Fill in the input form — most fields have sensible defaults.
3. Click **Start**. Output streams into the run's dataset.
4. Export from **Storage → Dataset** as JSON, CSV, or Excel — or fetch via the API.

### 📥 Input

| Field | Type | Required | Default | Notes |
|---|---|:--:|---|---|
| `legalName` | `string` | no | 'Equinor' | Match entities whose registered legal name contains this text. |
| `country` | `string` | no | '—' | Two-letter ISO country code of the legal address, e.g. <code>NO</code>. Leave empty for every country. |
| `status` | `string` | no | 'ANY' | Filter by entity status. |
| `maxResults` | `integer` | no | 100 | Stop after this many entities. Each entity is one billed result row. |
| `proxyConfiguration` | `object` | no | {'useApifyProxy': False} | GLEIF is a public API and does not need a proxy. Leave this off unless your account requires egress through Apify Proxy. |

#### Example input

```json
{
  "legalName": "Equinor",
  "maxResults": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

### 📤 Output

Every row is one dataset item.

| Field | Type | Notes |
|---|---|---|
| `lei` | `string` | 20-character Legal Entity Identifier. |
| `legal_name` | `string` | Registered legal name. |
| `status` | `string` | Entity status: `ACTIVE` or `INACTIVE`. |
| `legal_form` | `string` | Legal form code, when published. |
| `jurisdiction` | `string` | Registration jurisdiction code. |
| `category` | `string` | Entity category, e.g. `FUND`, `BRANCH`. |
| `address` | `string` | Legal address lines, joined. |
| `city` | `string` | Legal address city. |
| `region` | `string` | Legal address region code. |
| `country` | `string` | Legal address country code. |
| `postal_code` | `string` | Legal address postal code. |
| `registered_as` | `string` | Local business-register identifier. |
| `bic` | `array` | Associated BIC/SWIFT codes. |
| `initial_registration_date` | `string` | First LEI registration date. |
| `last_update_date` | `string` | Last record update. |
| `next_renewal_date` | `string` | Date the LEI must be renewed. |
| `registration_status` | `string` | LEI registration status, e.g. `ISSUED`, `LAPSED`. |
| `url` | `string` | GLEIF search page for this LEI. |

#### Example output

```json
{}
```

### 💰 Pricing

Pay-Per-Event — you pay only when these events fire:

| Event | USD | What it is |
|---|---:|---|
| `actor-start` | $0.05 | One-off warm-up charge per run |
| `result` | $0.002 | Per dataset item |

Example: 1 000 results at the rates above ≈ **$2.05**. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

### 🚧 Limitations

- Returns the LEI register record only — no ownership hierarchy or financial data.
- BIC codes are present only for entities that have registered them with GLEIF.

### ❓ FAQ

**Do I need an API key?**

No. GLEIF publishes the register openly and needs no credentials.

**Can I look up one specific LEI?**

Search by legal name and filter the result, or set the name to the exact entity — the API matches on the registered legal name.

**Why are some addresses missing a street?**

GLEIF stores address lines as an array that some registrars leave sparse. The Actor joins whatever lines exist and leaves the field empty rather than inventing one.

### 💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an
issue on the Actor's **Issues** tab on Apify Console — we ship
fixes weekly and we read every report.

***

<div align="center">

Built by **[Devil Scrapes](https://apify.com/DevilScrapes)** 😈 — a small fleet of
opinionated public-data Actors. Honest pricing, real engineering, zero fine print.

</div>

# Actor input Schema

## `legalName` (type: `string`):

Match entities whose registered legal name contains this text.

## `country` (type: `string`):

Two-letter ISO country code of the legal address, e.g. <code>NO</code>. Leave empty for every country.

## `status` (type: `string`):

Filter by entity status.

## `maxResults` (type: `integer`):

Stop after this many entities. Each entity is one billed result row.

## `proxyConfiguration` (type: `object`):

GLEIF is a public API and does not need a proxy. Leave this off unless your account requires egress through Apify Proxy.

## Actor input object example

```json
{
  "legalName": "Equinor",
  "status": "ANY",
  "maxResults": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `datasetItems` (type: `string`):

All dataset items as JSON.

## `datasetItemsCsv` (type: `string`):

Same data exported to CSV.

## `datasetView` (type: `string`):

Open the run dataset in the Console.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "legalName": "Equinor",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("devilscrapes/gleif-lei-records-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "legalName": "Equinor",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("devilscrapes/gleif-lei-records-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "legalName": "Equinor",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call devilscrapes/gleif-lei-records-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,devilscrapes/gleif-lei-records-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zfeyTGip3KpCvOxjt/builds/XjLhUGfDJEbMOQ6x6/openapi.json