GLEIF LEI Batch Validator - Official API Lookup

Validate Legal Entity Identifiers (LEIs) and company-name searches against the official Global Legal Entity Identifier Foundation (GLEIF) API. The Actor returns structured validation rows for KYB onboarding, vendor due diligence, counterparty master-data cleanup, DORA third-party register checks, and finance workflow automation.

This Actor is intentionally narrow. It does not scrape private sources, does not require cookies or accounts, and does not claim to make a legal compliance decision for you. It turns public GLEIF records into clean Apify Dataset rows with the fields teams usually need before routing a counterparty to approve, review, or manual remediation.

Legal basis: the upstream source is the official public GLEIF API for LEI reference data. That makes the data source suitable for public-record lookup automation, but it does not make any downstream use legally approved. Users remain responsible for their own compliance basis, retention rules, audit process, and decisions made from the data.

What it does

• Looks up exact LEI codes through the official GLEIF API.
• Searches company names through GLEIF full-text search.
• Validates LEI format and MOD 97-10 checksum.
• Reports whether a record exists in GLEIF.
• Reports entity status, registration status, renewal date, legal name, country, legal form, managing LOU, BIC codes, and ISIN codes when present.
• Emits deterministic dataset rows that can be exported to JSON, CSV, Excel, Google Sheets, Make, Zapier, n8n, or an internal onboarding queue.

Quick start

The default input validates one public LEI:

{
  "queries": ["5493001KJTIIGC8Y1R12"],
  "maxResultsPerQuery": 3,
  "maxRecordsTotal": 100,
  "onlyActive": false,
  "timeoutSeconds": 30
}

That first run succeeds without credentials and produces at least one validation row when the GLEIF API is available.

Use cases

• Validate a CSV column of LEIs before client onboarding.
• Check whether counterparties have active entities and issued LEI registrations.
• Add legal names and countries to a vendor or customer master-data table.
• Build DORA or third-party register checks that include LEI validation output.
• Enrich company-name searches with candidate LEI records before a human chooses the correct entity.
• Feed recurring KYB refresh workflows where expired renewals or inactive entities need follow-up.

Input

queries accepts LEI codes or company names. LEI-shaped values use exact lookup and return at most one record. Company names use GLEIF full-text search and return up to maxResultsPerQuery candidate records.

maxResultsPerQuery controls name-search breadth from 1 to 10.

maxRecordsTotal caps one run's total dataset rows and PPE events. Use it to bound spend when a batch contains many company-name searches.

onlyActive asks GLEIF to return active entities with issued registrations for name searches. Exact LEI lookups still return the public record as-is so you can see why it failed a validation check.

timeoutSeconds bounds each official API request.

Example output

Each dataset item includes:

{
  "query": "5493001KJTIIGC8Y1R12",
  "queryType": "lei",
  "matchRank": 1,
  "lei": "5493001KJTIIGC8Y1R12",
  "legalName": "Example Legal Entity",
  "entityStatus": "ACTIVE",
  "registrationStatus": "ISSUED",
  "country": "US",
  "headquartersCountry": "US",
  "category": "GENERAL",
  "legalFormId": "8888",
  "initialRegistrationDate": "2014-01-01T00:00:00.000Z",
  "lastUpdateDate": "2026-01-01T00:00:00.000Z",
  "nextRenewalDate": "2027-01-01T00:00:00.000Z",
  "managingLou": "EVK05KS7XY1DEII3R011",
  "bicCodes": [],
  "isinCodes": [],
  "validation": {
    "formatValid": true,
    "checksumValid": true,
    "existsInGleif": true,
    "activeEntity": true,
    "issuedRegistration": true,
    "renewalCurrent": true
  },
  "sourceUrl": "https://api.gleif.org/api/v1/lei-records/5493001KJTIIGC8Y1R12",
  "fetchedAt": "2026-07-16T00:00:00.000Z"
}

For an LEI-shaped value that does not exist in GLEIF, the Actor emits one factual non-match row with existsInGleif: false. For company-name searches with no matches, it emits no rows because there is no official record to attach to that name.

Pricing

This Actor uses pay per event pricing. The primary event is LEI record. One dataset row equals one charged LEI record event. Exact LEI lookups therefore cost one event when a row is emitted. Company-name searches cost one event per returned candidate record.

Example: 1,000 exact LEI records cost $1.00 at $0.001 per LEI record before any Apify platform minimums or account-level limits.

API example

curl "https://api.apify.com/v2/acts/rtworule~gleif-lei-batch-validator/runs?token=$APIFY_TOKEN" \
  -H "content-type: application/json" \
  -d '{
    "queries": ["5493001KJTIIGC8Y1R12", "Apple Inc"],
    "maxResultsPerQuery": 2,
    "onlyActive": true
  }'

Integrations

• Apify Scheduler for recurring KYB refreshes.
• Webhooks for alerting when a validation batch finishes.
• Google Sheets, Make, Zapier, and n8n through Apify integrations.
• Data warehouses and internal onboarding systems through the Apify Dataset API.
• Portfolio pairing: use Bulk Website Tech Stack Detector for public website enrichment, Public ATS Job Feed Normalizer for hiring signals, and Bulk URL Health Auditor to verify source URLs.

Limitations

• GLEIF data is public reference data, not a legal opinion or compliance approval.
• Name searches can return multiple legal entities. Use matchRank, country, and legal name fields before deciding which entity is correct.
• Parent ownership and relationship expansion are not included in this first version.
• GLEIF API availability and response schemas are upstream dependencies.
• Renewal status is calculated from the returned next renewal date at run time.

FAQ

Is this an official GLEIF product?

No. It is an Apify Actor that uses the official public GLEIF API and links each returned row back to the source record.

Can I upload company names instead of LEI codes?

Yes. Company-name searches use GLEIF full-text search and can return multiple candidate records. Use the country, legal name, and match rank before choosing the correct entity.

Does the Actor decide whether a counterparty is safe?

No. It returns factual validation fields. Your compliance, onboarding, or risk team decides what those fields mean for your workflow.

Why does an invalid LEI still produce a row?

If the input is LEI-shaped, the Actor emits a non-match row so batch jobs can preserve row-level traceability and explain why that identifier failed.

Responsible use

Use this Actor for public legal-entity reference data, KYB data-quality checks, and workflow automation against the official public GLEIF API. Do not treat the output as legal advice, sanctions clearance, credit approval, identity verification, or permission to transact. Keep private customer files and regulated personal data out of support messages and logs. When using the output in compliance workflows, preserve the GLEIF source URL and fetched timestamp so reviewers can reproduce the result.

More tools

Related Actors in this portfolio:

• Bulk URL Health Auditor checks public URL status and redirects.
• Bulk Website Tech Stack Detector enriches public websites with technology signals.
• Public ATS Job Feed Normalizer normalizes public job-board feeds.
• Public RSS, Atom & JSON Feed Normalizer turns public feeds into consistent rows.
• NWS Weather Alert Change Monitor emits official weather-alert lifecycle changes.

Support

Open an issue or contact the Actor maintainer through the Apify Store listing with the run ID, input, and the LEI or company name that behaved unexpectedly. Do not send private customer records, secrets, or regulated personal data in support messages.