GLEIF LEI Lookup

🔎 GLEIF LEI lookup for legal entity data

GLEIF LEI Lookup searches the public GLEIF Legal Entity Identifier data and saves clean company records you can export from Apify. Search by company name, exact 20-character LEI code, country filters, or a mix of targets, then get official registry facts, addresses, registration dates, parent relationship context, ISIN links, and deterministic KYB decision fields.

Use it when you need repeatable LEI lookup, vendor onboarding checks, counterparty screening, company enrichment, or a GLEIF data API workflow without maintaining your own LEI database. Each saved dataset row is one accepted GLEIF LEI entity record. Batch runs also write a PORTFOLIO_SUMMARY key-value output with totals, risk distribution, country exposure, priority queues, and watchlist health.

For a first run, keep the prefilled targets Apple and HWUPKR0MPOU8FGXBT394, keep Max records at 25, and start the Actor. Once the row shape fits your workflow, add more company names, paste LEI codes, add country filters, or turn on the richer relationship and securities options.

✅ What this Actor does

• Looks up GLEIF LEI records by company name or exact LEI code.
• Exports filtered country datasets by ISO country code, entity status, and entity category.
• Saves one dataset row per accepted Legal Entity Identifier record.
• Returns official legal names, alternate names, entity status, jurisdiction, legal form, registration authority, addresses, registration dates, managing LOU, and source URLs.
• Adds parent basics, child counts, relationship edges, and reporting exceptions when relationship enrichment is enabled and GLEIF provides the data.
• Adds ISIN/security links when securities enrichment is enabled and available.
• Adds deterministic decision fields such as recommended action, risk score, risk band, identity confidence, ownership transparency, onboarding complexity, and renewal state.
• Supports watchlist snapshots so scheduled runs can flag first-seen, unchanged, and changed LEI records.
• Works with Apify dataset exports, API access, schedules, webhooks, and integrations.
• Charges only for saved LEI records.

This Actor focuses on public GLEIF data. It does not provide sanctions, PEP, adverse media, OFAC, SEC, OpenCorporates, Companies House, or legal advice.

📦 Data you can export

Each dataset item is one official GLEIF Legal Entity Identifier record. Fields can be null or empty when GLEIF does not expose that data or when your selected output detail keeps the row compact.

• lei, matchedInputs, legalName, and otherNames
• entity with status, category, subcategory, jurisdiction, legal form, registration authority, registered-as number, and BIC codes
• registration with LEI status, initial registration date, last update date, next renewal date, managing LOU, and registration-number match state
• legalAddress and headquartersAddress
• parents with direct parent, ultimate parent, child count, and ownership-opacity signal
• relationships with parent, child, or other relationship edges when collected
• securities with ISIN links when collected
• decision with policy profile, recommended action, risk score, risk band, risk factors, review flags, identity confidence, ownership transparency, onboarding complexity, and renewal state
• watchlist with change status and changed fields when a watchlist name is supplied
• sourceUrl linking back to the public GLEIF record

🎯 Common use cases

• Enrich a vendor or customer list with official LEI records.
• Check whether a known LEI code is active, issued, renewed, and tied to the expected legal entity.
• Build country-level legal entity exports for research or screening.
• Add GLEIF source URLs and registration facts to a CRM, warehouse, spreadsheet, or compliance review queue.
• Review parent ownership context before onboarding a counterparty.
• Track a fixed watchlist of entities with scheduled Apify runs.
• Feed source-backed LEI data into an internal KYB workflow through the Apify API.

▶️ How to run it

1. Open the Actor input.
2. Add company names or exact LEI codes in Company names or LEI codes.
3. Optional: add ISO country codes such as US, GB, or DE in Countries.
4. Set Max records to control runtime and cost. Use 0 only when you want every matching record.
5. Choose Entity status, Entity category, Decision policy, and Output detail.
6. Turn relationship, securities, or graph-ready relationship data on only when you need that extra context.
7. Optional: add a Watchlist name or Registration number for repeat monitoring and corroboration.
8. Start the Actor and open the dataset or PORTFOLIO_SUMMARY output.

You can export results as JSON, CSV, Excel, XML, RSS, or HTML. You can also call the Actor through the Apify API, schedule repeat runs, or send results to another system with webhooks.

⚙️ Input

Example input:

{
  "queries": ["Apple", "HWUPKR0MPOU8FGXBT394"],
  "countries": ["US"],
  "maxRecords": 25,
  "entityStatus": "ACTIVE",
  "entityCategory": "GENERAL",
  "policyProfile": "balanced",
  "outputProfile": "standard",
  "includeRelationships": true,
  "includeSecurities": false,
  "includeGraphEdges": false,
  "watchlistName": "vendor-review",
  "registrationNumber": "C0806592"
}

🎯 Targets and filters

Use queries for specific company names or exact LEI codes. Use countries for filtered exports. You can fill both in one run; the Actor deduplicates accepted LEI records before saving them.

Use entityStatus and entityCategory when you want GLEIF-backed filters. Leave them blank for broader matching.

🧭 Decisions and output detail

Use policyProfile to choose how the deterministic decision fields weigh status, renewal, identity, and ownership evidence. Use outputProfile to control how much detail each row carries:

• essential: core LEI identity, statuses, dates, addresses, source URL, and compact decision scores.
• decision: adds decision evidence, registration-number corroboration, and watchlist changes.
• standard: adds alternate names, legal and registration labels, BIC codes, and parent basics.
• full: keeps requested relationship and ISIN/security arrays.

📄 Output example

{
  "lei": "HWUPKR0MPOU8FGXBT394",
  "matchedInputs": ["Apple", "HWUPKR0MPOU8FGXBT394"],
  "legalName": "APPLE INC.",
  "otherNames": ["Apple Computer, Inc."],
  "entity": {
    "status": "ACTIVE",
    "category": "GENERAL",
    "subcategory": null,
    "jurisdiction": "US-CA",
    "legalForm": { "code": "XTIQ", "name": "Corporation" },
    "registeredAs": "C0806592",
    "registrationAuthority": { "id": "RA000598", "name": "California Secretary of State" },
    "bicCodes": []
  },
  "registration": {
    "status": "ISSUED",
    "initialRegistrationDate": "2012-06-06",
    "lastUpdateDate": "2026-01-15",
    "nextRenewalDate": "2027-01-15",
    "managingLou": "EVK05KS7XY1DEII3R011",
    "registrationNumberMatch": "matched"
  },
  "decision": {
    "policyProfile": "balanced",
    "recommendedAction": "approve",
    "riskScore": 18,
    "riskBand": "low",
    "identityConfidence": 98,
    "identityVerdict": "strong_match",
    "ownershipTransparency": "clear",
    "onboardingComplexity": "standard",
    "renewalState": "current"
  },
  "sourceUrl": "https://search.gleif.org/#/record/HWUPKR0MPOU8FGXBT394"
}

The actual dataset row also includes address, parent, relationship, securities, and watchlist fields from the approved output schema.

💳 Pricing

This Actor uses pay-per-event pricing. You are charged once for each accepted LEI record saved to the dataset. The current local pricing artifact sets Checked LEI record at $0.0018 per saved record.

The portfolio summary, watchlist comparison fields, and optional enrichment fields are part of the saved LEI record. They are not separate charge events.

⚠️ Limits and caveats

• Max records controls the number of accepted LEI records saved across the run.
• Max records set to 0 means every matching record, subject to normal Actor runtime and source availability.
• Relationship and securities enrichment can add runtime on large exports.
• Some entities do not have parent, child, relationship, ISIN, BIC, or watchlist-change data in GLEIF.
• Decision fields are deterministic indicators from GLEIF facts. They are not legal, compliance, or financial advice.

❓ FAQ

Do I need a GLEIF API key?

No. The Actor uses public GLEIF data and does not ask you for GLEIF credentials, cookies, or a private source account.

Can I use it as a GLEIF data API?

Yes. Run the Actor through the Apify API, schedule it, export the dataset, or connect it to webhooks and integrations. The dataset rows are structured for downstream systems.

Does it screen sanctions or adverse media?

No. It only uses GLEIF LEI data. Use a separate screening source if you need sanctions, PEP, adverse media, or other risk lists.

Why are some fields empty?

GLEIF does not expose every relationship, security, address detail, or code label for every entity. The Actor keeps unavailable source data empty instead of inventing values.

📝 Changelog

• 0.0: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• Pappers Sirene Scraper ↗ - Search and enrich French company registry data with official identifiers, addresses, financials, dirigeants, and establishments.
• LinkedIn Company Scraper ↗ - Export public LinkedIn company profile data for account research and CRM enrichment.
• LinkedIn Company People Scraper ↗ - Extract visible people from LinkedIn company People pages using your own browser session.
• Business Address Scraper ↗ - Find physical business addresses shown on public company websites.
• Harris County Court Records Scraper ↗ - Export public Harris County Probate and Civil case metadata, parties, attorneys, and filing events.

Made with ❤️ by Maxime Dupré