Japan EDINET Disclosure Filings (Official API) avatar

Japan EDINET Disclosure Filings (Official API)

Pricing

from $2.00 / 1,000 record scrapeds

Go to Apify Store
Japan EDINET Disclosure Filings (Official API)

Japan EDINET Disclosure Filings (Official API)

List Japan's securities-disclosure filings (yuho, quarterly, large-shareholding, etc.) via the official EDINET API v2: by date or date range, filterable by company or document type. Bibliographic metadata only, corporations/funds only. Bring your own EDINET API key. Unofficial.

Pricing

from $2.00 / 1,000 record scrapeds

Rating

0.0

(0)

Developer

JP Open Data

JP Open Data

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Categories

Share

Japan EDINET Disclosure Filings (Official API v2)

Japan's securities-disclosure filings — annual reports (yuho), quarterly reports, extraordinary reports, large-shareholding reports and more — straight from the official EDINET API of the Financial Services Agency, as clean English-schema JSON.

This Actor is a thin client of the official EDINET API v2 (api.edinet-fsa.go.jp) run by Japan's 金融庁 (Financial Services Agency). It lists the disclosure documents submitted to EDINET — by a single date or across a date range — and returns their bibliographic metadata: document ID, filer (company/fund), securities code, corporate number, document type (resolved to a name), reporting period, submission time, and content flags. Think of it as an English, scriptable index over Japan's equivalent of the SEC's EDGAR filing feed.

Unofficial tool. Not affiliated with or endorsed by the Financial Services Agency of Japan. Source: 金融庁 EDINET. EDINET content is provided under the 公共データ利用規約(第1.0版)(PDL1.0), which permits reproduction, adaptation, and commercial use with attribution — the required 出典 statement 「出典:金融庁 EDINET」 is embedded in the license string of every output record.


Quick start — verified input

Copy, paste, replace the key, run (verified against mock API fixtures in npm test; a live run needs your own EDINET API key — see the next section for how to get one in two minutes):

{
"apiKey": "<your key>",
"mode": "list",
"date": "2026-08-25",
"maxItems": 100
}

Get the key at https://disclosure2.edinet-fsa.go.jp/ (free) → ログイン (create an account) → API キー発行 → copy the Subscription-Key. For a window of days use {"mode": "range", "dateFrom": "2026-08-01", "dateTo": "2026-08-31"} (max 62 days).

Bring your own EDINET API key

Since 2024, the EDINET API requires an API key (a Subscription-Key). This Actor does not bundle a shared key — it never has one. You pass your own free EDINET API key in the apiKey input (stored as a secret). Every request runs under your own registration, and EDINET's access limits apply to you.

Get a key (free): open the EDINET viewer site → ログイン → create an account → API キー発行. Portal: https://disclosure2.edinet-fsa.go.jp/

Metadata only — no document bodies

This Actor calls only the 書類一覧API (documents.json), which returns the list of filings with their metadata. It deliberately never calls the 書類取得API (documents/{docID}), so it never downloads XBRL, PDF, or CSV document bodies — only the bibliographic index. The flags (xbrlFlag, pdfFlag, csvFlag, englishDocFlag) tell you which bodies exist, so you can fetch them yourself with your key if you need them.

Corporations and funds only (privacy by design)

Large-shareholding reports (大量保有報告書) can be filed by individuals, whose filer name is a personal name. This Actor drops every filing whose submitter is a natural person — detected by the absence of a 法人番号 (Corporate Number / JCN). Only filings from corporations and funds are emitted, so no individual's name ever appears in the output. (This conservatively also drops the rare corporate filer that carries no JCN — privacy is prioritised over completeness.)

Modes

  • list — every filing for one submission date (YYYY-MM-DD). One API request.
  • range — filings across dateFrom..dateTo (one request per day, span capped at 62 days). Best for tracking one company (secCode / edinetCode) or one document type over time.

Input example

{
"apiKey": "<your key>",
"mode": "list",
"date": "2026-08-25",
"docTypeCode": "120,140",
"maxItems": 100
}
  • apiKeyrequired: your own EDINET API key (secret).
  • date — required in list mode (YYYY-MM-DD; 2026/08/25 and 20260825 are tolerated). dateFrom/dateTo — required in range mode; if you pass only these two, the Actor switches to range for you.
  • docTypeCode — optional comma-separated 3-digit type codes. Common ones: 120 有価証券報告書 (annual / yuho), 140 四半期報告書 (quarterly), 160 半期報告書 (semi-annual), 180 臨時報告書 (extraordinary), 350 大量保有報告書 (large-shareholding).
  • secCode — optional 4-digit ticker (e.g. 7203; 7203.T tolerated) or full 5-digit EDINET securities code.
  • edinetCode — optional filer EDINET code (E + 5 digits), for non-listed filers and funds.
  • maxItems / maxApiRequests — output and request caps (defaults 1000 / 40).

Values are validated before the first request; an invalid value fails the run immediately with a message that shows the expected format.

Common input mistakes

MistakeCorrect
"apiKey": "<your key>" left as is / emptypaste your real Subscription-Key (the run fails immediately with a link to get one)
"date": "25/08/2026" / "Aug 25""2026-08-25"
"date" on a Saturday/Sunday/holidaya Japanese business day — weekends have no filings (0 items)
{"mode": "list", "dateFrom": …, "dateTo": …}"mode": "range" (the Actor switches for you when mode is omitted)
"dateFrom": "2025-01-01", "dateTo": "2025-12-31"at most 62 days per run — split the year into windows
"docTypeCode": "yuho"the code: "120"
"secCode": "TM" / "Toyota"the ticker "7203" or "edinetCode": "E02144"

Empty results?

A run that finds nothing completes with 0 items and a warning in the log (not a failure). Typical causes: a non-business day (no filings on weekends / Japanese holidays), a docTypeCode that no filer submitted that day (e.g. 120 yuho outside the June peak), or a secCode/edinetCode filter for a company that did not file in the window — annual reports come once a year, so use range over the filing season. EDINET answers HTTP 401 for a bad key — that fails the run visibly.

Sample output (dataset item)

{
"seqNumber": 1,
"docId": "S100ABCD",
"edinetCode": "E02144",
"secCode": "72030",
"jcn": "1180301018771",
"filerName": "トヨタ自動車株式会社",
"fundCode": null,
"ordinanceCode": "010",
"formCode": "030000",
"docTypeCode": "120",
"docTypeName": "有価証券報告書",
"periodStart": "2025-04-01",
"periodEnd": "2026-03-31",
"submitDateTime": "2026-08-25 15:04",
"docDescription": "有価証券報告書-第122期(令和7年4月1日-令和8年3月31日)",
"issuerEdinetCode": null,
"xbrlFlag": "1",
"pdfFlag": "1",
"csvFlag": "1",
"englishDocFlag": "1",
"legalStatus": "1",
"source": "金融庁 EDINET(有価証券報告書等の開示書類に関する電子開示システム)API / EDINET, Financial Services Agency of Japan",
"sourceUrl": "https://disclosure2.edinet-fsa.go.jp/",
"license": "出典:金融庁 EDINET(https://disclosure2.edinet-fsa.go.jp/)。公共データ利用規約(第1.0版)(PDL1.0)に準拠し出典表示のうえ複製・翻案・商用利用可。Unofficial EDINET API v2 client …",
"retrievedAt": "2026-08-26T09:12:44Z"
}

Flags are the source's own "1"/"0" strings; null fields are values EDINET did not publish for that filing (e.g. periodStart/periodEnd only appear for period-based reports), passed through honestly.

Pricing

Pay per result — see the pricing tab. One list day is a handful to a few hundred filings; a range panel of one company across a quarter is a few rows.

FAQ

Where does the data come from? The official EDINET API v2 (api.edinet-fsa.go.jp/api/v2/documents.json) operated by Japan's Financial Services Agency. Retrieved via the API — the EDINET terms forbid scraping but expressly permit API access, which is what this Actor uses.

Is this an official government service? No. Unofficial, independently built and maintained. EDINET content is reusable commercially under PDL1.0 with attribution; the required 出典 statement is embedded in every record.

Do I need an API key? Yes — your own free EDINET API key. This Actor never ships a shared key. See "Bring your own EDINET API key" above.

How fresh is the data? Real-time to EDINET: filings appear the moment they are accepted. EDINET keeps roughly the last 10 years of filings queryable by date. Non-business days have no filings.

Does it download the actual reports? No. Bibliographic metadata only. The xbrlFlag / pdfFlag / csvFlag fields tell you which document bodies exist so you can retrieve them yourself.

Any privacy concerns? None by construction: individual (natural-person) filers are dropped, so only corporation/fund filing metadata is emitted. Automated tests assert no individual name, phone, e-mail, or address survives, and full source attribution on every record.

What about server load? One polite request per date, ≥1.5 s apart, exponential backoff on 429/5xx, hard request budget, no rate-limit evasion. range is capped at 62 days per run. The EDINET terms forbid 「短時間における大量のアクセス」 — honoured in code.

Search terms this Actor answers

edinet api actor · japan securities filings · japan financial disclosure english · yuho data · japanese annual report data · EDINET disclosure documents API · japan large shareholding reports · japan quarterly report data · japan company filings by securities code · FSA Japan disclosure feed

More Japan public-data Actors by the same developer

  • Japan e-Stat Official Statistics — the official statistics portal API (getStatsList / getStatsData).
  • Japan Trade Statistics — monthly customs import/export by HS code and country.
  • Japan Government Tenders & Awards — tender notices and award results from kkj.go.jp.
  • Japan Government Subsidies & Grants — open subsidy calls from the official jGrants API.
  • Japan Financial Licenses & Registrations — FSA-licensed banks, securities firms, and crypto exchanges.

Data source: 金融庁 EDINET — https://disclosure2.edinet-fsa.go.jp/ . API: https://api.edinet-fsa.go.jp/api/v2 . Terms: https://disclosure2dl.edinet-fsa.go.jp/guide/static/disclosure/WZEK0030.html (PDL1.0 — commercial use permitted, attribution required — embedded in every record).