GLEIF LEI Bulk Lookup

Bulk lookup Legal Entity Identifiers (LEIs) from the official GLEIF API. Enter company names, legal names, or LEI codes and export normalized compliance-ready entity records.

What does GLEIF LEI Bulk Lookup do?

GLEIF LEI Bulk Lookup turns a list of companies or LEI codes into structured Legal Entity Identifier records. It uses the public GLEIF JSON API directly, so runs are fast, lightweight, and do not need a browser, login, or proxy.

Use it when you need to enrich vendors, counterparties, customers, issuers, or portfolio companies with verified LEI metadata.

Who is it for?

• 🏦 KYB and KYC operations teams checking legal entity status.
• 🛡️ Compliance analysts validating counterparties before onboarding.
• 📦 Procurement and vendor-risk teams enriching supplier lists.
• 💳 Fintech onboarding teams matching company names to LEIs.
• 📊 CRM and data teams adding LEI fields to account records.
• ⚖️ Legal and risk teams checking registration renewal and conformity.

Why use it?

Manual GLEIF lookups are fine for one company. They are painful for a spreadsheet. This actor accepts bulk input, keeps the source query on every row, normalizes nested GLEIF data into exportable fields, and charges only for records it saves.

What data can I extract?

Field	Description
query	Original company name or LEI input.
queryType	lei for exact LEI lookups or text for full-text searches.
rank	Result rank within the query.
lei	Legal Entity Identifier.
legalName	Official legal name from GLEIF.
otherNames	Trading names, former names, or transliterations when available.
jurisdiction	Legal jurisdiction code.
entityStatus	Entity status such as ACTIVE.
registrationStatus	LEI registration status such as ISSUED or LAPSED.
conformityFlag	GLEIF conformity flag.
registeredAs	Local registry identifier.
legalAddress	Structured legal address object.
headquartersAddress	Structured headquarters address object.
bic, mic, ocid, qcc, spglobal	Additional identifiers when GLEIF provides them.
gleifUrl	Official GLEIF API URL for the record.

How much does it cost to look up LEIs in bulk?

The actor uses pay-per-event pricing:

• A small one-time start event per run.
• A per-record event for each LEI record written to the dataset.

Because the actor calls the official API directly and does not use proxies or browsers, costs are designed to stay low for recurring enrichment jobs.

How to use it

1. Open the actor on Apify.
2. Paste company names or LEI codes into Company names or LEIs.
3. Set Max results per name query.
4. Optionally filter by country, active entities, or conforming records.
5. Run the actor.
6. Download the dataset as JSON, CSV, Excel, or connect it to your workflow.

Input example

{
  "queries": [
    "Apple Inc",
    "Microsoft Corporation",
    "529900T8BM49AURSDO55"
  ],
  "maxResultsPerQuery": 10,
  "onlyActive": true,
  "onlyConforming": false,
  "includeRelationships": true
}

Output example

{
  "query": "529900T8BM49AURSDO55",
  "queryType": "lei",
  "rank": 1,
  "lei": "529900T8BM49AURSDO55",
  "legalName": "Ubisecure Oy",
  "jurisdiction": "FI",
  "entityStatus": "ACTIVE",
  "registrationStatus": "ISSUED",
  "conformityFlag": "CONFORMING",
  "registeredAs": "1748721-4",
  "nextRenewalDate": "2027-06-28T18:34:06Z",
  "gleifUrl": "https://api.gleif.org/api/v1/lei-records/529900T8BM49AURSDO55"
}

Company-name matching

For ordinary company names, the actor uses GLEIF full-text search. Each saved row includes the original query and result rank so you can review match quality in downstream systems.

Exact LEI matching

For 20-character LEI-shaped inputs, the actor uses the exact LEI endpoint. Invalid or unknown LEIs return no rows instead of creating noisy placeholder records.

Country filters

Use countryCodes to restrict results to ISO alpha-2 country codes. The actor checks the legal jurisdiction prefix plus legal and headquarters address country fields.

Active and conforming filters

Use onlyActive for entity status checks and onlyConforming for GLEIF conformity screening. These filters are useful for compliance teams that only want immediately actionable records.

Parent relationship links

Enable includeRelationships to add direct and ultimate parent relationship URLs where GLEIF exposes them. The actor records links instead of expanding nested parent data by default, keeping bulk runs fast and inexpensive.

Tips for best results

• Use exact legal names when possible.
• Combine company name and country filter for common names.
• Set maxResultsPerQuery higher for ambiguous names and lower for clean internal master data.
• Keep onlyActive off during discovery if you need to find historical or lapsed records.
• Keep the query column in exports so reviewers can trace every row back to the source list.

Integrations

Use this actor in:

• 🧾 Vendor onboarding workflows before supplier approval.
• 🏦 Customer due diligence and KYB queues.
• 📈 Portfolio monitoring dashboards.
• 🧹 CRM enrichment and account deduplication flows.
• 📤 Apify integrations that send dataset rows to Google Sheets, S3, BigQuery, or webhooks.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/gleif-lei-bulk-lookup').call({
  queries: ['Apple Inc', '529900T8BM49AURSDO55'],
  maxResultsPerQuery: 5,
  onlyActive: true
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/gleif-lei-bulk-lookup').call(run_input={
    'queries': ['Apple Inc', '529900T8BM49AURSDO55'],
    'maxResultsPerQuery': 5,
    'onlyActive': True,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~gleif-lei-bulk-lookup/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"queries":["Apple Inc","529900T8BM49AURSDO55"],"maxResultsPerQuery":5}'

Use with MCP and AI agents

You can connect this actor to AI tools through Apify MCP. Use a scoped MCP URL such as:

https://mcp.apify.com/?tools=automation-lab/gleif-lei-bulk-lookup

Example prompts:

• "Look up LEI records for these counterparties and summarize which ones are active."
• "Find conforming LEI records for this supplier list and flag lapsed registrations."
• "Enrich these company names with LEI, jurisdiction, and next renewal date."

Data source

The source is the Global Legal Entity Identifier Foundation (GLEIF) public API. GLEIF provides official LEI reference data and relationship links. This actor is not affiliated with or endorsed by GLEIF.

Legality and compliance

This actor retrieves public business registry metadata from a public API. You are responsible for using the output in accordance with your compliance program, local regulations, and data governance rules.

FAQ and troubleshooting

Why did a company name return many rows?

GLEIF full-text search can match legal names, addresses, and related fields. Use country filters, exact legal names, or exact LEI codes for tighter matching.

Why did an LEI return no row?

The LEI may be invalid, unknown to GLEIF, or mistyped. Exact LEI inputs use the /lei-records/{lei} endpoint and do not emit placeholder rows for 404 responses.

Why are parent fields empty?

Not every record has direct or ultimate parent relationship links. Enable includeRelationships to include available URLs.

Related Apify actors

• https://apify.com/automation-lab/company-website-finder
• https://apify.com/automation-lab/website-contact-finder
• https://apify.com/automation-lab/domain-to-company-name

Changelog

• 0.1.0 — Initial version with bulk name/LEI lookup, normalized output, filters, and optional relationship links.

Support

If you need additional fields from the GLEIF API, share an example LEI and the field you need. The actor is designed to be extended without changing the core bulk workflow.

Field quick reference

• query is included as a stable export column for spreadsheet and database workflows.
• queryType is included as a stable export column for spreadsheet and database workflows.
• rank is included as a stable export column for spreadsheet and database workflows.
• lei is included as a stable export column for spreadsheet and database workflows.
• legalName is included as a stable export column for spreadsheet and database workflows.
• otherNames is included as a stable export column for spreadsheet and database workflows.
• jurisdiction is included as a stable export column for spreadsheet and database workflows.
• entityCategory is included as a stable export column for spreadsheet and database workflows.
• entityStatus is included as a stable export column for spreadsheet and database workflows.
• registrationStatus is included as a stable export column for spreadsheet and database workflows.
• conformityFlag is included as a stable export column for spreadsheet and database workflows.
• legalFormId is included as a stable export column for spreadsheet and database workflows.
• registeredAtId is included as a stable export column for spreadsheet and database workflows.
• registeredAs is included as a stable export column for spreadsheet and database workflows.
• managingLou is included as a stable export column for spreadsheet and database workflows.
• initialRegistrationDate is included as a stable export column for spreadsheet and database workflows.
• lastUpdateDate is included as a stable export column for spreadsheet and database workflows.
• nextRenewalDate is included as a stable export column for spreadsheet and database workflows.
• legalAddress is included as a stable export column for spreadsheet and database workflows.
• headquartersAddress is included as a stable export column for spreadsheet and database workflows.
• bic is included as a stable export column for spreadsheet and database workflows.
• mic is included as a stable export column for spreadsheet and database workflows.
• ocid is included as a stable export column for spreadsheet and database workflows.
• qcc is included as a stable export column for spreadsheet and database workflows.
• spglobal is included as a stable export column for spreadsheet and database workflows.
• directParentLeiUrl is included as a stable export column for spreadsheet and database workflows.
• directParentRelationshipUrl is included as a stable export column for spreadsheet and database workflows.
• ultimateParentLeiUrl is included as a stable export column for spreadsheet and database workflows.
• ultimateParentRelationshipUrl is included as a stable export column for spreadsheet and database workflows.
• gleifUrl is included as a stable export column for spreadsheet and database workflows.
• fetchedAt is included as a stable export column for spreadsheet and database workflows.