ECB Exchange Rates Scraper — Free FX Data 1999–Today | No API Key | from $0.50/1K

For finance teams, accountants, and data engineers who need clean, audit-grade historical FX rates for invoice conversion, portfolio valuation, or regulatory reporting — at near-zero cost.

No API key. No proxy. No rate limit. ECB open data back to 1999. $0.50 per 1,000 rows (Pay Per Event). A typical run: all currencies today = ~30 rows ≈ $0.02. Full 2025 EUR/USD daily = 252 rows ≈ $0.13.

Fetch live and historical currency exchange rates from the European Central Bank (ECB) via the free, public Frankfurter API. No API key. No proxy. No auth. Unlimited history back to 1999.

Features

• Three modes: latest (today's ECB snapshot), historical (single date), timeseries (full date range)
• Flat output: one row per (date, base, quote) triple — ready for spreadsheets, databases, pipelines
• 30 ECB currencies including USD, EUR, GBP, JPY, CAD, CHF, AUD, CNY, and more
• Parse confidence field in every row — machine-readable quality signal
• Pay per result — no wasted spend on headers or metadata rows

Input

Field	Type	Default	Description
baseCurrency	string	USD	ISO 4217 base currency
symbols	string[]	all	Quote currencies to return
mode	select	latest	latest / historical / timeseries
startDate	string	—	YYYY-MM-DD (required for historical/timeseries)
endDate	string	today	YYYY-MM-DD (timeseries end)
maxResults	integer	0 (no limit)	Cap total rows for cost control

Output

One dataset row per (date, base_currency, quote_currency) triple:

Field	Type	Example
date	string (ISO date)	2026-05-29
base_currency	string	USD
quote_currency	string	EUR
rate	float	0.85881
amount	float	1.0
mode	string	latest
scraped_at	string (ISO UTC)	2026-05-29T12:00:00Z
parse_confidence	float [0–1]	1.0
warnings	string[]	[]

Interpretation: 1 USD = 0.85881 EUR on 2026-05-29.

Pricing example

Pay per result (PPE). $0.50 per 1,000 rows.

Fetch	Records	Cost
Latest rates, all 30 currencies	~30 rows	~$0.02
1 month EUR/USD daily	~22 rows	~$0.01
1 year EUR→USD, GBP, JPY	~780 rows	~$0.39
Full 2025 all-currencies timeseries	~7,500 rows	~$3.75

FAQ

Do I need an API key or account? No. The Frankfurter API is a free, public ECB data service. No registration, no key, no rate limit documented.

What currencies are supported? 30 ECB currencies: AUD, BRL, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HUF, IDR, ILS, INR, ISK, JPY, KRW, MXN, MYR, NOK, NZD, PHP, PLN, RON, SEK, SGD, THB, TRY, USD, ZAR. ECB does not publish rates for all world currencies.

Can I schedule this to run automatically? Yes. Schedule in Apify Console (e.g. daily at 16:30 CET after ECB publishes) or trigger via webhook from n8n / Make to feed your FX pipeline automatically.

What if a date returns no data? Weekend and holiday dates automatically snap to the previous ECB business day. If the API is unavailable, the actor logs the error and pushes nothing — you are not charged.

Data source

Frankfurter — open-source API backed by ECB reference exchange rates. Published daily at ~16:00 CET on business days. Weekend/holiday dates snap to previous business day automatically.

Supported currencies

AUD, BRL, CAD, CHF, CNY, CZK, DKK, EUR, GBP, HKD, HUF, IDR, ILS, INR, ISK, JPY, KRW, MXN, MYR, NOK, NZD, PHP, PLN, RON, SEK, SGD, THB, TRY, USD, ZAR.

Use cases

• Financial data pipelines (spreadsheets, BI tools, databases)
• Portfolio valuation at historical dates
• FX trend analysis and backtesting
• Invoice currency conversion audit trails
• Academic / research datasets

Competitor comparison

Source	Cost	History depth	Currencies
This actor (ECB/Frankfurter)	$0.50/1K rows	1999–today	30 ECB currencies
Open Exchange Rates	$12–97/mo	1999–today	170 currencies
Fixer.io	$13–97/mo	2000–today	170 currencies
exchangerate-api.com	Free (1,500/mo) then paid	6 mo	162 currencies

ECB data is free, audit-grade, and published daily. The actor wraps 27 years of history into clean flat rows — one per (date, base, quote) triple.

Use with AI agents (MCP)

This actor is callable as a tool by AI agents (Claude Desktop, Cursor, VS Code, n8n, LangGraph, CrewAI, or any MCP-compatible client) via Apify's hosted Model Context Protocol server. An agent uses it to look up historical or live FX rates mid-conversation — e.g. "convert $500 to EUR at the 2024-12-31 rate", "what was the USD/JPY rate last week".

Point your MCP client at this tool:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.apify.com/?tools=bovi/exchange-rates-scraper",
        "--header",
        "Authorization: Bearer <YOUR_APIFY_TOKEN>"
      ]
    }
  }
}

Minimal input an agent can send:

{ "mode": "latest", "baseCurrency": "USD", "symbols": ["EUR", "GBP", "JPY"] }

Also in this finance family

• Yahoo Finance Scraper — stocks, ETFs, crypto, indices, forex
• CoinGecko Scraper — live crypto prices, market caps, all coins
• Binance Scraper — spot prices + OHLCV klines for 3,500+ pairs
• Dexscreener Scraper — DEX pairs, on-chain token prices across 50+ chains
• DefiLlama Scraper — DeFi protocol TVL + yield pool APY

Integrations

Built for finance teams and data engineers pulling audit-grade ECB historical FX rates into pipelines and reports — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.