GLEIF LEI Relationship Records Scraper

Extract direct and ultimate parent ownership relationships from the public GLEIF API. Use it to turn LEI codes or company names into compliance-ready parent relationship records with parent LEIs, legal names, relationship validity dates, registration status, corroboration details, and source URLs.

What does GLEIF LEI Relationship Records Scraper do?

This Apify actor queries api.gleif.org/api/v1 and saves one dataset row for each requested Legal Entity Identifier (LEI) and relationship scope.

It can:

• 🔎 Resolve company legal names to GLEIF LEI records.
• 🧭 Fetch direct parent relationship records.
• 🏢 Fetch ultimate parent relationship records.
• ✅ Hydrate parent legal names from parent LEI records.
• 📎 Preserve GLEIF source URLs for audit trails.
• 🧾 Save relationship status, relationship type, validity periods, and registration metadata.
• ⚠️ Save a row when no relationship record is published, so you know the LEI was checked.

Who is it for?

Compliance and KYC teams

Use the actor to map counterparty ownership and parent consolidation relationships before onboarding vendors, clients, issuers, or funds.

AML and sanctions operations

Enrich watchlist or customer files with direct and ultimate parent LEIs so analysts can identify corporate control relationships.

Procurement and third-party risk teams

Batch-check supplier LEIs or legal names and store parent relationship evidence alongside vendor due-diligence documents.

Financial data teams

Create repeatable relationship snapshots from GLEIF for internal master data, entity resolution, or reference-data QA pipelines.

Why use this actor?

GLEIF publishes relationship records through a public JSON API, but operational users often need a repeatable batch workflow, not one API call at a time. This actor handles name resolution, relationship endpoint selection, parent-name hydration, dataset exports, charging, and Apify integrations.

How much does it cost to extract GLEIF LEI parent relationship records?

The actor uses pay-per-event pricing. You pay a small start charge when the run begins and a per-result charge for each relationship row saved.

A relationship row is one subject LEI plus one scope, such as direct parent or ultimate parent. If you enable both scopes, each resolved LEI can produce up to two dataset rows.

Charge event	When it is charged	Price
Run started	Once when a run starts	$0.005
Item extracted — FREE tier	Each saved dataset row	$0.000056183
Item extracted — BRONZE tier	Each saved dataset row	$0.000048855
Item extracted — SILVER tier	Each saved dataset row	$0.000038107
Item extracted — GOLD tier	Each saved dataset row	$0.000029313
Item extracted — PLATINUM tier	Each saved dataset row	$0.000019542
Item extracted — DIAMOND tier	Each saved dataset row	$0.000013679

Example cost on the FREE tier:

Input shape	Expected rows	Estimated actor charge
10 LEIs, direct parent only	up to 10	about $0.0056
10 LEIs, direct + ultimate parent	up to 20	about $0.0061
50 resolved LEIs, direct + ultimate parent	up to 100	about $0.0106

The free Apify plan includes monthly platform credits that can cover many small compliance checks. For example, a 100-row FREE-tier run is roughly one cent in actor charges before normal Apify platform usage costs, so you can test the workflow with the default maxResults before scheduling larger monitoring jobs.

Input options

Field	Type	Description
leis	array	LEI codes to inspect directly.
companyNames	array	Company legal names to resolve through GLEIF before relationship lookup.
maxResolvedLeisPerName	integer	Maximum resolved LEI records per company name.
maxResults	integer	Maximum relationship rows saved to the dataset.
includeDirectParent	boolean	Fetch direct parent relationship records.
includeUltimateParent	boolean	Fetch ultimate parent relationship records.
hydrateParentNames	boolean	Fetch parent LEI records to include parent legal names.

Example input

{
  "leis": ["5493001KJTIIGC8Y1R12", "HWUPKR0MPOU8FGXBT394"],
  "companyNames": ["Apple Inc."],
  "maxResolvedLeisPerName": 5,
  "maxResults": 20,
  "includeDirectParent": true,
  "includeUltimateParent": true,
  "hydrateParentNames": true
}

Output data

Each dataset item contains a relationship lookup result.

Field	Description
inputType	Whether the subject came from a direct LEI or a company-name search.
inputValue	Original LEI or company name.
resolvedLei	Subject LEI used for relationship lookup.
resolvedLegalName	Subject legal name from GLEIF.
resolvedJurisdiction	Subject jurisdiction.
resolvedEntityStatus	Subject entity status.
relationshipScope	direct-parent or ultimate-parent.
relationshipRecordId	GLEIF relationship record ID, when published.
relationshipType	Relationship type such as IS_DIRECTLY_CONSOLIDATED_BY.
relationshipStatus	Relationship status from GLEIF.
parentLei	Parent LEI from the relationship end node.
parentLegalName	Parent legal name when hydration is enabled.
relationshipValidFrom	Relationship validity start.
relationshipValidTo	Relationship validity end, when provided.
relationshipPeriods	GLEIF relationship and accounting periods.
registrationStatus	Relationship registration status.
corroborationLevel	GLEIF corroboration level.
corroborationDocuments	Corroboration document category.
sourceUrl	GLEIF relationship endpoint URL.
subjectRecordUrl	Subject LEI record URL.
parentRecordUrl	Parent LEI record URL.
noRelationshipReason	Explanation when no published relationship record exists.
scrapedAt	Timestamp when the row was saved.

Example output

{
  "inputType": "lei",
  "inputValue": "5493001KJTIIGC8Y1R12",
  "resolvedLei": "5493001KJTIIGC8Y1R12",
  "resolvedLegalName": "Bloomberg Finance L.P.",
  "relationshipScope": "direct-parent",
  "relationshipType": "IS_DIRECTLY_CONSOLIDATED_BY",
  "relationshipStatus": "ACTIVE",
  "parentLei": "549300B56MD0ZC402L06",
  "parentLegalName": "Bloomberg L.P.",
  "registrationStatus": "PUBLISHED",
  "sourceUrl": "https://api.gleif.org/api/v1/lei-records/5493001KJTIIGC8Y1R12/direct-parent-relationship"
}

How to run

1. Open the actor on Apify.
2. Enter one or more LEI codes, company names, or both.
3. Choose direct parent, ultimate parent, or both relationship scopes.
4. Set maxResults to control spend.
5. Run the actor.
6. Download the dataset as JSON, CSV, Excel, XML, or through the Apify API.

Tips for better results

• Use exact legal names when resolving company names.
• Prefer LEI codes when you already have them; this avoids ambiguous company-name matches.
• Keep maxResolvedLeisPerName low for common words such as “Bank”.
• Enable parent-name hydration when a human analyst will read the dataset.
• Disable parent-name hydration for very large monitoring jobs when LEI-only output is enough.
• Use both relationship scopes for ownership mapping and only one scope for focused QA checks.

Monitoring workflow

Run this actor on a schedule to detect parent relationship changes:

1. Store your vendor or counterparty LEIs in the actor input.
2. Schedule a daily, weekly, or monthly run.
3. Export results to your database.
4. Compare relationshipRecordId, relationshipStatus, parentLei, relationshipValidFrom, and lastUpdateDate against the previous run.
5. Alert analysts when a parent LEI or status changes.

KYC workflow

A common KYC workflow is:

1. Resolve the client legal name to candidate LEIs.
2. Review candidate jurisdiction and legal name.
3. Fetch direct and ultimate parent relationships.
4. Store source URLs for evidence.
5. Join parent LEIs to sanctions, PEP, adverse media, or credit-risk workflows.

Procurement workflow

Procurement teams can use the actor to enrich suppliers:

• Add supplier legal names or known LEIs.
• Fetch parent ownership records.
• Attach output to third-party risk files.
• Flag suppliers whose ultimate parent is in a restricted jurisdiction or risk category.

Integrations

You can connect results to:

• Google Sheets for analyst review.
• Snowflake, BigQuery, or PostgreSQL for master data.
• Slack or email alerts for relationship changes.
• CRM and vendor management systems through Apify webhooks.
• Custom KYC applications through the Apify API.

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-relationship-records-scraper').call({
  leis: ['5493001KJTIIGC8Y1R12'],
  includeDirectParent: true,
  includeUltimateParent: true,
  maxResults: 10
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/gleif-lei-relationship-records-scraper').call(run_input={
    'companyNames': ['Apple Inc.'],
    'maxResolvedLeisPerName': 3,
    'maxResults': 6,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~gleif-lei-relationship-records-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"leis":["5493001KJTIIGC8Y1R12"],"maxResults":2}'

MCP integration

Use this actor from Claude Desktop, Claude Code, or other MCP clients through Apify MCP.

MCP server URL:

https://mcp.apify.com/?tools=automation-lab/gleif-lei-relationship-records-scraper

Claude Code setup:

$claude mcp add apify-gleif-lei-relationships --transport http https://mcp.apify.com/?tools=automation-lab/gleif-lei-relationship-records-scraper

Claude Desktop JSON configuration:

{
  "mcpServers": {
    "apify-gleif-lei-relationships": {
      "url": "https://mcp.apify.com/?tools=automation-lab/gleif-lei-relationship-records-scraper"
    }
  }
}

Cursor setup:

1. Open Cursor settings.
2. Go to MCP servers.
3. Add a server named apify-gleif-lei-relationships.
4. Use the HTTP URL above.

VS Code setup:

1. Install an MCP-capable extension or use the built-in MCP configuration if available in your VS Code version.
2. Add an HTTP MCP server with the same Apify MCP URL.
3. Save the configuration and select the actor tool in chat.

Example prompts:

• “Run the GLEIF LEI Relationship Records Scraper for these supplier LEIs and summarize ultimate parents.”
• “Resolve Apple Inc. through GLEIF and list direct and ultimate parent relationship records.”
• “Check whether these counterparties have published parent relationship records and return source URLs.”

Data source

The actor uses the public GLEIF API:

• GET /lei-records/{lei}
• GET /lei-records?filter[entity.legalName]=...
• GET /lei-records/{lei}/direct-parent-relationship
• GET /lei-records/{lei}/ultimate-parent-relationship

Legality

GLEIF data is public reference data. You are responsible for using the output in compliance with your policies, laws, and any GLEIF terms that apply to your use case. The actor does not bypass login, paywalls, or access controls.

FAQ

Is this actor a generic LEI lookup tool?

No. It includes basic subject fields for context, but it is focused on direct and ultimate parent relationship records. Use GLEIF LEI Bulk Lookup when you only need generic LEI profile data.

Does the actor need a GLEIF API key?

No. It uses public GLEIF API endpoints that do not require a login or API key.

Troubleshooting

Why did I get rows with no parent LEI?

GLEIF may not publish a direct or ultimate parent relationship record for every LEI. The actor saves a row with noRelationshipReason so you can prove the LEI and relationship scope were checked.

Why did a company name return multiple LEIs?

Company-name matching can produce multiple entities, branches, jurisdictions, or similarly named records. Use exact LEIs when possible, or review resolvedLegalName and resolvedJurisdiction before using downstream.

Why are parent names missing?

Parent names require hydrateParentNames: true. If hydration is disabled, the actor saves parent LEIs and source URLs without extra parent record lookups.

Related scrapers

• GLEIF LEI Bulk Lookup — generic LEI profile lookup at scale.
• Website Contact Finder — enrich company websites with contact details.
• Company Data Scrapers by Automation Lab — more business data actors.

Changelog

0.1

• Initial release focused on GLEIF direct and ultimate parent relationship records.

Support

If you need a field from the GLEIF API that is not currently exposed, open an Apify issue on the actor page and include a sample LEI plus the target field.