# New LEI Registrations: Newly Registered Legal Entities (`veridra/new-lei-registrations`) Actor

Get legal entities that just received an LEI from GLEIF: legal name, registration number, legal form, jurisdiction, address and status. Filter by date, country, category and name. Daily feed of new companies and funds.

- **URL**: https://apify.com/veridra/new-lei-registrations.md
- **Developed by:** [Veridra Computer Technology](https://apify.com/veridra) (community)
- **Categories:** Lead generation, Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does New LEI Registrations do?

**New LEI Registrations** returns the legal entities that were just issued a **Legal Entity Identifier (LEI)**, straight from the official GLEIF API. Every new company, fund or branch that will trade, borrow or report in financial markets needs an LEI, so this is an early, worldwide signal of new and newly active businesses. It returns what GLEIF publishes; it does not verify or score the entities.

It collects data from **[GLEIF (Global Legal Entity Identifier Foundation)](https://www.gleif.org/en/lei-data/gleif-api)** and returns clean, structured results you can download or pull through the **Apify API**.

### Why use New LEI Registrations?

- **Fintech, banking and payments sales:** reach companies and funds the week they get the identifier they need to open accounts, trade or report.
- **KYC and onboarding teams:** pull fresh LEI records with registration numbers, legal forms and addresses to pre-fill and check customer files.
- **Fund and asset-management research:** follow new funds by country, with the umbrella or manager LEI when it is reported.
- **Market and competitor intelligence:** count new legal entities by country, legal form or name, and schedule daily runs to build a time series.
- **AI agents:** clean, consistent JSON with a link to the official GLEIF record on every result.
- Runs on the Apify platform: schedule runs, call it through the API, connect it to integrations, and get notified when a run fails.

### What data can New LEI Registrations extract?

| Field | Type | Description |
| --- | --- | --- |
| `lei` | string | The 20-character Legal Entity Identifier. |
| `legalName` | string | Legal name as registered with GLEIF. |
| `otherNames` | array | Other and transliterated names of the entity. |
| `registrationNumber` | string | The entity's number in its local business register. |
| `registrationAuthorityId` | string | GLEIF code of the business register (RA list code). |
| `jurisdiction` | string | Legal jurisdiction, as an ISO country or subdivision code. |
| `legalFormCode` | string | ISO 20275 Entity Legal Form (ELF) code. |
| `legalForm` | string | Name of the legal form: English when GLEIF has one, otherwise the local name; the form in words when no ELF code applies. |
| `category` | string | Entity category: GENERAL, FUND, BRANCH, RESIDENT_GOVERNMENT_ENTITY or INTERNATIONAL_ORGANIZATION. |
| `subCategory` | string | Entity subcategory, for government entities. |
| `entityStatus` | string | ACTIVE or INACTIVE. |
| `entityCreationDate` | string | Date the entity itself was created (YYYY-MM-DD), when reported. |
| `leiIssuedDate` | string | Date the LEI was first issued (YYYY-MM-DD). |
| `registrationStatus` | string | Status of the LEI registration, for example ISSUED or PENDING_TRANSFER. |
| `nextRenewalDate` | string | Date the LEI must be renewed by (YYYY-MM-DD). |
| `corroborationLevel` | string | How far the issuer checked the data against an authoritative source. |
| `managingLou` | string | LEI of the Local Operating Unit that issued and manages this LEI. |
| `legalAddress` | string | Street lines of the registered legal address. |
| `legalCity` | string | City of the legal address. |
| `legalRegion` | string | ISO 3166-2 region of the legal address, when reported. |
| `legalPostalCode` | string | Postal code of the legal address. |
| `legalCountry` | string | Two-letter ISO country code of the legal address. |
| `headquartersAddress` | string | Street lines of the headquarters address. |
| `headquartersCity` | string | City of the headquarters address. |
| `headquartersCountry` | string | Two-letter ISO country code of the headquarters address. |
| `associatedEntityLei` | string | LEI of the associated entity, such as a fund's umbrella or manager, when reported. |
| `associatedEntityName` | string | Name of the associated entity, when reported without an LEI. |
| `bic` | array | SWIFT/BIC codes GLEIF maps to this LEI. |
| `gleifUrl` | string | The entity's page in GLEIF's LEI search, for verification. |
| `sourceUrl` | string | GLEIF API record for this LEI. |
| `scrapedAt` | string | When this result was collected (UTC, ISO 8601). |

### How to use New LEI Registrations

1. Open the actor and select **Try for free**.
2. Fill in **Days back**, **Issued from**. The prefilled example works as a first test.
3. Set **Maximum results** to control how much data, and cost, a run produces.
4. Select **Start** and wait for the run to finish.
5. Download the results as JSON, CSV, Excel or HTML, or fetch them through the API.

### How much does it cost to use New LEI Registrations?

You pay per result: **$5.00 per 1,000 results** ($0.005 each), plus Apify's small start fee of $0.0001 per run. For example, 1,000 results cost about $5.00. You can set a maximum cost per run in the run options, and the actor stops cleanly when it is reached.

Subscribers to Apify's paid plans pay less per result: 10% off on Bronze, 20% off on Silver and 30% off on Gold and higher plans.

### Get only new results

Turn on **Only new results** and schedule the actor (for example daily) to use it as a monitor: each run skips what earlier runs already returned, so you get a feed of new records and pay only for those. The first run returns everything that matches. The memory lives in your own Apify account; give runs the same **Monitor name** to share it when you change other inputs.

### Use it from AI agents

AI agents can find and run New LEI Registrations as a tool through Apify's MCP server (mcp.apify.com) or the Apify API, and get the same structured results, billed per result. Without code, Apify's Zapier, Make and n8n integrations can start it and send each new result to a sheet, CRM or chat.

### Input

See the **Input** tab for every option. The main fields:

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `daysBack` | integer | 7 | LEIs issued in this many days up to today, today included. Ignored when a start date is set. |
| `dateFrom` | string | "" | Only LEIs first issued on or after this date (YYYY-MM-DD). Leave empty to use Days back. |
| `dateTo` | string | "" | Only LEIs first issued on or before this date (YYYY-MM-DD). Leave empty for today. |
| `countries` | array | \[] | Two-letter ISO codes of the legal address country, for example DE, GB or AE. Leave empty for every country. |
| `categories` | array | \["GENERAL", "FUND", "BRANCH", "RESIDENT_GOVERNMENT_ENTITY", "INTERNATIONAL_ORGANIZATION"] | Which kinds of legal entity to include. Sole proprietors are not offered because they are people trading under their own name. |
| `nameContains` | string | "" | Only entities whose legal name contains this text, for example Capital or Bank. |
| `onlyActive` | boolean | true | Leave out entities GLEIF already marks as inactive. |
| `maxResults` | integer | 1000 | Stop after this many results. Each result costs $0.005, so this also caps the cost of a run. Use 0 for no limit. Keep it low for a first test. |
| `onlyNew` | boolean | false | Monitoring mode: skip results this monitor returned in earlier runs, so a scheduled run returns, and bills, only what is new. The first run returns everything that matches. |
| `monitorName` | string | "" | Runs with the same name share one memory of returned results, even if you change other inputs. Leave empty to keep a separate memory for each distinct input. |

Example input:

```json
{
  "daysBack": 3,
  "maxResults": 20
}
```

### Output

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. Example items:

```json
[
  {
    "lei": "98450098BAC5D3GA5853",
    "legalName": "TH73 PRIVATE LIMITED",
    "otherNames": [],
    "registrationNumber": "202645181M",
    "registrationAuthorityId": "RA000523",
    "jurisdiction": "SG",
    "legalFormCode": "Y8W9",
    "legalForm": "Exempt Private Company",
    "category": "GENERAL",
    "subCategory": null,
    "entityStatus": "ACTIVE",
    "entityCreationDate": "2026-09-30",
    "leiIssuedDate": "2026-10-19",
    "registrationStatus": "ISSUED",
    "nextRenewalDate": "2027-10-19",
    "corroborationLevel": "FULLY_CORROBORATED",
    "managingLou": "529900T8BM49AURSDO55",
    "legalAddress": "2 VENTURE DRIVE, #19-21, VISION EXCHANGE",
    "legalCity": "Singapore",
    "legalRegion": "SG-01",
    "legalPostalCode": "608526",
    "legalCountry": "SG",
    "headquartersAddress": "2 VENTURE DRIVE, #19-21, VISION EXCHANGE",
    "headquartersCity": "Singapore",
    "headquartersCountry": "SG",
    "associatedEntityLei": null,
    "associatedEntityName": null,
    "bic": [],
    "gleifUrl": "https://search.gleif.org/#/record/98450098BAC5D3GA5853",
    "sourceUrl": "https://api.gleif.org/api/v1/lei-records/98450098BAC5D3GA5853",
    "scrapedAt": "2026-10-19T18:49:54+00:00"
  },
  {
    "lei": "984500V14D1CQD6A9843",
    "legalName": "OPNISCIENCE CORP.",
    "otherNames": [],
    "registrationNumber": "7646465",
    "registrationAuthorityId": "RA000602",
    "jurisdiction": "US-DE",
    "legalFormCode": "XTIQ",
    "legalForm": "Corporation",
    "category": "GENERAL",
    "subCategory": null,
    "entityStatus": "ACTIVE",
    "entityCreationDate": "2023-08-29",
    "leiIssuedDate": "2026-10-19",
    "registrationStatus": "ISSUED",
    "nextRenewalDate": "2027-10-19",
    "corroborationLevel": "FULLY_CORROBORATED",
    "managingLou": "529900T8BM49AURSDO55",
    "legalAddress": "2140 S DUPONT HWY",
    "legalCity": "CAMDEN",
    "legalRegion": "US-DE",
    "legalPostalCode": "19934",
    "legalCountry": "US",
    "headquartersAddress": "2140 S DUPONT HWY",
    "headquartersCity": "CAMDEN",
    "headquartersCountry": "US",
    "associatedEntityLei": null,
    "associatedEntityName": null,
    "bic": [],
    "gleifUrl": "https://search.gleif.org/#/record/984500V14D1CQD6A9843",
    "sourceUrl": "https://api.gleif.org/api/v1/lei-records/984500V14D1CQD6A9843",
    "scrapedAt": "2026-10-19T18:49:55+00:00"
  }
]
```

### Tips

- Set Days back to 1, turn on Only new results and schedule a daily run to get a feed of each day's new LEIs.
- Use Countries to focus on your market, for example AE and SA for the Gulf, or DE, FR and NL for the EU.
- Choose only Funds under Entity categories to follow new investment funds.
- Schedule the actor to keep a dataset fresh, and use the API or integrations to send new results where you need them.

### FAQ, disclaimers, and support

#### Where does the data come from?

From GLEIF (Global Legal Entity Identifier Foundation) (api.gleif.org). Data is used under: GLEIF LEI data is published free of charge under the Creative Commons CC0 1.0 public domain dedication; reuse, including commercial reuse, needs no permission. See the source's terms: https://www.gleif.org/en/meta/lei-data-terms-of-use

#### Is it legal to use this data?

This actor only collects publicly available data from GLEIF (Global Legal Entity Identifier Foundation) and does not collect personal data about private individuals. Check that your use complies with the source's terms and the laws that apply to you. This actor is not affiliated with or endorsed by GLEIF (Global Legal Entity Identifier Foundation).

#### How fresh is the data?

GLEIF publishes new and updated LEI records several times a day, and the actor queries the live API on every run. A record usually appears within a day of the LEI being issued.

#### Why are sole proprietors missing?

Sole proprietors are people trading under their own name, often from a home address. To avoid returning personal data, the actor never returns them, and it drops address lines that start with c/o (care of a person).

#### What is the difference between the LEI issued date and the entity creation date?

The LEI issued date is when the entity received its identifier. The entity creation date is when the company or fund itself was set up, which can be years earlier: an older company that only now needs an LEI shows up as a new registration too.

#### Does an LEI mean the company is verified?

LEI issuers check registration data against a business register, and corroborationLevel shows how far that check went. It is not a credit, sanctions or ownership check.

#### Something is not working

Open an issue in the **Issues** tab with your run link and we will look at it. For programmatic access, see the **API** tab.

# Changelog

This Actor's version history is a separate document: https://apify.com/veridra/new-lei-registrations/changelog.md

# Actor input Schema

## `daysBack` (type: `integer`):

LEIs issued in this many days up to today, today included. Ignored when a start date is set.

## `dateFrom` (type: `string`):

Only LEIs first issued on or after this date (YYYY-MM-DD). Leave empty to use Days back.

## `dateTo` (type: `string`):

Only LEIs first issued on or before this date (YYYY-MM-DD). Leave empty for today.

## `countries` (type: `array`):

Two-letter ISO codes of the legal address country, for example DE, GB or AE. Leave empty for every country.

## `categories` (type: `array`):

Which kinds of legal entity to include. Sole proprietors are not offered because they are people trading under their own name.

## `nameContains` (type: `string`):

Only entities whose legal name contains this text, for example Capital or Bank.

## `onlyActive` (type: `boolean`):

Leave out entities GLEIF already marks as inactive.

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

Stop after this many results. Each result costs $0.005, so this also caps the cost of a run. Use 0 for no limit. Keep it low for a first test.

## `onlyNew` (type: `boolean`):

Monitoring mode: skip results this monitor returned in earlier runs, so a scheduled run returns, and bills, only what is new. The first run returns everything that matches.

## `monitorName` (type: `string`):

Runs with the same name share one memory of returned results, even if you change other inputs. Leave empty to keep a separate memory for each distinct input.

## Actor input object example

```json
{
  "daysBack": 3,
  "dateFrom": "",
  "dateTo": "",
  "countries": [],
  "categories": [
    "GENERAL",
    "FUND",
    "BRANCH",
    "RESIDENT_GOVERNMENT_ENTITY",
    "INTERNATIONAL_ORGANIZATION"
  ],
  "nameContains": "",
  "onlyActive": true,
  "maxResults": 20,
  "onlyNew": false,
  "monitorName": ""
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset containing all results

# 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 = {
    "daysBack": 3,
    "maxResults": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("veridra/new-lei-registrations").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 = {
    "daysBack": 3,
    "maxResults": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("veridra/new-lei-registrations").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 '{
  "daysBack": 3,
  "maxResults": 20
}' |
apify call veridra/new-lei-registrations --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,veridra/new-lei-registrations"
        }
    }
}
```

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/LRzYZHeUXsfLq10WJ/builds/9NFHIfgXdZxjgnCZK/openapi.json