GLEIF New LEI Feed: New Companies & Funds Worldwide (official API, no key)

Get every newly registered Legal Entity Identifier (LEI) worldwide, the day it is issued, from the official GLEIF API (CC0 open data). Around 1,100-1,500 new LEIs are issued every day: new companies, holding companies, SPVs, investment funds, branches and subsidiaries that are about to trade securities, take out financing, open institutional accounts or report under EMIR, MiFID II or Dodd-Frank. That makes the LEI feed a global new-company signal you can filter by country, legal form (GmbH, AG, Ltd, LLC, SICAV...), jurisdiction (e.g. Delaware) and category (companies or funds). Add lapsed and retired / merged LEIs to track entities going dormant, and turn on parent enrichment to see the direct and ultimate parent company behind each new entity.

Who it's for

• B2B sales and business development: a daily list of new legal entities in your countries, e.g. new German GmbHs, new Delaware LPs, new Luxembourg funds. New entities need banks, auditors, fund administrators, law firms, insurers, software and office space.
• Fund administrators, custodians, depositaries and transfer agents: new funds (categories: ["FUND"]) in LU, IE, KY, US the day they get an LEI, often before launch.
• Banks, KYC / AML and compliance teams: new and lapsed counterparties, parent chains and reporting exceptions; lapsed LEIs signal reporting problems.
• M&A, private equity and corporate-structure research: new subsidiaries and SPVs of known groups (ultimate parent), retired / merged LEIs after deals.
• Data vendors, CRMs and AI agents: clean JSON with ISO country / region codes, ISO 20275 legal form codes plus readable names, registry numbers and GLEIF links.

Why this Actor

• Feed, not a lookup: existing GLEIF Actors search one LEI at a time. This one delivers what is new: a stateless lookback window by default, or new since last run with per-schedule history so a daily schedule pays only for LEIs it has not delivered yet.
• Three event types: new registrations, lapsed (renewal date passed without renewal) and retired (retired or merged).
• Smart filters: legal forms by ELF code or plain name / abbreviation (GmbH, AG, Aktiebolag, LLP, SICAV), resolved against the bundled ISO 20275 ELF code list (3,600 forms); jurisdictions like US-DE; countries; categories.
• Readable output: legal form name and the abbreviation the entity actually uses, managing LOU (LEI issuer) name, founding date and age at registration (spot brand-new companies vs old companies getting their first LEI), flattened legal and HQ address, registry ID.
• Optional parents: direct and ultimate accounting-consolidation parent (LEI, name, country) or GLEIF's reporting-exception reason (NATURAL_PERSONS, NON_CONSOLIDATING, NO_LEI, NO_KNOWN_PERSON...).
• Entity-level only: sole proprietors (natural persons) are always excluded. No personal data.
• Official, open, polite: GLEIF API, no key, CC0 1.0 licence; under 1 request per second with retries.
• Fast: the default run returns 30 LEIs in about 2 seconds at 512 MB.

Quick start

1. Click Start with the default input {}. You get the 30 newest LEIs from the latest UTC day with data.
2. New US companies and funds of the last 2 days: {"countries": ["US"], "daysBack": 2, "maxItems": 300}
3. New German GmbHs and UGs: {"countries": ["DE"], "legalForms": ["GmbH"], "daysBack": 3, "maxItems": 500}
4. New Luxembourg and Irish funds: {"countries": ["LU", "IE"], "categories": ["FUND"], "daysBack": 7, "maxItems": 500}
5. New Delaware entities with parent companies: {"jurisdictions": ["US-DE"], "includeParents": true, "maxItems": 50}
6. Lapsed and retired LEIs in the UK: {"eventTypes": ["lapsed", "retired"], "countries": ["GB"], "daysBack": 3, "maxItems": 200}

Schedule tip (daily feed)

Create an Apify Schedule (for example daily at 06:00 UTC, after GLEIF's overnight publication) with:

{ "mode": "sinceLastRun", "stateKey": "de-gmbh-daily", "countries": ["DE"], "legalForms": ["GmbH"], "maxItems": 1000 }

Use one stateKey per schedule. Each run delivers only LEIs not delivered before for that key (it re-checks the last 3 days, because issuers sometimes publish records a day or two late). Connect the run to Slack, email, Google Sheets, Airtable, HubSpot, Make, Zapier, n8n or a webhook via Apify integrations.

Input

Field	Meaning
mode	window (default, stateless) or sinceLastRun (set this for schedules)
eventTypes	new (default), lapsed, retired (retired or merged); several allowed, maxItems is split between them
daysBack	UTC days ending today, default 1. In window mode a short window is widened one day at a time (max 7) so the latest day with data is covered (autoExtend)
countries	Legal-address country codes: US, GB, DE, LU, IE, KY, SG...
legalForms	ELF codes (2HBR, XJHM) or names / abbreviations (GmbH, AG, Ltd, LLP, SICAV, Aktiebolag)
jurisdictions	US-DE, US-NY, CA-ON, GB, KY...
categories	GENERAL, FUND, BRANCH, INTERNATIONAL_ORGANIZATION, RESIDENT_GOVERNMENT_ENTITY (sole proprietors always excluded)
includeParents	Add direct and ultimate parent or reporting-exception reason (extra lei-enriched event, ~2 s per record)
maxItems	Cap per run (also caps your spend), default 30
autoExtend	Window mode: widen a short window (default on)
stateKey	One key per saved search (sinceLastRun)

Output

Base fields (always): lei, eventType (new / lapsed / retired), eventDate (registration date, renewal date or last update date, UTC), legalName, legalNameLanguage, otherNames, legalFormCode, legalFormName, legalFormAbbreviation, legalFormOther, jurisdiction, category, subCategory, entityStatus, entityCreationDate, entityAgeDaysAtRegistration, registeredAs (registry number), registrationAuthorityId, legalAddress, legalCity, legalRegion, legalCountry, legalPostalCode, hqAddress, hqCity, hqRegion, hqCountry, hqPostalCode, registrationStatus, initialRegistrationDate, lastUpdateDate, nextRenewalDate, managingLou, managingLouName, corroborationLevel, expirationDate, expirationReason, successorLei, successorName, bic, hasDirectParent, hasUltimateParent, gleifUrl, apiUrl, firstSeenAt.

Parent fields (filled when includeParents is on, otherwise null): enriched, directParentLei, directParentName, directParentCountry, directParentException, ultimateParentLei, ultimateParentName, ultimateParentCountry, ultimateParentException.

Example (a real enriched record):

{
  "lei": "254900ZE5SHQ5U4KB714",
  "eventType": "new",
  "eventDate": "2026-10-29",
  "legalName": "Wipro Technologies GmbH",
  "legalNameLanguage": "de",
  "otherNames": [],
  "legalFormCode": "2HBR",
  "legalFormName": "Gesellschaft mit beschränkter Haftung",
  "legalFormAbbreviation": "GmbH",
  "legalFormOther": null,
  "jurisdiction": "DE",
  "category": "GENERAL",
  "subCategory": null,
  "entityStatus": "ACTIVE",
  "entityCreationDate": "2017-05-29",
  "entityAgeDaysAtRegistration": 3440,
  "registeredAs": "HRB 108590",
  "registrationAuthorityId": "RA000242",
  "legalAddress": "Senckenberganlage 19",
  "legalCity": "Frankfurt Am Main",
  "legalRegion": "DE-HE",
  "legalCountry": "DE",
  "legalPostalCode": "60325",
  "hqAddress": "Senckenberganlage 19",
  "hqCity": "Frankfurt Am Main",
  "hqRegion": "DE-HE",
  "hqCountry": "DE",
  "hqPostalCode": "60325",
  "registrationStatus": "ISSUED",
  "initialRegistrationDate": "2026-10-29",
  "lastUpdateDate": "2026-10-29",
  "nextRenewalDate": "2027-10-29",
  "managingLou": "5493001KJTIIGC8Y1R12",
  "managingLouName": "Bloomberg Finance L.P.",
  "corroborationLevel": "FULLY_CORROBORATED",
  "expirationDate": null,
  "expirationReason": null,
  "successorLei": null,
  "successorName": null,
  "bic": [],
  "hasDirectParent": false,
  "hasUltimateParent": true,
  "gleifUrl": "https://search.gleif.org/#/record/254900ZE5SHQ5U4KB714",
  "apiUrl": "https://api.gleif.org/api/v1/lei-records/254900ZE5SHQ5U4KB714",
  "enriched": true,
  "directParentLei": null,
  "directParentName": null,
  "directParentCountry": null,
  "directParentException": "NO_LEI",
  "ultimateParentLei": "335800IFS1IJHESG8362",
  "ultimateParentName": "WIPRO LIMITED",
  "ultimateParentCountry": "IN",
  "ultimateParentException": null,
  "firstSeenAt": "2026-10-31T06:59:51.366Z"
}

See sample-output.json for more. Every run also writes a summary (windows, resolved filters, total matching records, counts, why it stopped) to the OUTPUT record. Download as JSON, CSV, Excel or via API.

Pricing

Pay per event (Apify takes care of billing; you only pay for what is delivered):

Event	Price	Charged
apify-actor-start	$0.005	once per run
lei-record	$0.003	per LEI record delivered
lei-enriched	$0.005	additionally per record with parent companies, only when includeParents is on

A default test run (30 new LEIs, no parents) costs about $0.095. With includeParents on, each record costs $0.008 in total. maxItems and Apify's max cost per run cap your spend; the Actor never delivers more than your run budget allows. No separate platform-usage charges: compute is included in the event prices.

Data source and notes

• GLEIF API (/lei-records, parent and reporting-exception endpoints, no key) and the ISO 20275 ELF code list. LEI data is published by GLEIF under CC0 1.0. This Actor is not affiliated with or endorsed by GLEIF.
• Dates are UTC. GLEIF publishes updates several times a day; a new LEI usually appears within hours of issuance.
• An LEI's entityCreationDate is when the entity was founded, not when it got the LEI. Use entityAgeDaysAtRegistration < 90 to focus on truly new companies.
• Parent relationships are often reported some days after a new LEI is issued, so many new records show a reporting exception instead.
• retired uses the record's last update date as the event date; GLEIF sometimes re-touches retired records in bulk.

FAQ

Is this a list of all newly incorporated companies? It is every entity that obtained a new LEI. Most are companies, funds and SPVs active in financial markets; very small local businesses often never get an LEI. How fresh is it? Live from the GLEIF API at run time (the golden copy is refreshed several times a day). Can I look up a specific company? Use the gleifUrl / apiUrl, or a GLEIF lookup Actor; this Actor is a feed of changes. Do I need an API key? No.