Corporate Registry

ISIN codes mapped to a LEI

Changed on

List the ISO 6166 International Securities Identification Numbers (ISINs) mapped to a LEI. Issuers file ISIN-to-LEI mappings with GLEIF to support regulatory reporting (EMIR, MiFID II). Each entry carries the 12-character ISIN and the parent LEI. Returns an empty list when the entity has no reported ISIN mappings.

get/api/v1/gleif/lei-records/{lei}/isins

Request

  • Base URL: https://sugra.ai
  • URL: https://sugra.ai/api/v1/gleif/lei-records/{lei}/isins
  • Auth: API key in header x-api-key

Path parameters

leistring required

20-character LEI whose ISIN mappings are returned.

Query parameters

page_sizeinteger

Entries per page (1 to 200).

page_numberinteger

1-based page number.

Response

ISIN entries mapped to the LEI, with pagination block when the list spans pages.

Example response

{
  "meta": {
    "endpoint": "/api/v1/fred/us/cpi",
    "data_time": "2026-04-16T14:30:00Z",
    "response_time": "2026-04-16T14:30:12Z",
    "provider": "Sugra API v1.0.1",
    "data_age_days": 8.532,
    "source": "sugra_crypto",
    "attribution": "Short interest and Reg SHO daily short volume data is owned by and sourced from FINRA (Financial Industry Regulatory Authority).",
    "fallback_chain": [
      "sugra_crypto",
      "sugra_finance"
    ],
    "stale_since": "2026-09-08T12:00:00Z",
    "period": "2026-Q1",
    "notes": "the UKMTO report behind these counts is dated 2026-08-21 and is 11 days old"
  }
}

Changes

    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

    • info

      added the non-success response with the status