Global LEI Registry Lookup API

Search public GLEIF records by LEI or company name and return normalized legal-entity status, identifiers, addresses, registration data, confidence, and official source links. Global enrichment, onboarding, KYC support, due-diligence, and data-integration teams. Resolve company names or LEIs into normalized, source-linked legal-entity records for a one-time lookup or scheduled workflow.

What it does

This Actor normalizes the supported evidence into a default Apify dataset and keeps the original source reference with each buyer-visible result. Its buyer-value event is lookup-result; it uses Apify pay-per-event pricing, so inspect the current Pricing tab and begin with a small validation run.

Supported sources and boundary

• GLEIF LEI API for public global legal-entity records

Only the sources and buyer inputs listed above are supported. The Actor does not bypass login, CAPTCHA, paywalls, robots restrictions, private APIs, or any other access control. It is an independent tool and is not affiliated with the named source platforms or authorities.

Inputs

• buyerQuery — An LEI or company-name lookup query.
• watchlistTerms — Company names or LEIs to resolve.
• maxItems — Maximum lookup results to return.

Existing saved-task fields remain accepted for backward compatibility. Use Apify's maximum run-charge limit for any live validation run.

Buyer-ready output

• lei
• legalName
• entityStatus
• registrationStatus
• legalAddress
• registrationData
• confidence
• sourceUrl

Every output preserves source provenance where the input or public source provides it. Unsupported sources return an explicit boundary error instead of an invented record.

First run

{
    "sourceMode": "sample",
    "buyerQuery": "LEI lookup by company name",
    "watchlistTerms": [
        "example legal entity"
    ],
    "maxItems": 1
}

The bundled first-run example is a labelled deterministic demonstration, not proof of current live coverage:

{
    "evidenceType": "deterministic_demo",
    "lei": "52990000000000000000",
    "legalName": "Illustrative Legal Entity",
    "entityStatus": "ACTIVE"
}

API, dataset, schedules, and webhooks

Use the Apify API or default dataset for programmatic retrieval. Save an input as an Apify task to schedule recurring runs. If the current input schema exposes webhookUrl, it can notify a buyer-controlled endpoint after a completed run; otherwise use Apify webhooks for the task or run.

Common use cases

• Build a source-linked internal review queue.
• Compare repeated signals across a buyer watchlist.
• Export normalized JSON or CSV for an approved downstream workflow.

Limitations and responsible use

This global product is distinct from the German monitoring Actor. It does not provide licence lookup; confirm critical decisions against the official GLEIF record.

Support

Include the Actor run ID, the input field names (not secrets), an example source URL when authorized, and the observed output field when contacting Zentra support. Check the current Pricing and API tabs before production-scale runs.