Japanese Financial News API
Real-time news from Japanese domestic sources, structured for systems that do not read Japanese. Articles arrive in Japanese with sentiment scores and English canonical company tags: TSE tickers, ISINs, exchange listings.
What the API returns
A Japanese article, as your system receives it
One JPY options market note from Kabutan. Timestamps are UTC; this article published at 02:30 JST, hours before European desks open.
{
"link": "https://kabutan.jp/news/marketnews/?b=n202608080024",
"source": "kabutan.jp",
"title": "[通貨オプション]OP売り、イベント通過や週末要因",
"summary": "ドル・円オプション市場で変動率は低下。週末要因やイベント通過でオプション売りが優勢となった。...",
"publishDate": "2026-08-07T17:30:00.000Z",
"language": "ja",
"categories": ["markets"],
"countries": ["JP"],
"sentiment": "neutral",
"confidence": 0.9999
}Response abbreviated. Full objects include links, confidence scores, and full content on plans with content access.
Entity resolution
Japanese article in, English entities out
The gap between Japanese domestic news and non-Japanese-speaking desks is not translation. It is identification: which listed company is this article about, and what is its ticker. finlight resolves company names written in kanji and katakana to canonical entities with primary and cross-listings.
{
"source": "minkabu.jp",
"title": "日経平均寄与度ランキング（大引け）～日経平均は小幅続落、アドバンテストや...",
"language": "ja",
"companies": [
{
"name": "Toyota Motor Corporation",
"ticker": "7203",
"primaryListing": { "exchangeCode": "XJPX", "exchangeCountry": "JP" },
"otherListings": [{ "ticker": "TM", "exchangeCode": "XNYS" }, "..."],
"isin": "JP3633400001",
"sector": "Consumer Discretionary",
"confidence": 0.92
},
{
"name": "SoftBank Group Corp.",
"ticker": "9984",
"primaryListing": { "exchangeCode": "XJPX", "exchangeCountry": "JP" },
"isin": "JP3436100006",
"confidence": 0.92
}
]
}A Nikkei 225 contribution ranking from Minkabu, written entirely in Japanese, tagged with 25 companies. Your systems filter and route on 7203 or US-listed ADR tickers without parsing a single character of Japanese.
Get started
Query Japanese news for a TSE name
Insert your key, run it. The query filters to Japanese-language articles for Toyota (7203) and returns entity data.
import { FinlightApi } from 'finlight-client'
const api = new FinlightApi({ apiKey: 'YOUR_API_KEY' })
const res = await api.articles.fetchArticles({
language: 'ja',
tickers: ['7203'],
includeEntities: true,
pageSize: 10,
})
for (const a of res.articles) {
console.log(a.publishDate, a.sentiment, a.title)
console.log(
' companies:',
a.companies?.map((c) => `${c.name} (${c.ticker})`).join(', '),
)
}The same filters work on the WebSocket stream and on webhooks, so a language: ja subscription with a ticker list runs during Tokyo hours while your team does not.
Source coverage
What is covered today
finlight ingests Japanese-language financial news from domestic sources including Kabutan, Minkabu, Jiji Press, NHK, and Kyodo News via 47news. Coverage spans TSE-listed equities, FX and rates commentary, macro releases, and corporate news, plus Japanese-language coverage of overseas markets as domestic outlets report them.
Every article carries the standard finlight structure: sentiment with a confidence score, category tags, country tags, and company entities where companies are identified. The source list grows; the current live set is on the sources page in your dashboard.
The live list is always visible on the sources page in the dashboard; the page you are reading is not the source of truth for the current set.
Honest comparison
The alternative: English wires only
Most non-Japanese desks cover Japan through English wires and English-language Japanese outlets. That works for headline events. What it misses is the domestic layer: Kabutan and Minkabu publish market-moving detail on individual TSE names, contribution rankings, and intraday commentary that English services pick up later, partially, or not at all. If your strategy touches Japanese single names during Tokyo hours, the domestic sources are where the information starts. finlight does not replace your wires; it adds the layer they do not carry, in a structure your systems already consume. Trading desks use this coverage for TSE-hour signal generation; geopolitical risk teams for multi-perspective Japan monitoring.
Pricing
Plans that scale with your coverage needs
Start free with 5k requests per month. Japanese sources are part of the standard source set, not an add-on.
Pro Standard
REST and WebSocket access with sentiment, entities, and country tags
Pro Scale
Multiple WebSocket connections and higher dispatch quotas for multi-desk setups
Compare all plans on the pricing page
Other ways to connect
REST, WebSocket, webhooks, or MCP
The REST API is one integration. finlight also offers real-time streaming, event-driven webhooks, and an MCP server for AI agents.
Frequently Asked Questions
Japanese Financial News API Questions
Common questions about using finlight for Japanese domestic financial news coverage.
Japanese-language coverage is included in the standard plans; there is no separate fee for it. See the pricing page for tiers and request volumes.
Still Have Questions?
Our developer-first support team is here to help you integrate and scale.
Japanese domestic financial news, structured, in real time, in your stack today
Free tier, no card. Your first language: "ja" call is five lines of code.
Custom sources, annual invoicing, priority onboarding: contact us.