GLEIF LEI ↔ 法人番号 bridge
GLEIF LEI (Legal Entity Identifier) <-> 法人番号 bridge (jpverify.lei; the method and the measured coverage are summarised in /llms.txt and below). Provide exactly one of corporate_number=/t_number= (-> the corporation's LEI, if GLEIF's golden copy maps one) or lei= (-> the 法人番号 it maps to, if any). Honest scope: only a measured ~20% of JP-jurisdiction LEIs have a number-based or exact-name join to a 法人番号 today (the join is by the 法人番号 GLEIF records as the registration authority id, else by an exact normalised legal name — nothing fuzzy) — a null lei is the ordinary, correctly-reported case, not a lookup failure. When more than one LEI maps to the same 法人番号, the chosen one prefers an ISSUED registration then the most recently updated (see lei_candidates for the total). GLEIF publishes this data under CC0 1.0 (no attribution required); a response also carrying houjin-bangou data still owes the NTA attribution for that half. Where the bridge is not configured this returns 503.
Request
- Base URL: https://jp-verify.obolpay.xyz
- URL: https://jp-verify.obolpay.xyz/v1/lei
- Auth: one of:
- none
- API key in header X-API-Key
Query parameters
a 13-digit 法人番号 (Corporate Number, check-digit validated) — look up its LEI
alternative input: T + 13-digit 法人番号
alternative input: a 20-character LEI (ISO 17442) — look up the 法人番号 it maps to
Headers
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.