How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
GLEIF

GLEIF LEI Records API

Operations on Legal Entity Identifier records

Documentation Provider Profile APIs.io OpenAPI GitHub

GLEIF LEI Records API is one of 5 APIs that GLEIF publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include LEI Records. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 7 operations across 7 paths, and defines 16 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://api.gleif.org/api/v1.

7 operations 7 paths 16 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.gleif.org/api/v1
Contact
GLEIF
License
Creative Commons Zero (CC0)
Resource Areas
1

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. Each is listed below with its method, path, parameters, and response codes.

LEI Records 7

Operations on Legal Entity Identifier records

GET
/lei-records
List or search LEI records
listLeiRecords 10 params → 200400
GET
/lei-records/{lei}
Get a single LEI record
getLeiRecord 1 param → 200404
GET
/lei-records/{lei}/direct-children
Get direct children of a legal entity
getLeiRecordDirectChildren 3 params → 200404
GET
/lei-records/{lei}/ultimate-children
Get ultimate children of a legal entity
getLeiRecordUltimateChildren 3 params → 200404
GET
/lei-records/{lei}/managing-lou
Get the managing LEI Issuer for a record
getLeiRecordManagingLou 1 param → 200404
GET
/lei-records/{lei}/lei-issuer
Get the LEI Issuer for a record
getLeiRecordLeiIssuer 1 param → 200404
GET
/lei-records/{lei}/field-modifications
Get field modification history for a LEI record
getLeiRecordFieldModifications 3 params → 200404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Entity (19 properties), Registration (9 properties), LeiRecordAttributes (9 properties), Address (9 properties). Each schema is shown below with its type and property counts.

LegalName
object
2 properties
Registration
object
9 properties
LeiRecordListResponse
object
3 properties
LeiRecordRelationships
object
3 properties
LeiRecordSingleResponse
object
2 properties
LeiIssuerSingleResponse
object
2 properties
LeiIssuer
object
5 properties
PaginationMeta
object
2 properties
ErrorResponse
object
1 property
PaginationLinks
object
3 properties
GoldenCopyMeta
object
1 property
Entity
object
19 properties
PaginationInfo
object
6 properties
LeiRecordAttributes
object
9 properties
LeiRecord
object
5 properties
Address
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gleif-lei-records-api-openapi.yml Raw ↑

Other APIs GLEIF publishes across the network.

GLEIF Corporate Relationships API
AE Profile APIs.io
GLEIF LEI Issuers API
AE Profile APIs.io
GLEIF Reference Data API
AE Profile APIs.io
GLEIF Search API
AE Profile APIs.io
#LEI Records
← Back to G APIs
API Details
ID
gleif:gleif-lei-records-api
Base URL
https://api.gleif.org/api/v1
Docs
https://www.gleif.org/en/lei-data/gleif-api
Provider
GLEIF
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=gleif-lei-records-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/gleif-lei-records-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of GLEIF LEI Records API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.