Verifex
Create an API key

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.

Get API key Read current documentation

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.

GLEIF/LEI data currently informs KYB, UBO, and entity-screening workflows. The example below describes an intended standalone lookup shape, not a live public endpoint.

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.

bash
Illustrative planned request — not live

curl -X GET https://api.verifex.dev/v1/gleif/lookup \
  -H "Authorization: Bearer vfx_your_api_key" \
  -G -d "lei=5493001KJTIIGC8Y1R12"
json
{
  "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
}
Important limitation: GLEIF coverage depends on whether an entity has voluntarily obtained an LEI. Many small businesses and non-financial entities do not have LEIs. GLEIF data is sourced from publicly available records and may not reflect the latest corporate changes. Always verify critical corporate data against official registries where required by policy.

Explore the full platform

UBO Analysis

Ownership-chain risk calculations and OFAC 50% Rule support.

Learn more

KYB Dossiers

Manual-enhanced company verification for Turkey and Azerbaijan.

Learn more

Sanctions Screening

Global sanctions and watchlist screening with structured confidence.

Learn more

KYB API

Company verification, ownership analysis, and compliance dossiers. Automated coverage is UK Companies House (beta).

Learn more

Start with entity screening. Add context where it is available.

Start with the current screening workflow, then assess GLEIF/LEI context in the relevant entity and ownership process.

Start screening UBO Analysis