Skip to main content
JP FR / API · Japan

Build on Japan filings programmatically.

A typed REST API over 259,076 filings from 3,897 Japanese listed companies — JSON metadata, Markdown body, and original PDF. Webhooks on every new release.

Public-company filings in Japan are supervised by Financial Services Agency of Japan (FSA). Reporting follows JGAAP / Japan-IFRS / IFRS / US GAAP (issuer choice). Filings are most commonly published in Japanese and English. Major issuers are listed on Nikkei 225, TOPIX and TOPIX Core 30. March year-end common (≈70% of issuers).

Programmatic access to Japanese filings — EDINET, TDnet, and cross-border consistency

The FinancialReports API delivers Japan's dual-channel regulatory disclosure stream — EDINET statutory reports and TDnet ad-hoc announcements — through a single REST surface authenticated with one x-api-key header, the same key that works across every covered market from Frankfurt to Seoul. A Japan-only integration is a one-parameter filter (?country=JP) on the global filings endpoint; there is no separate JPX or FSA endpoint, no separate API key, and no per-market billing tier. The same endpoint that delivers a Nikkei 225 Tanshin delivers a DAX annual report.

For real-time pipelines the webhook channel is the recommended path: subscribe once, receive a POST with full filing metadata within roughly 60 seconds of EDINET or TDnet publication. Japan's fiscal-year concentration around the 31 March year-end produces a predictable throughput surge in May (quarterly Tanshin and results announcements) and late June (statutory annual reports), which the webhook infrastructure handles without per-subscriber rate changes. The payload shape is identical across markets — a Japanese earnings flash arrives with the same JSON envelope as a French AMF filing — so your handler processes Tokyo and Berlin without market-specific branching.

Filing bodies are available as JSON metadata, Markdown via /api/filings/{id}/markdown/, and original PDF or XBRL. EDINET files XBRL-tagged statutory reports, and the platform preserves those tagged line-items where the FSA publishes them — particularly useful for building J-GAAP / IFRS comparable financial databases across the TSE Prime universe without per-issuer scraping. The Markdown rendering is valuable for Japanese content where the EDINET PDF renderings are structurally consistent but verbose; the processed text is substantially more compact and NLP-ready than the source document. Language metadata is exposed on every filing, enabling English-only filters for Prime issuers that publish English Tanshin summaries.

Typical API use cases for Japanese data include backfilling TOPIX and Nikkei 225 consolidated financials for quant research (covering the J-GAAP / IFRS accounting-standard split without per-issuer normalisation), triggering on TDnet ad-hoc announcements — buyback authorisations, parent-subsidiary restructurings, earnings revisions — for event-driven strategies, monitoring EDINET insider-transaction disclosures, and constructing cross-border portfolios that span TSE Prime and European markets using a consistent financial data schema. Trial keys are available on request; the web product is free and publicly indexed, so coverage quality across the 3,800-company universe is verifiable before integration.

Filings indexed
259,076
in Japan
Listed companies
3,897
Japanese issuers
Auth
x-api-key
single header
Webhook latency
< 1 min
from regulator publish

Reporting at a glance — Japan

Regulator, indices, accounting, language
Primary indices
Nikkei 225TOPIXTOPIX Core 30JPX-Nikkei 400
Accounting standards
JGAAP / Japan-IFRS / IFRS / US GAAP (issuer choice)
Reporting languages
JapaneseEnglish
Fiscal year
March year-end common (≈70% of issuers)

Quick start — Japan filings

REST · JSON · Markdown · PDF
# 1. List filings for Japan, newest first
curl "https://api.financialreports.eu/api/filings/?countries=JP" \
    -H "x-api-key: $FR_API_KEY"

# 2. Pull full Markdown for one filing
curl https://api.financialreports.eu/api/filings/<id>/markdown/ \
    -H "x-api-key: $FR_API_KEY"

# 3. Filter by filing type — annual reports only
curl "https://api.financialreports.eu/api/filings/?countries=JP&type=10-K" \
    -H "x-api-key: $FR_API_KEY"

# 4. Filter by ISIN (single issuer)
curl "https://api.financialreports.eu/api/filings/?company_isin=DE000A1EWWW0" \
    -H "x-api-key: $FR_API_KEY"

Full API documentation ↗ · Interactive Swagger ↗

Get API access for Japan

Pricing · trial keys · enterprise
Get API access Talk to the team Read the docs ↗

Filings activity by year

Last 6 years · Japanese issuers
  • 2026 6,311
  • 2025 38,622
  • 2024 43,370
  • 2023 40,014
  • 2022 32,231
  • 2021 24,642

Reporting languages

Filing-by-filing distribution
  • Japanese 256,609
  • English 1,943
  • Korean 240
  • German 119
  • Swedish 102

FAQ — Japan

Coverage, formats, integration
How do I authenticate API requests for Japan filings?
Send a single header — `x-api-key: $FR_API_KEY` — on every request. The same key works across all 42 covered markets; there's no per-country key.
What format does the Japan API return?
Filing metadata is returned as JSON. Full filing bodies are available as Markdown (one endpoint) and original PDF. The same payload shape is used across every covered market.
Do you provide webhooks for new Japanese filings?
Yes. Webhook subscribers receive a POST with full filing metadata within ~60 seconds of the regulator publishing the document.
Is there a rate limit on the Japanese API?
Standard plans are throttled to a generous request budget that suits typical research and dashboards. Bulk and high-throughput plans negotiate higher limits.
Is there a free tier for Japan data?
The web product (search, browse, single-filing read) is free and indexed for the public web. Programmatic API access is a paid plan; trial keys are available on request.