FXMacroData vs e-Stat API: Japan CPI and Labour Data for JPY Traders

This comparison is for FX traders, quant developers, and analysts who need Japanese CPI, core CPI, and labour data in code, and who are deciding whether to call Japan's official e-Stat API directly or use FXMacroData. Both routes lead to the same Statistics Bureau numbers. The decision is about how much work sits between the 08:30 JST release and a row that your USD/JPY model, alert, or dashboard can use.

The short answer: e-Stat is the free, authoritative portal for Japanese government statistics, with full table detail, English documentation, and a licence that permits commercial use. FXMacroData reads the same official Statistics Bureau and Bank of Japan releases and adds what an FX workflow needs on release day: a second-level announcement timestamp on every row, a release calendar, one schema across 22 currencies, and pair context next to the Bank of Japan decisions that the data feed into.

Decision snapshot

Choose e-Stat when

You need free, source-of-record Japanese statistics: CPI by item and region, Tokyo ward-area CPI, Labour Force Survey tables, long history, and full survey metadata.

Choose FXMacroData when

You trade or model the release itself: exact publication time, the calendar, and the same data shape for JPY, USD, EUR, GBP and 18 other currencies.

Fast verdict

e-Stat is the right free archive for Japan. FXMacroData is the release-time layer for JPY automation. Many research stacks use both.

Takeaway: if the job ends at "what was Japan's core CPI", e-Stat is enough. If it continues to "when could the market have known it, and what did USD/JPY do next", you need a release-time layer.

Pricing And Access

There is no commercial price to compare. Japan's statistics portal offers two free programmatic routes. The e-Stat API (version 3.0) requires a free e-Stat account, which issues an application ID (appId) that must be sent with every request and may not be shared with third parties. The Statistics Dashboard API, also run for Japan's official statistics, needs no registration at all and exposes around 6,000 headline indicators. The Bank of Japan added a third free route on 18 February 2026, when it launched an API for its Time-Series Data Search with JSON and CSV output and no key.

FXMacroData has an Always Free tier with no key, but it covers USD data only (100 requests per day, USD announcements delayed 15 minutes), so JPY data needs a paid plan. The Individual plan is $50/month or $500/year with a 14-day trial and 1,000,000 requests per month (bursts of 300 per minute and 5,000 per hour, 20 concurrent). Business is $250/month or $2,500/year for companies and teams of up to 10 people, with the same allowance and priority support. Enterprise is by custom agreement.

e-Stat API 3.0

Free, appId*

Free e-Stat sign-up issues an application ID. XML, JSON, JSONP, or CSV; up to 100,000 records per request by default.

Statistics Dashboard API

Free, no key*

About 6,000 indicators with time and region axes; XML, JSON, CSV, and JSON-stat.

FXMacroData Individual

$50/month

JPY and 21 other currencies, real-time releases, 1,000,000 requests/month, 14-day trial.

Takeaway: for Japan-only research the official routes cost nothing. You pay FXMacroData for release-time delivery, cross-currency coverage, and the integration work you no longer maintain.

Side-By-Side Comparison

* Competitor pricing, access, and limits retrieved from the e-Stat API documentation and terms of use in October 2026. e-Stat lists no paid API tier.

What The Official APIs Return For Japan CPI

The chart below was built from the keyless Statistics Dashboard API with one request, using indicator code 0703010601010030010: CPI all items less fresh food, year-on-year change, 2025 base. This is the measure FX markets call Japan's core CPI and the one the Bank of Japan's price-stability discussion centres on.

Japan core CPI (all items less fresh food), % change from a year earlier, September 2025 to August 2026

National, original series, 2025 base. Values marked fixed by the Statistics Bureau.

Takeaway: core inflation fell from 3.0% in late 2025 to 1.4% in April and May 2026 and has held below 2% since January, which keeps every monthly print relevant to the Bank of Japan path and to USD/JPY.

Two details from building that chart matter for anyone writing their own pipeline. First, Japan moved its CPI to a 2025 base in August 2026: the Statistics Bureau converted earlier history to the new base and began publishing monthly reports on it from 21 August. The dashboard still serves the discontinued 2020-base series under a different code, so a pipeline pinned to the old code can quietly drift from the official headline. Second, the same request returned headline CPI at 1.9% and, from the Labour Force Survey, a seasonally adjusted unemployment rate of 2.5% for August 2026. Each series has its own code, unit, and seasonal-adjustment flag, and you need to know which combination matches the published headline.

Release Timing And API Availability

The e-Stat release calendar schedules national CPI and the Labour Force Survey at 08:30 JST. National CPI for September 2026 is due on 23 October; Tokyo ward-area CPI for October, the earlier signal markets watch for the national trend, is due on 30 October; and the Labour Force Survey for October is due on 1 December. Tokyo CPI matters to JPY traders because it arrives about three weeks before the national figure for the same month.

The API side is a separate question. The e-Stat API documentation and terms reviewed for this article do not say at what time a new month becomes retrievable through the API, and the terms state that neither the government nor the Statistics Center guarantees the content. That is reasonable for a statistical archive. For a trader who wants the value at 08:30:01 JST, it means watching the release page or using a feed built for release time.

One Japan CPI release, two data paths

1. 08:30:00 JST

The Statistics Bureau publishes national CPI. USD/JPY reprices during the Tokyo session.

2. Seconds later

FXMacroData row: headline or core value, prior, source, and a second-level announcement_datetime.

3. Table refresh

The new month appears in the e-Stat table and dashboard indicator; no retrieval time is stated in the API documentation.

4. Base change

On a rebasing, e-Stat restates history on the new base. Your pipeline must switch tables or codes to stay aligned with the headline.

FXMacroData targets one second from publication, measured from the actual publication rather than the schedule, and publishes the record at /release-speed, including the share of releases available within one second by source and every release that took longer. Scheduled times for the next Japan CPI or jobs print sit on the release calendar, and the FX sessions view shows that 08:30 JST lands in the Tokyo morning, before London opens.

API Format And Developer Experience

The e-Stat API is thorough. Version 3.0 offers seven functions, including getStatsList to search tables, getMetaInfo to read a table's classification codes, getStatsData to pull values, and getStatsDatas for batch retrieval. Output can be XML, JSON, JSONP, or CSV, and a lang parameter returns English labels where they exist. The English documentation covers the API overview and terms, while parts of the detailed specification are written in Japanese. The work is in navigating tables: a CPI request needs the right statsDataId, area code, and category codes, and those change when a table is replaced on a new base.

FXMacroData uses one route pattern for every currency and indicator. A Japan core CPI request looks like this:

curl -H "X-API-Key: YOUR_API_KEY" "https://api.fxmacrodata.com/v1/announcements/jpy/core_inflation"

Example response (abridged, illustrative):

{
  "currency": "JPY",
  "indicator": "core_inflation",
  "data": [
    {
      "date": "2026-08-31",
      "val": 1.7,
      "prior": 1.8,
      "announcement_datetime": 1789687800,
      "announcement_datetime_local": "2026-09-18T08:30:00+09:00"
    }
  ]
}

Fields an FX model uses

• announcement_datetime anchors the event to the second.
• val and prior arrive as numbers, ready for surprise maths.
• The same fields come back for USD, EUR, GBP, and every other currency.

The e-Stat equivalent

A VALUE object keyed by time code 20260800, indicator, unit, region, and a fixed-or-provisional flag, with the value as a string. Accurate and official, but with no release time.

Takeaway: the same official number, shaped for a different job. e-Stat describes the statistical period; FXMacroData describes the release event.

The same pattern returns US CPI, UK inflation, or a euro-area policy rate decision, so a USD-versus-JPY model does not need a second parser. For US data, US CPI and Non-Farm Payrolls sit under the same schema next to the Fed policy rate.

The Bank Of Japan Time-Series API

Japanese macro data does not all live on e-Stat. Policy rates, money market rates, the balance of payments, money stock, Tankan results, and corporate goods prices come from the Bank of Japan. Since 18 February 2026 the BoJ has offered an API for its Time-Series Data Search, returning JSON or CSV without a key, and with English series names. It is a useful companion to e-Stat for anyone building a full Japan dataset, and it carries its own usage notice.

For the policy side of JPY, including how the BoJ sets rates and which indicators it watches, see the Bank of Japan guide. FXMacroData draws on the BoJ for its JPY policy-rate, balance-of-payments, and money data, and places those series in the same schema as the Statistics Bureau releases.

Licence And Commercial Use

e-Stat's content terms are based on the Government of Japan Standard Terms of Use (version 2.0). They state that commercial use is permitted, that content may be used under a Creative Commons Attribution 4.0 licence instead of the terms, and that numerical data and simple tables are not subject to copyright. The separate API terms add conditions on the access route: the application ID is for the registered user only, applications must display a source credit in the format e-Stat specifies, heavy access in a short period is prohibited, and access may be limited depending on load. The Statistics Dashboard API asks for a similar credit line.

FXMacroData plans cover an individual's or team's own research, dashboards, notebooks, alerts, and API scripts. Showing FXMacroData data to an outside audience is covered by the self-serve Commercial Redistribution add-on at $10/month per block of up to 100 measured users or 1,000 public-feed followers.

How FXMacroData Builds On Japan's Official Data

FXMacroData's Japan CPI, core CPI, and unemployment rows come from the same official Statistics Bureau releases published through e-Stat and the Statistics Bureau's own release pages, and its policy and external-sector rows come from the Bank of Japan. FXMacroData reads the same official releases and adds the release time, source metadata, and a consistent schema. If a figure ever looks odd, the Statistics Bureau is the authority.

What FXMacroData adds sits around that number: one schema for 22 currencies, a release calendar, FX spot rates, COT positioning for yen futures, bond yields including JGBs, central-bank press releases, exports, widgets, and an MCP server, so a Japan CPI surprise can be read against USD/JPY in one place.

Where e-Stat Is Genuinely Stronger

• It is the source of record. Japanese government statistics are published here, with methodology, classification metadata, and survey notes alongside the data.
• Depth. CPI by item, region, and goods-or-services split, Tokyo ward-area CPI, Labour Force Survey detail by age, sex, and employment type, and statistics from many ministries, all through one API.
• Cost and licence. It is free, commercial use is permitted, and the content terms are compatible with CC BY 4.0.
• Formats. XML, JSON, JSONP, and CSV, plus a keyless dashboard API for quick headline pulls.
• Batch size. Up to 100,000 records per request by default suits large research downloads.

If you are building a Japan inflation model by item, studying regional labour markets, or need a table FXMacroData does not carry, use e-Stat.

Where FXMacroData Is Stronger For FX Teams

FXMacroData strengths

• Releases typically available within seconds, with a public speed record.
• Second-level timestamps for point-in-time tests.
• One schema, 22 currencies, calendar, FX, COT, yields, MCP.

FXMacroData tradeoffs

• JPY data needs a paid plan; the free tier is USD only.
• Carries FX-relevant headlines, not every e-Stat table.
• The Statistics Bureau remains the methodological reference.

e-Stat strengths

• Free, official, and commercially usable with credit.
• Very deep Japanese price and labour coverage.
• English labels and documentation for the core API.

e-Stat tradeoffs

• No release timestamp; no stated API availability time.
• Table and code navigation; codes change on rebasing.
• Japan only; other currencies need other agencies and parsers.

Takeaway: e-Stat wins on depth and cost for Japan research. FXMacroData wins when the release moment and the cross-currency comparison drive the decision.

The cross-currency point matters most for yen pairs. USD/JPY reacts to Japanese CPI in the Tokyo morning and to US CPI and payrolls in the New York morning. A trader comparing both would otherwise integrate e-Stat, the BoJ, and the US Bureau of Labor Statistics, each with its own IDs, formats, schedules, and revision habits. FXMacroData returns all of them in the same shape, which is why the pair view for USD/JPY, EUR/USD, or AUD/USD can show both sides of the macro picture together.

Example workflow: Tokyo CPI into USD/JPY research

Plan

Check the calendar for Tokyo ward-area CPI at 08:30 JST and the next BoJ meeting date.

Capture

Pull the core CPI row with its announcement timestamp as soon as it is published.

Compare

Read it against US CPI, JGB and Treasury yields, and yen COT positioning.

Act

Send the surprise into a notebook, alert, or MCP-connected assistant.

Takeaway: e-Stat supplies the official number. The workflow around it, from calendar to pair reaction, is where a release-timed layer saves time.

Decision Matrix

Recommendation

Use the e-Stat API when the work is Japan-focused research: item-level CPI, regional data, Labour Force Survey detail, long histories, or any table FXMacroData does not carry. Register for a free application ID, display the required credit, and pace your requests. For quick headline pulls, the keyless Statistics Dashboard API is often enough, and the BoJ API covers the central-bank side.

Use FXMacroData when the work is about the release as a market event: trading or modelling the reaction in USD/JPY, running alerts on Tokyo or national CPI, comparing Japan with the US and Europe, or giving an AI assistant timestamped, source-labelled macro context across currencies. Compare the plans, read the API reference, and check the measured release-speed record before deciding. AI-focused teams can start from the AI trading guides.

Bottom line: e-Stat is the right free archive for Japanese price and labour statistics. FXMacroData is the right paid layer for FX teams that need Japan CPI and jobs data timestamped to the second and lined up with 21 other currencies. Most serious JPY research stacks benefit from both.

Sources Checked

The e-Stat and Bank of Japan claims in this article come from the official pages and API responses below, checked in October 2026.

e-Stat API

API overview, application ID, version 3.0 specification, functions, formats, and record limit.

API overview · How to use · Specification 3.0

Terms

API terms (appId, credit, load) and content terms (Standard Terms of Use 2.0, CC BY 4.0, commercial use).

API terms · Content terms

Statistics Dashboard API

Keyless access, indicator count, formats, and credit line; source of the core CPI chart.

Dashboard API

Release schedules and CPI base

08:30 JST release times, 2026 CPI and LFS dates, and the 2025-base revision.

CPI calendar · LFS calendar · 2025 base

Bank of Japan API

Launch of the Time-Series Data Search API on 18 February 2026, formats, and usage notice.

BoJ notice

FXMacroData plans and docs

Plans, allowances, API reference, and release-speed record.

View plans

Takeaway: every e-Stat figure here, from the record limit to the August core CPI print, can be checked on the official pages or reproduced with a keyless API call.

Related Reading

• JPY data coverage guide for every Japanese series FXMacroData carries.
• FXMacroData vs BLS API for the US side of USD/JPY: CPI and payrolls from the official source.
• FXMacroData vs ECB Data Portal API for another official-source comparison.
• Best macroeconomic data APIs in 2026 for a broader buyer guide.