Disclosed major shareholders of an EDINET securities-report filer
The 「大株主の状況」 table a 有価証券報告書 / 半期報告書 filer publishes on EDINET, keyed by 法人番号 — facts as filed, never a determination.
Honest scope. What is published about a company's owners depends on its legal form. A 株式会社's 株主名簿 is inspectable by its own shareholders and creditors, on a stated reason (会社法 125条2項) — the route the Act gives an outsider is a 親会社社員's, with a court's permission (125条4項) — and its shareholders are not among the registered items (会社法 911条3項). A 持分会社 keeps no 株主名簿, and the members who execute its business and represent it ARE registered items (会社法 914条六・七 for a 合同会社), a public record this service does not carry. Major-shareholder facts of the kind this endpoint serves therefore exist only for corporations that file a 有価証券報告書 or 半期報告書 — MEASURED 4,918 code-list rows / 4,917 distinct 法人番号 on the 2026-09-18 list, 0.098 % of 5,009,012 active corporations. For any other 法人番号 this endpoint answers with a structured no-public-disclosure certificate (status: no_public_disclosure) that cites those provisions — each with the legal form it holds for — and the code-list date it was checked against; it never says the corporation has no shareholders.
Privacy (mode A). A holder is named only when it is positively an organisation — resolved to exactly one active 法人番号 by exact name match, or carrying an organisation marker from a pinned table. Every other holder is served as unresolved with rank, share count and ratio only; its published name and the address column of every row are discarded in memory at parse time and are never stored, logged, signed or served. A row whose name cell was nil or empty in the filing is unknown — likewise nameless, and withheld by the same gate. Per-ROW figures for holders served without a name go only to a key whose onboarding recorded the Terms Art. 7(3) representation while the operator's counsel record is in place; every other caller — and always the sandbox — receives them in aggregate (holders_form: "aggregate", with the reason beside it).
1 unit on every tier including the sandbox; a 400, a 404 (doc_id not retained) and a 503 (no sidecar) are free. The 404 body is {error, corporate_number, hint} — it does NOT carry filings[], which is part of the metered answer.
Request
- Base URL: https://jp-verify.obolpay.xyz
- URL: https://jp-verify.obolpay.xyz/v1/shareholders
- Auth: one of:
- none
- API key in header X-API-Key
Query parameters
a 13-digit 法人番号 (Corporate Number, check-digit validated)
alternative input: T + 13-digit 法人番号
YYYY-MM-DD — select the latest retained filing submitted on or before this date (what a reader could have seen then); the holdings themselves are as of the filing's own basis_date
select one retained filing by its EDINET docID (書類管理番号); a docID this deployment does not retain is a free 404 that carries no document index
Ed25519-signed record (Growth/Reseller keys)
Headers
Response
The filer's 「大株主の状況」 table, or a structured statement of why none is published. Both generated examples are real responses of this code on a synthetic sidecar.
Changes
No recorded changes to this operation across all 1 revision of this API.