GLEIF / LEI Context for Entity-Screening Workflows
Understand how GLEIF/LEI reference data can inform entity and ownership workflows while keeping company-reference data distinct from compliance screening results.
How GLEIF / LEI context is positioned today.
GLEIF / LEI reference context
GLEIF/LEI data can provide entity identifiers and corporate context within supported Verifex workflows.
Reported ownership context
Where available in source data, parent relationships can inform entity and ownership analysis; they are not a substitute for independent verification.
Entity identity context
Legal name, jurisdiction, and entity attributes can help a team distinguish entity-reference data from sanctions or PEP screening results.
Separate screening workflow
Entity-reference data can inform a screening workflow, but an LEI record is not sanctions status and does not certify an entity as clear.
Corporate structure research
Entity attributes and reported relationships can provide context for a team’s own corporate-structure research and matching review.
Standalone endpoint is roadmap
Verifex does not currently offer a public standalone /v1/gleif/lookup endpoint. The examples below describe an intended future shape only.
Separate current workflows from the planned standalone lookup.
Roadmap: today, GLEIF/LEI data powers KYB, UBO, and entity screening (POST /v1/screen, POST /v1/ubo/calculate). A standalone /v1/gleif/lookup endpoint is planned. The example below shows its intended shape.
Illustrative planned request: not live
curl -X GET https://api.verifex.tech/v1/gleif/lookup \
-H "Authorization: Bearer vfx_your_api_key" \
-G -d "lei=5493001KJTIIGC8Y1R12"{
"lei": "5493001KJTIIGC8Y1R12",
"legal_name": "ACME GLOBAL HOLDINGS LIMITED",
"jurisdiction": "GB",
"legal_form": "Limited Company",
"registration_status": "ACTIVE",
"registration_date": "2015-03-12",
"direct_parent": {
"lei": "549300ABCD1234567890",
"legal_name": "ACME PARENT PLC"
},
"ultimate_parent": {
"lei": "549300XYZ9876543210",
"legal_name": "ULTIMATE ACME GROUP"
},
"queried_at": "2026-05-11T09:00:00.000Z",
"source": "GLEIF_GOLDEN_COPY",
"source_freshness_days": 2
}Frequently Asked Questions
What is a Legal Entity Identifier (LEI)?
An LEI is a 20-character alphanumeric code based on the ISO 17442 standard. It provides a unique global identifier for legal entities participating in financial transactions. GLEIF maintains the global LEI database.
Does Verifex provide a public standalone GLEIF lookup API?
No. The standalone /v1/gleif/lookup endpoint shown on this page is roadmap-only. The current public API and documentation should not be read as offering that endpoint.
How is GLEIF / LEI data used today?
GLEIF/LEI reference data can inform Verifex KYB, UBO, and entity-screening workflows. It remains distinct from the screening result itself, and availability depends on the relevant workflow and source data.
What if an entity does not have an LEI?
Not all entities have LEIs. You can screen by name using the standard /v1/screen endpoint regardless of whether an LEI exists. LEI coverage is strongest for financial entities and large corporates.
How is LEI data used in KYB workflows?
LEI data provides a verified legal name, jurisdiction, registration status, and corporate hierarchy. KYB teams use this to confirm entity identity, verify active registration, and understand parent-subsidiary relationships before applying sanctions screening or onboarding decisions.
Can GLEIF data replace sanctions screening?
No. GLEIF provides corporate identity and structure data, not sanctions status. A valid LEI does not mean an entity is not sanctioned. GLEIF data complements sanctions screening by providing verified entity details that improve matching accuracy.
Explore the full platform
UBO Analysis
Ownership-chain risk calculations and OFAC 50% Rule support.
KYB Dossiers
Manual-enhanced company verification for Turkey and Azerbaijan.
Sanctions Screening
Global sanctions and watchlist screening with structured confidence.
KYB API
Company verification, ownership analysis, and compliance dossiers. Automated coverage is UK Companies House (beta).