Skip to main content
Japan Segments provides the business-segment breakdown a Japanese-listed company tagged in its own EDINET annual and half-year reports: revenue (external, intersegment and total), segment profit, assets, capex, depreciation, R&D, goodwill, impairment and headcount, per segment per period. Segment names come from the filing, with the company’s own English label where it published one. Every response carries a reconciliation block that checks whether the segments add up to the consolidated figure.
Plan: Free and above · Credits: 1 per call

​
What you can use Japan segments for

See which business drives a Japanese company’s revenue and profit, and how the mix moves year to year. Compare segment margins. Track capex and R&D by segment. Japanese segment data is not in Segmented Financials, which covers SEC filers only.

​
Read this before you add anything up

The rows are flat but the segments are a tree, and subtotals sit in the same table looking exactly like segments. One filer reports a segment group, its four children and a reportable-segments total; summing the value column naively gives about ¥4.66 trillion against a real ¥1.69 trillion.Pass leaves_only=true, or keep only rows where segment_is_leaf is true and member_role is segment.
member_role is segment, total or reconciliation. segment_depth and segment_parent place each row in the tree.

​
The reconciliation block

Every response carries reconciliation: for each recent period, the sum of the leaf segments’ external revenue (leaf_sum, over n_leaf segments) against the consolidated revenue from the same filing (consolidated), with the gap as diff_pct (in percent). Use it to see whether the breakdown adds up for that company and period instead of assuming it. It needs both sides in one filing — external revenue tagged per segment and a consolidated revenue line in yen. An empty reconciliation on a response that has segment rows means it could not be computed, not that the segments failed to add up. A large diff_pct usually means the filer tagged a subtotal that is not yet classified, not that a number is wrong.

​
Key Japan segment fields

  • segment, segment_label_en, segment_label_ja — the segment’s machine name and the filer’s English and Japanese labels.
  • metric_key — FocusAlpha’s normalised metric (see the parameter below). Rows whose element did not map keep metric_key null with the raw element_id, so nothing is hidden by failing to normalise.
  • value and unit — the amount and its unit, usually JPY; employees rows are headcounts.
  • period_start, period_end, rel_period — the period, and the filing’s own word for it (当期 current, 前期 prior).
  • doc_id and doc_type_code — the EDINET filing the row came from.

​
Japan segments coverage

Not every filer tags segments: a single-segment company reports none at all, and some file the breakdown only as a note. The coverage block reports how many companies have segment rows (companies_covered) against the Japanese universe (companies_tracked), and the range of filings loaded.

​
GET /v1/companies/{company}/jp/segments

​
string
required
Tokyo symbol (7203.T or 7203), five-digit EDINET security code, EDINET filer code, ADR symbol (TM), ISIN or company_id.
​
string
One of revenue_external, revenue_intersegment, revenue_total, segment_profit, assets, assets_noncurrent, liabilities, capex, depreciation, employees, employees_temporary, rnd, goodwill, goodwill_amortization, impairment. Omit to get every metric, mapped or not.
​
string
default:"false"
true keeps only the rows that are safe to sum. If a filer’s members are not yet classified, this can drop all of its rows — try without it.
​
string
annual, half or quarterly.
​
string
Exact period end, YYYY-MM-DD.
​
integer
default:"200"
Rows per page, between 1 and 1000, newest period first. Narrow with period_end and metric_key to keep one period in one page.
See also Japan Financials for the consolidated figures the reconciliation compares against, and Japan Report Sections for management’s narrative on each business.