FXMacroData vs KSH (Hungarian Central Statistical Office): Hungarian Macro Data for HUF Traders

This comparison is for FX traders, quant developers, and analysts who need Hungarian macro data in code and are deciding whether to work directly with the Hungarian Central Statistical Office (KSH, also published in English as HCSO) or use FXMacroData. The forint is one of the most rate-sensitive currencies in central and eastern Europe: EUR/HUF and USD/HUF tend to move on the 08:30 Budapest CPI print and again on Magyar Nemzeti Bank (MNB) decision days, so the data route you choose decides how quickly and cleanly those events reach your model.

The core finding is that these are different tools. KSH is the official, free source of record for Hungarian statistics, with STADAT summary tables in CSV and XLSX, a dissemination database for detailed queries, a High-Value Datasets API, and a CC BY 4.0 licence. It does not offer one REST API over its full release flow. FXMacroData reads the same official KSH releases and MNB decisions and adds the FX layer: second-level announcement timestamps on every row, one JSON schema across 22 currencies, a release calendar, MNB reference rates for 17 HUF pairs, and MCP access for AI assistants.

Pricing And Access

Price is not a like-for-like commercial comparison. KSH publishes its STADAT tables, first releases, dissemination database, and High-Value Datasets free of charge, with no registration or API key. Its copyright policy places most content under Creative Commons Attribution 4.0 (CC BY 4.0), so commercial reuse is allowed, but attribution is mandatory: content may be used only if KSH is named as the source ("Source: HCSO / ksh.hu"), the credit may not be hidden or separated, and online credits must carry an active link. Custom data files prepared on request fall under the non-commercial CC BY-NC 4.0 licence instead, and the KSH logo cannot be reused without written consent.

FXMacroData is a paid workflow product. The Always Free tier needs no key and covers USD data only, at 100 requests per day with USD announcements delayed 15 minutes. HUF data starts on the Individual plan at $50/month or $500/year, with a 14-day trial, 1,000,000 requests per month, and bursts of 300 per minute. The Business plan at $250/month or $2,500/year covers companies and teams of up to 10 people with the same allowance and priority support. Showing FXMacroData data to your own users is a self-serve add-on at $10/month per block of up to 100 measured users.

Side-By-Side Comparison

* KSH terms, formats, and publication times retrieved from its public copyright policy, High-Value Datasets API documentation and OpenAPI description, STADAT pages, and first-release time notice in October 2026.

What The Official Data Shows

The chart below combines two official sources, which is exactly the joining work an FX desk does around the forint. Headline CPI comes from KSH STADAT table 1.2.1.2, downloaded as CSV, where the annual rate is published as an index with the same month of the previous year at 100 (so 101.3 means 1.3%). The policy rate is the MNB central bank base rate from the MNB's own base-rate history file, shown at each month end. The MNB defines its 3% inflation target on the KSH consumer price index, with a ±1 percentage point tolerance band. In FXMacroData the two series are HUF CPI inflation and the MNB policy rate.

Coverage And Depth

KSH is far deeper on Hungary than any FX data product. The August 2026 CPI first release alone reports the consumer price index, the harmonised index (1.8% year on year), KSH's core inflation measure (2.0%), and the pensioner index (0.9%), then breaks prices down to individual items. STADAT adds full tables by consumption group, COICOP class, and seasonally adjusted form, plus labour, national accounts, and regional data. If your question is about Hungarian food inflation or household energy prices, KSH is the place to go, and FXMacroData will not replace it.

FXMacroData's coverage is built the other way round: narrower per country, wider across countries. For HUF it carries the series an FX desk watches: CPI inflation, producer prices, retail sales, wages, GDP, unemployment and employment, trade balance, current account, money supply, Hungarian government bond yields, and the MNB policy rate. Several of those come from the MNB or the debt agency rather than KSH, which is the point: HUF rows from more than one official publisher arrive in one format. For the central bank side, including how the Monetary Council reads CPI, see our MNB monetary policy guide; for the curve, see the Hungary government bond yields article.

Programmatic Access Routes

KSH offers several ways in, and it helps to know which one does what. STADAT summary tables are the practical route for most macro series: each table has a stable CSV and XLSX download, an English version, and a "last updated" date. The dissemination database (Tájékoztatási adatbázis, served at statinfo.ksh.hu) lets you build detailed custom queries through a web interface. The newer High-Value Datasets API at data.ksh.hu, published under the EU's high-value datasets rules, lists 13 datasets including industrial production, producer prices, retail sales volumes, HICP, and quarterly and annual national accounts, with an OpenAPI description and SDMX files.

Each route has a catch for a trading system. STADAT files are built for people as well as machines, with stacked sections for different base periods. The High-Value Datasets API is clean and documented, but it serves curated files, not a release-by-release feed: the HICP distribution we checked listed a 2017 to 2024 period, issued in February 2026. The MNB, separately, runs a public SOAP web service for its official daily exchange rates and an Excel file of base-rate history.

Release Timing And Timestamps

KSH publishes on a fixed clock. Since January 2023, first releases have appeared on the KSH website at 08:30 Budapest time on the day shown in the dissemination calendar, moved from 09:00. CPI for a given month usually lands in the first half of the following month: the August 2026 figures were published on 8 September 2026 at 08:30 CEST, which is 06:30 UTC, and the September figures are scheduled for 7 October 2026. The MNB Monetary Council meets monthly and announces its decision in the afternoon of the meeting day; FXMacroData records those decisions at 14:00 Budapest time.

The KSH files themselves carry a date, not a moment: STADAT shows "last updated: 8 September 2026", and the CSV has no time field per observation. That is fine for research, but an event study needs to know when each past print became public, to the second, so that no backtest uses a number before it existed. FXMacroData reads the same official release and stores an announcement_datetime in epoch seconds on every row, past and present, in the same field across all 22 currencies. Releases are typically available within seconds of official publication, against a target of one second, and the measured record is published at /release-speed, including the share of releases inside one second by source and every release that took longer.

API Design And Developer Experience

Working with KSH directly is file handling more than API calls: download the English CSV, split on semicolons, convert decimal commas, find the section headed "Corresponding period of the previous year = 100.0%", carry the year down, and subtract 100 from the index. None of it is hard, but every table has its own layout.

FXMacroData uses named routes instead. The same indicator name works across countries, so switching from Hungarian to US inflation is a change of currency code. The HUF inflation API docs list the fields; a request looks like this:

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

Year;Period;Food;...;Total;Consumer price index of pensioners
Corresponding period of the previous year = 100.0%
2026;January;...;102,1;...
;July;...;101,2;...
;August;...;101,3;100,9

{
  "date": "2026-08-31",
  "val": 1.3,
  "prior": 1.2,
  "announcement_datetime": 1788849000
}

On the exchange-rate side, FXMacroData lists the Magyar Nemzeti Bank as an official FX reference source and serves its daily official rates for 17 HUF pairs, credited "Source: Magyar Nemzeti Bank", alongside spot rates through /v1/forex/eur/huf, with no SOAP client to write.

Rate Limits And Fair Use

KSH does not publish a numeric request limit for STADAT downloads or the High-Value Datasets API; the documentation asks automated users to act responsibly and avoid excessive load, and calls from browser-side web apps are blocked by CORS. For a handful of monthly tables that is ample; for catching new prints, you build your own polite polling and change detection.

FXMacroData's limits are explicit: 1,000,000 requests per month on Individual and Business, with bursts of 300 per minute, 5,000 per hour, and 20 concurrent requests. Because new releases can be pushed over SSE streaming, an FX application does not need to poll at all to catch the 08:30 print.

Licensing And Redistribution

KSH's licence is open but not unconditional. CC BY 4.0 allows commercial reuse, and a fintech can publish Hungarian statistics to clients on that basis, provided every use credits "Source: HCSO / ksh.hu" visibly, with an active link online. Two details matter for products: custom data files that KSH prepares on request are CC BY-NC 4.0 and cannot be used commercially, and the KSH logo and domain name need written permission for anything beyond reference.

FXMacroData's Individual plan covers a trader's or analyst's own research, dashboards, and scripts; Business covers internal team use. If you show FXMacroData data to your own users, the Commercial Redistribution add-on is $10/month per block of up to 100 measured users or 1,000 public-feed followers, and it is self-serve.

Where KSH Is Genuinely Stronger

Where FXMacroData Is Stronger

The gap opens as soon as Hungary is one of several countries in your model. EUR/HUF reacts to Hungarian CPI and MNB decisions, but also to euro-area inflation and the ECB policy rate; USD/HUF adds US CPI and the dollar cycle. With KSH alone you would add the MNB, Eurostat, the ECB, and the BLS as separate integrations, each with its own formats and time conventions. With FXMacroData those rows share one schema and one timestamp field.

Around the releases, FXMacroData adds the context an FX desk uses: the cross-country release calendar, FX spot and MNB reference rates, government bond yields, MNB statements in the HUF press-release feed next to the ECB feed, pair dashboards, exports, and widgets. The MCP server lets Claude, ChatGPT, or Cursor query the same records directly, so an assistant can answer "what did Hungarian CPI do this morning and how did EUR/HUF respond" with sourced rows rather than a web search.

Decision Matrix

Recommendation

Choose KSH if your work is about Hungary itself: detailed price breakdowns, official citation, revision analysis, or a Hungarian data warehouse. It is free, keyless, openly licensed, and the source FXMacroData itself relies on for Hungarian statistics.

Choose FXMacroData if Hungarian data is an input to FX decisions. You get the 08:30 CPI print and the MNB rate decision with second-level timing, next to the euro-area, US, and other data that moves EUR/HUF and USD/HUF, without maintaining separate KSH and MNB integrations. Check the measured timing record at /release-speed, browse the API reference, and compare plans on the pricing page; the Individual plan includes a 14-day trial, and you can start it here.

Sources Checked

Related Reading

• FXMacroData vs ECB Data Portal API: official euro-area statistics, the other side of EUR/HUF.
• FXMacroData vs Eurostat API: harmonised EU data, including Hungarian HICP.
• FXMacroData vs Trading Economics: a commercial multi-country alternative.
• Best macroeconomic data APIs in 2026: the wider landscape.