Workflow validation
LEI Entity Lookup API
A buyer-intent page for fintech, marketplace, supplier-risk, and data-ops teams that want a lightweight API or CSV feed for LEI records, company-register identity fields, and entity status changes.
GET /v1/entities/identity/lookup?name=sample%20holdings&jurisdiction=GB
{
"data": [
{
"lei": "00000000000000000123",
"legalName": "Sample Holdings Ltd",
"jurisdiction": "GB",
"registrationStatus": "ISSUED",
"matchedName": "sample holdings",
"sourceUrl": "https://api.gleif.org/api/v1/lei-records/00000000000000000123"
}
],
"meta": { "sampleOnly": true, "workflow": "lei-entity-lookup-api" }
}
Likely Buyers
This page is only a demand test. Build starts after tracked workflow intent beats the broader market pages.
- Fintech and marketplace teams building counterparty record checks.
- Supplier-risk teams monitoring legal-name or status changes.
- Data operations teams maintaining entity master records.
Signals To Watch
These events decide whether this workflow deserves implementation.
- Request clicks from LEI API, company lookup, and entity identity keywords.
- Legal entity sample CSV downloads.
- Demo clicks from teams comparing response shape before a build.
Smallest Build
If this page crosses a gate, the first implementation should stay this narrow.
- GLEIF-first LEI lookup and change feed with source URLs.
- One regional company-register enrichment path before broad global scope.
- No KYC/KYB decisioning, UBO inference, sanctions screening, or private data enrichment.