Frankfurter FX Rates Scraper

Frankfurter FX Rates Scraper

Scrape daily spot, historical, and time-series exchange rates for 30+ currencies from the Frankfurter API. Each row returns a base currency, target currency, rate, and date. No API key required. Export to CSV, JSON, Excel, or XML.

The European Central Bank publishes daily reference rates, but fetching them in bulk or over a date range requires calling an API endpoint for each day. This Actor reads the public Frankfurter API directly, collecting spot rates, single-date historical snapshots, or full time series for any supported currency pair. It returns every rate as a flat, analysis-ready row. No registration, no API key, and no rate-limit headaches.

Who uses it	What they scrape Frankfurter FX Rates for
Financial analysts	Pull daily EUR/USD or other major pair rates into a spreadsheet for trend analysis.
E-commerce developers	Populate a product database with current multi-currency prices from a single base.
Accounting teams	Fetch historical month-end rates to revalue foreign-currency transactions.
Data scientists	Build a clean time-series dataset of daily FX rates for a forecasting model.

What it does

This Actor collects foreign exchange rates from the Frankfurter API by mode (latest, historical, timeseries, or supported currencies) and returns each rate as a flat row with base, target, rate, and date.

• 📅 Latest spot rates: today's reference rate for all or selected target currencies against a chosen base.
• 🕰️ Historical single date: the rate for a specific past date, useful for period-end closes.
• 📈 Time series range: every daily rate between two dates, returned as one row per day per pair.
• 🌍 Supported currency list: a full list of the 30+ currencies the API covers, with their names.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Frankfurter FX Rates data

💱 Populate a multi-currency pricing table.

An e-commerce manager runs the Actor in latest mode with USD as the base and gets a row for every target currency, then uploads the CSV to their store's price conversion table.

📊 Build a daily FX rate dataset for a model.

A data scientist sets the mode to timeseries, picks a two-year range, and collects every EUR/JPY daily rate into a single flat file for a volatility forecasting model.

🧾 Revalue foreign-currency invoices at month-end.

An accountant runs the Actor in historical mode for the last day of the month, pulls the GBP and CHF rates against the company's EUR base, and posts the revaluation journal entries.

🗺️ Discover which currencies are available.

A fintech product manager runs the currencies mode to get the full list of supported codes and names, then maps them to the countries their app will launch in.

Why choose this scraper

	What you get
No API key	The Frankfurter API is public. No registration, no OAuth, no key to manage.
Bulk collection	Grab up to a million rates in one run, instead of calling the API date by date.
Fixed schema	Every row has the same columns: base, target, rate, and date. No nested JSON to flatten.
Multi-format export	Download your rates as CSV, JSON, Excel, or XML directly from the dataset.

How it compares

No other Store actor targets Frankfurter FX Rates the same way, so the honest comparison is with the alternatives teams actually weigh.

	Frankfurter FX Rates Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Frankfurter FX Rates changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor by selecting a mode, a base currency, and an optional list of target currencies. For historical and timeseries modes, set a single date or a date range to collect only the rates you need. The Input tab lists every parameter.

A first run with the defaults:

{
  "maxItems": 10,
  "mode": "latest",
  "baseCurrency": "EUR"
}

A larger pull:

{
  "maxItems": 200,
  "mode": "latest",
  "baseCurrency": "EUR"
}

Pricing

Pay-per-result: $0.01733 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$1.73
1,000 results	$17.33
10,000 results	$173.30

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Frankfurter FX Rates Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Frankfurter FX Rates through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/frankfurter-fx-rates-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results for my date range?

The Frankfurter API only has data on business days. If your range falls entirely on a weekend or a holiday, no rates will be returned. Try a wider range that includes weekdays.

The Actor fails with an error about an invalid date format.

Dates must be in YYYY-MM-DD format. Check that your Date From and Date To fields use this exact format, with leading zeros for months and days under 10.

I set a base currency but the output still shows EUR.

The base currency field is ignored when the mode is set to 'Supported currency list'. Switch to latest, historical, or timeseries mode to use a custom base currency.

My target currency list is being ignored.

Target currencies are also ignored in 'Supported currency list' mode. For all other modes, ensure the currency codes are uppercase and comma-separated, like USD,GBP,JPY.

FAQ

Question	Answer
Where does the exchange rate data come from?	The data comes from the Frankfurter API, which tracks reference rates published by the European Central Bank. The Actor reads the API's public endpoints directly.
Do I need an API key to use this Actor?	No. The Frankfurter API is a free, public service. This Actor calls it without any authentication, so you can start scraping immediately.
How far back can I get historical rates?	The Frankfurter API provides data back to 1999 for most major currencies. You can set any start date in the timeseries mode to pull the full available history.
Can I get rates for only a few specific currencies?	Yes. Use the Target Currencies field to list the exact codes you need, like USD, GBP, and JPY. Leave it empty to return all 30+ supported pairs.
What is the base currency and how do I change it?	The base currency is the currency you are converting from. The default is EUR, but you can change it to any supported code like USD or GBP in the input settings.
How is the timeseries data structured in the output?	Each row in the dataset represents one rate for one date. If you request a 30-day range for 5 target currencies, you will get up to 150 rows, each with a date, base, target, and rate.
What is the difference between historical and timeseries mode?	Historical mode returns rates for a single specific date. Timeseries mode returns rates for every day in a date range you define, from the start date to the end date.
Can I schedule this Actor to run daily?	Yes. You can set up a schedule on Apify to run the Actor every day in latest mode, giving you a fresh dataset of spot rates each morning.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Frankfurter API. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.