All APIsexpand_more
Full financial statement (hierarchical)
/stable/financial-statement-full10 tokens per callReturns every line item of the balance sheet, income statement, cash-flow statement, statement of changes in equity, comprehensive income and the earnings-release summary as the presentation tree of the filing (XBRL). Each item carries its depth, parent (parent_key), order (sort), heading/subtotal flags, original XBRL tag (company extension tags included), labels, context and how the value was obtained. Without a fiscal period you get the latest one; pass quarter=FY for the full fiscal year.
What you can do with this API
- check_circleRebuild the statement exactly as the company filed it — order, depth and line names
- check_circleSee company-specific line items that standardised fields do not cover
- check_circleCheck subtotals against their child lines
Example URL
https://api.zenithcode.net/stable/financial-statement-full?symbol=7203&fiscalPeriod=2026-03&quarter=FYShown without percent-encoding for readability. Non-ASCII values are encoded automatically when sent.
Parameters
| Parameter | Required | Description | Example |
|---|---|---|---|
symbolstring | Required | Securities code (4 characters, e.g. 7203 = Toyota Motor; alphanumeric codes such as 130A also work) | 7203 |
fiscalPeriodstring | Optional | Fiscal period (YYYY-MM, e.g. 2026-03 = fiscal year ending March 2026). Defaults to the latest | 2026-03 |
quarterselect | Optional | Quarter: Q1, Q2, Q3 or FY. Omit to get the most recent period, which may be a quarter Allowed values: Q1, Q2, Q3, FY | FY |
Try it
Run it with your own parameters and check the response as a table, JSON or CSV. Sign-in required; each run uses 10 tokens.
travel_exploreTry in the API ViewerResponse example (real data)
Response fields
symbol証券コード(4 桁) | string | 証券コード(4 桁) |
fiscalPeriod期末月 YYYY-MM | string | 期末月 YYYY-MM |
periodQ1 | Q2 | Q3 | FY | string | Q1 | Q2 | Q3 | FY |
accountingStandard会計基準(jgaap / ifrs など) | string | 会計基準(jgaap / ifrs など) |
updatedAtデータ基盤が更新した日時 | string | データ基盤が更新した日時 |
statements提出どおりの全科目。statements.{BS|PL|CF|SS|CI|Summary}.items[] に、depth(段)・parent_key(親の tree_tag)・sort(表示順)・is_abstract(見出し)・is_subtotal(小計)・original_tag(XBRL タグ。会社独自の拡張タグを含む)・label_ja / label_en・master_key(標準項目への対応)・context_id・source(xbrl / calculated)・value(円) | object | 提出どおりの全科目。statements.{BS|PL|CF|SS|CI|Summary}.items[] に、depth(段)・parent_key(親の tree_tag)・sort(表示順)・is_abstract(見出し)・is_subtotal(小計)・original_tag(XBRL タグ。会社独自の拡張タグを含む)・label_ja / label_en・master_key(標準項目への対応)・context_id・source(xbrl / calculated)・value(円) |
Statement hierarchy (the tree as filed)
This endpoint returns the presentation tree of each filed statement (XBRL) as is — depth, parent, order and company-specific line items included. Below are the item fields and a tree drawn from a real response.
Reproduce the statement exactly as filed
Order (sort), depth, parent (parent_key) and line names (label_ja) match the filing, so you can rebuild the table the company published.
Company-specific line items are kept
Industry- or company-specific lines (e.g. receivables related to financial services) are filed under the company’s own extension tags. Lines that disappear in standardized fields are returned here with their original_tag.
Check subtotals
With is_subtotal and parent_key you can add up child lines and compare them with the subtotal line — useful for checking ingestion and signs, or as the basis of your own aggregation.
Linked to standardized fields
Lines with a master_key map to standardized fields in income-statement, balance-sheet-statement and so on, so you can trace which line a standardized value came from.
| Field | Meaning |
|---|---|
depth | Depth in the tree; 1 is the top level (Summary and SS may start at 0). |
parent_key | The tree_tag of the parent line; null at the top level. |
sort | Display order in the filing; sort ascending to get the original order. |
is_abstract | A heading-only line; it has no value, so value is null. |
is_subtotal | A total or subtotal line; heading lines are also true. |
original_tag | XBRL tag in the filing. Tags starting with jppfs_cor_, jpigp_cor_, jpcrp_cor_ etc. are standard taxonomy; others (e.g. tse-qcediffr-72030_…) are the company’s extension tags. |
label_ja | The line name given by the company; label_en is the English name and may be empty. |
master_key | The mapped ZENITH Code standardized field (e.g. cash_and_equivalents); null for company-specific lines and similar. |
context_id | The XBRL context (instant or duration), e.g. CurrentQuarterInstant (quarter end) or CurrentYTDDuration (year to date); null on headings. |
source | How the value was obtained: xbrl is taken from the filing, calculated is a subtotal filled in by calculation. |
value | The amount in JPY. Ratios in the Summary are 0–1 decimals (0.104 in the API, 10.4% on screen). Outflows are negative, as disclosed. |
Example: the first lines of the income statement and balance sheet of 7203, 2026-06 Q1 (sample response fetched on 2026-10-23). Amounts are in ¥100 millions.
Income statement (PL)
| Line (depth, tag) | Amount (¥100 mn) |
|---|---|
営業収益HeadingExtension depth=1 · tse-qcediffr-72030_SalesRevenuesIFRSAbstract_pl | — |
Sales of productsExtension depth=2 · tse-qcediffr-72030_SalesOfProductsIFRS_pl | 121,423 |
Financing operationsExtension depth=2 · tse-qcediffr-72030_FinancingOperationsIFRS_pl | 13,831 |
Total net revenuesSubtotalExtension depth=2 · tse-qcediffr-72030_TotalNetRevenuesIFRS_pl | 135,254 |
売上原価並びに販売費及び一般管理費HeadingExtension depth=1 · tse-qcediffr-72030_CostsAndExpensesIFRSAbstract_pl | — |
Balance sheet (BS)
| Line (depth, tag) | Amount (¥100 mn) |
|---|---|
資産Heading depth=1 · jpigp_cor_AssetsIFRSAbstract_bs | — |
Current AssetsHeading depth=2 · jpigp_cor_CurrentAssetsIFRSAbstract_bs | — |
Cash and Cash Equivalentscash_and_equivalents depth=3 · jpigp_cor_CashAndCashEquivalentsIFRS_bs | 103,431 |
Notes and Accounts Receivablenotes_and_accounts_receivable depth=3 · jpigp_cor_TradeAndOtherReceivablesCAIFRS_bs | 40,196 |
Receivables related to financial servicesExtension depth=3 · tse-qcediffr-72030_ReceivablesRelatedToFinancialServicesCAIFRS_bs | 140,863 |
Sample responses keep only the first few items of long arrays, so the tree is cut short; real responses contain every line. “Extension” marks a company-specific tag; a tag such as cash_and_equivalents shows the mapped standard field (master_key).
Related: /stable/financial-statement-full · How metrics are calculated
Related APIs
FAQ
How is this different from the other statement endpoints?expand_more
The income statement and similar endpoints return standardised main items in a flat form. This one returns every filed item with its hierarchy, so the response is larger. Items with a master_key map to the standardised fields.
How do I tell company-specific line items apart?expand_more
Items whose original_tag does not start with a standard taxonomy prefix (jppfs_cor_, jpigp_cor_ and so on) use the company’s own extension tags; industry- or company-specific lines fall into this group.
How many tokens does one call use?expand_more
10 tokens per call, regardless of how many rows come back. Your monthly allowance depends on your plan.
Do I need an account to try it?expand_more
Use the API Viewer to run it with your own parameters. Sign up for free and sign in (no credit card). Each run uses this API's tokens.
Can I get CSV instead of JSON?expand_more
Add format=csv to the URL to get CSV, ready for spreadsheets or pandas.
Can I get labels in English?expand_more
With neither lang nor Accept-Language, labels such as sector names are returned in English; add lang=ja or send Accept-Language: ja for Japanese. Company and sector names are always returned in both languages as nameJa / nameEn and sectorJa / sectorEn. Field names are the same in both languages.

