FXMacroData vs Statistics Denmark API: Danish Macro Data and the DKK Peg

This comparison is for FX traders, quant developers, and analysts who need Danish macro data in code and are deciding whether to call the Statistics Denmark StatBank API directly or use FXMacroData. Denmark is an unusual case for currency work: the krone is pegged to the euro inside ERM II, so EUR/DKK trades in a narrow band and the policy rate of Danmarks Nationalbank exists to defend that peg rather than to steer domestic inflation. That changes which data matters and how you read it.

The core finding: the StatBank API at api.statbank.dk is the official, free, keyless source for Danish statistics, and it also carries Danmarks Nationalbank's own tables for interest rates, exchange rates, reserves, and intervention. It is licensed under CC BY 4.0, which allows commercial use with a source reference. FXMacroData reads the same official releases and adds what an FX workflow needs on top: second-level announcement timestamps, one schema across 22 currencies, a cross-country release calendar, Danish and euro-area data side by side, pair dashboards, and MCP access for AI assistants. Many DKK desks will use both.

Pricing And Access

Price is not a like-for-like commercial comparison. Statistics Denmark offers the StatBank API as a public service with no paid tier. Data calls such as tableinfo and data work without registration or a key; the documentation notes that a key is needed only for the separate catalogue method. Statistics Denmark states that its statistical data can be used free of charge for commercial and non-commercial purposes as long as you include a source reference, which corresponds to Creative Commons CC BY 4.0.

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. DKK 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. Redistribution 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

* Statistics Denmark terms, formats, and extract limits retrieved from its public StatBank API documentation page in October 2026; update times read from StatBank table metadata.

What The Official Data Shows

To show what the StatBank API returns, the chart below is built from one request to table PRIS01 (Consumer price index), selecting the all-items index and the unit "percentage change compared to same month the year before". This is the headline Danish CPI rate that FX desks track. The table's metadata shows the latest update, covering August 2026, landed on 10 September 2026 at 08:00.

The DKK Peg: Why Danish Data Works Differently

Denmark participates in ERM II at a central rate of 746.038 kroner per 100 euro, and Danmarks Nationalbank keeps the krone between 729.252 and 762.824, a band of 2.25% either side. The tools are intervention, buying or selling kroner against euro, and interest rates, which Nationalbanken describes as reserved for managing the exchange rate. Nationalbanken's daily rates in StatBank put EUR/DKK at 747.58 per 100 euro on 1 October 2026, about 0.2% from the central rate.

In practice the policy rate tracks the European Central Bank. On 10 September 2026 Nationalbanken raised its current-account rate by 0.25 percentage point to 2.10%, effective the next day, and said the move was a consequence of the ECB raising its deposit facility rate by the same amount, keeping the spread to the euro area unchanged. The previous change, to 1.85%, took effect on 12 June 2026. So for an FX desk the Danish policy rate is mostly an ECB echo, and the interesting signals are the spread to the ECB policy rate, pressure on EUR/DKK inside the band, reserve changes, and any rate move that is not matched by Frankfurt.

Coverage And Depth

StatBank's catalogue is far deeper on Denmark than any FX data product. PRIS01 alone splits CPI by commodity group down to individual product categories; other tables cover regions, industries, and household types. It also hosts Danmarks Nationalbank's statistics: daily official rates and the DESTR reference rate (DNRENTD), daily exchange rates back to 1977 (DNVALD), foreign-exchange reserve stocks (DNRA), and daily observations of net foreign-currency purchases from intervention (DNVALI). If your research question is about Danish rent inflation or the history of intervention, StatBank is the right place, and FXMacroData will not replace it.

FXMacroData's coverage is designed the other way round: narrower per country, wider across countries. For DKK it carries the series an FX desk watches: headline and month-on-month CPI, PPI, GDP, the unemployment rate, employment and wages, retail sales, trade and current account, confidence surveys, money supply, the Nationalbanken policy rate and a daily risk-free rate, government bond yields, and central-bank reserves. Its FX reference rates include Danmarks Nationalbank's own daily rates, published at about 16:00 Copenhagen time and mirroring the ECB's reference set, listed as a source on /v1/fx/sources. Statistics Denmark and Nationalbanken releases arrive in one consistent format, next to the euro-area data that drives them.

Release Timing And Timestamps

Statistics Denmark publishes at a fixed morning slot: StatBank tables update at 08:00 Danish time on release days, which is 06:00 or 07:00 UTC depending on daylight saving time. The August 2026 CPI, for example, appeared in PRIS01 with an updated value of 2026-09-10T08:00:00.

The difference is in how the time is represented. That updated stamp belongs to the table, carries no time-zone offset, and reflects the table's latest refresh rather than a per-observation release time, so your code has to know it means Copenhagen time and keep its own record of when each period first appeared. FXMacroData reads the same official release and stores an announcement_datetime in epoch seconds for every row, 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. Danish and euro-area releases also sit together in the release calendar.

API Design And Developer Experience

The StatBank API is compact and well documented, with four main methods: subjects and tables for discovery, tableinfo for a table's variables and codes, and data for extraction. Requests can be sent as GET parameters or POSTed as a JSON object, and an online console helps you build them. The learning curve is the code system: you look up table IDs such as PRIS01 or DNRENTD, then variable codes such as VAREGR, ENHED, and time keys like 2026M08 or 2026M10D01. Default labels are in Danish unless you request English, and CSV values use a comma as the decimal separator.

FXMacroData uses named routes instead. The same indicator name works across countries, so switching from Danish to euro-area inflation is a change of currency code, not a new table lookup. A DKK CPI request looks like this:

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

VAREGR;ENHED;TID;INDHOLD
00 Forbrugerprisindeks i alt;
Ændring i forhold til samme
måned året før (pct.);
2026M08;2,00

{
  "date": "2026-08-31",
  "val": 2.0,
  "prior": 1.7,
  "announcement_datetime": 1789020000
}

Limits And Availability

Statistics Denmark caps non-streaming extracts at 1,000,000 cells, counted as rows multiplied by the number of variables plus time and value, and points larger jobs to the streaming BULK and SDMX formats, which have no upper limit. The documentation reviewed does not state a per-second or per-day request limit. For pulling a few headline series that is ample; the practical work is choosing selections carefully so that large tables do not return far more cells than you need.

FXMacroData's limits are 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 StatBank at 08:00 to catch the print.

Licensing And Redistribution

This is a genuine Statistics Denmark strength. Data from Statistikbanken.dk can be used free of charge for commercial as well as non-commercial purposes, including app development, as long as you include a source reference, matching CC BY 4.0. For a team publishing Danish statistics to clients, that is a clear and permissive basis.

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 Statistics Denmark Is Genuinely Stronger

Where FXMacroData Is Stronger

The gap opens as soon as Denmark is one of several countries in your model, and with a pegged currency that is almost always the case. EUR/DKK is driven by the ECB, so a DKK workflow needs euro-area policy and inflation beside Danish data; USD/DKK behaves much like EUR/USD, which brings in US CPI and Non-Farm Payrolls. With StatBank alone you would add the ECB, Eurostat, and US agencies as separate integrations, each with its own identifiers and time formats. 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 reference rates, government bond yields for the Danish and euro-area curves, CFTC positioning in euro futures, central-bank press releases, pair dashboards, exports, and widgets. The MCP server lets Claude, ChatGPT, or Cursor query the same records directly, so an assistant can answer "did Nationalbanken match the ECB this month and where is EUR/DKK against the central rate" with sourced rows rather than a web search.

Decision Matrix

Recommendation

Choose the Statistics Denmark StatBank API if your work is about Denmark itself: deep breakdowns, official citation, peg history, or a Danish data warehouse. It is free, simple to call, openly licensed, and it is a source FXMacroData itself relies on for Danish statistics and Nationalbanken data.

Choose FXMacroData if Danish data is an input to FX decisions. You get DKK releases with second-level timing next to the ECB, euro-area, and US data that actually drives the krone, without maintaining a separate integration per publisher. Check the measured timing record at /release-speed, browse the API reference, follow Nationalbanken statements in the DKK press-release feed and the EUR/DKK dashboard, and compare plans on the pricing page; the Individual plan includes a 14-day trial.

Sources Checked

Related Reading

• FXMacroData vs ECB Data Portal API: the euro-area source behind every Danish rate decision.
• FXMacroData vs Statistics Canada API: the same official-source comparison for CAD.
• FXMacroData vs OANDA Exchange Rates API: reference FX rates compared.
• Best macroeconomic data APIs in 2026: the wider landscape.