FXMacroData vs yfinance (Yahoo Finance): Unofficial Price Scraper vs Official FX Macro Data

This comparison is for FX traders, quant developers, and analysts who started with yfinance, the popular open-source Python library that pulls data from Yahoo Finance, and are now deciding whether it can carry a macro-driven FX workflow. The question is not whether yfinance is useful. It plainly is. The question is whether an unofficial price and calendar scraper should be the data layer behind backtests, alerts, dashboards, or a product that other people rely on.

The short finding: yfinance is an excellent free tool for quick price prototyping across equities, ETFs, indices, and FX tickers such as EURUSD=X. It is not affiliated with Yahoo, Yahoo publishes no official public finance API, and Yahoo's terms restrict automated collection and commercial reuse. FXMacroData is a licensed, documented FX macro data API built on official statistics agencies and central banks, with second-level release timestamps, a release calendar, FX rates, and published plans that start free.

Decision snapshot

Choose yfinance when

You are prototyping in a notebook, want free multi-asset price history in a few lines of Python, and your use is personal research where an occasional breakage or rate limit is acceptable.

Choose FXMacroData when

You need official macro releases with exact announcement timestamps, a documented API with published limits, a licence for programmatic use, and FX context for automated or commercial workflows.

Fast verdict

yfinance wins for zero-cost price exploration. FXMacroData wins once macro data has to be reliable, timestamped, licensed, and repeatable.

Takeaway: Many traders use both: yfinance for exploratory price pulls, FXMacroData as the official macro layer their systems depend on.

Pricing And Access

yfinance itself costs nothing. It is an Apache-2.0 licensed package installed with pip install yfinance. The cost shows up elsewhere: there is no service agreement, no published rate limit, and no licence from Yahoo to use the data. The yfinance README states that the project is not affiliated with, endorsed, or vetted by Yahoo, that it is intended for research and educational purposes, and that the Yahoo Finance API is intended for personal use only.

Yahoo does sell paid Yahoo Finance plans. Bronze, Silver, and Gold are priced at $9.95, $24.95, and $49.95 per month on monthly billing, or $95.40, $239.40, and $479.40 per year. Those plans add research tools, charts, and in-app CSV downloads. They do not add an API: Yahoo's plan page says no developer plan or API access is offered and asks interested users to register interest instead. A paid Yahoo plan therefore does not change the legal or technical position of a script that calls Yahoo endpoints.

FXMacroData publishes self-serve plans. Always Free gives keyless USD data at 100 requests/day with USD announcements delayed 15 minutes. Individual is $50/month or $500/year with a 14-day trial, 1,000,000 requests/month, bursts of 300/minute, 5,000/hour, and 20 concurrent requests. 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, and a self-serve Commercial Redistribution add-on costs $10/month per block of up to 100 measured users or 1,000 public-feed followers.

yfinance library

$0

Open-source, unofficial. No SLA, no published limits, no data licence; the README points users to Yahoo's terms and personal use.

Yahoo Finance Gold

$49.95/mo*

Monthly billing ($479.40/year billed yearly*). Research tools and CSV downloads in the app. No API access.

FXMacroData Individual

$50/mo

14-day trial, 1,000,000 requests/month, REST, SSE, GraphQL, MCP, 22 currencies of official macro data. Always Free USD tier below it.

Takeaway: At almost the same monthly price as Yahoo Finance Gold, FXMacroData Individual includes the thing Gold does not: a documented API you are licensed to call from code.

Monthly list price, USD

FXMacroData in mint; Yahoo Finance plans in cyan. None of the Yahoo plans include API access. Hover a bar for the exact price.

Takeaway: The price gap between Yahoo Finance Gold and FXMacroData Individual is five cents; the difference is that only one of them is an API product.

Side-By-Side Comparison

* Competitor pricing retrieved from Yahoo Finance's public plan page in October 2026.

Official API Versus Unofficial Scraper

The most important difference is structural. Yahoo does not publish a supported public API for Yahoo Finance. yfinance works by calling the same endpoints the Yahoo Finance website uses, handling cookies and session tokens, and reshaping the responses into DataFrames. The maintainers do impressive work keeping it running, but when Yahoo changes an endpoint, adds bot protection, or tightens throttling, every script built on it is exposed at the same moment. The yfinance issue tracker shows this pattern repeatedly, including a run of YFRateLimitError('Too Many Requests') reports in 2025 that persisted across several releases.

FXMacroData is the opposite arrangement. The API is the product. Endpoints are versioned under /v1/, described in OpenAPI, documented in the API reference, and governed by published limits. If you are paying for a plan, an outage or a schema change is the provider's problem to fix and communicate, not something you discover from a failing cron job.

Two data paths into your code

yfinance path

Your script → yfinance → undocumented Yahoo web endpoints (cookies, crumb tokens, throttling) → DataFrame. Upstream changes break every user at once; terms limit use to personal, non-automated contexts.

FXMacroData path

Official statistics agency or central bank → FXMacroData normalised release row with source and timestamp → documented REST, SSE, GraphQL, or MCP → your system, under a plan that licenses the use.

What changes for you

Fewer silent breakages, published limits you can engineer against, provenance you can cite, and a clear answer when someone asks whether you are allowed to use the data.

Takeaway: yfinance is a convenient bridge to a website; FXMacroData is a contracted data service. That difference matters more as the workflow becomes automated.

Terms Of Use And Licensing

Traders often skip this section, so it is worth stating plainly. Yahoo's Terms of Service prohibit accessing or collecting data from its services by automated means such as scrapers or data-extraction tools without Yahoo's express prior permission. They also bar using data from the services to build a database, data feed, or widget that substitutes for Yahoo's services, and state that, unless expressly allowed, the services may not be reused for any commercial purpose. The yfinance README repeats the practical conclusion: refer to Yahoo's terms, and treat the data as intended for personal use.

That does not make every notebook experiment a problem, and this article is not legal advice. It does mean that a fund research pipeline, a signal service, a broker widget, a SaaS dashboard, or an AI product sitting on yfinance has a licensing question with no clean answer. FXMacroData's plans exist precisely for programmatic use, and commercial display to an audience is covered by the self-serve Commercial Redistribution add-on rather than a negotiation.

FX Prices And Macro Coverage

Most FX traders meet yfinance through tickers such as EURUSD=X or JPY=X. For quick daily charts of EUR/USD or USD/JPY, that is genuinely convenient. yfinance also exposes Yahoo's economic events calendar through Calendars.get_economic_events_calendar(), which returns events with country, event time, period, actual, market expectation, prior, and revised values as a DataFrame.

What it does not provide is a macro dataset in the sense a systematic FX workflow needs: indicator-level release histories normalised across countries, source attribution to the publishing agency, and a stable schema per series. FXMacroData covers 22 currencies (USD, EUR, GBP, JPY, AUD, CAD, CHF, NZD, BRL, CNH, CNY, DKK, HUF, ILS, KRW, MYR, NGN, NOK, PEN, SEK, THB, TWD) and 700+ indicator series: policy rates, CPI and core CPI, GDP, non-farm payrolls, unemployment, PMIs, retail sales, trade, current account, and wages, sourced from official statistics agencies and central banks. Around that sit FX spot rates, CFTC COT positioning, government bond yields, commodities, central-bank press releases from the Federal Reserve, ECB, Bank of Japan, and Bank of England, and FX session context.

Release Timing And Timestamps

For event-driven FX work, the time a number became public matters as much as the number. FXMacroData stores a second-level announcement_datetime on every release row, and releases are typically available within seconds of official publication. The target is one second from publication, and FXMacroData publishes the measured record at /release-speed, showing the share of releases available within one second by source and listing every release that took longer.

Yahoo's calendar is a display product. It shows a scheduled event time and fills in actuals, but Yahoo does not publish how quickly actuals appear, and a scraper polling a web page adds its own delay and throttling risk. For a discretionary trader glancing at the week ahead, that is fine. For an event study measuring GBP/USD moves in the minutes after a UK CPI print, or an alert that must fire on the release, it is not.

Use case: trading US payrolls on AUD/USD

1. Before the release

Pull the schedule from /v1/calendar/usd and prior prints from the announcements endpoint. yfinance can show the calendar row too, without a delivery commitment.

2. At publication

FXMacroData pushes the release over SSE, typically within seconds, stamped with the official publication time. A scraper must poll a web page and hope it is not throttled.

3. After the release

Join the timestamped row to AUD/USD price action, yields, and positioning. yfinance price bars are still useful here for quick charting.

Takeaway: The release moment is where an unofficial scraper is weakest and a timestamped official feed is strongest.

Reliability And Rate Limits

yfinance does not publish request limits because Yahoo does not publish them. In practice users report HTTP 429 responses after bursts of downloads, temporary IP blocks, and periods where cookie or crumb handling breaks until a new library release ships. Common workarounds are sleeps between batches, caching, and rotating sessions, all of which are engineering time spent defending against a source that never promised availability.

FXMacroData publishes the numbers: paid plans include 1,000,000 requests/month with bursts of 300/minute, 5,000/hour, and 20 concurrent requests, and the free tier allows 100 requests/day. You can size a backtest or a polling loop against those limits before writing it, and streaming over SSE removes the need to poll for new releases at all.

API Example

An FXMacroData request sends the API key in the X-API-Key header. Pulling US payrolls looks like this:

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

Example response (abridged, values illustrative):

{
  "currency": "USD",
  "indicator": "non_farm_payrolls",
  "data": [
    {
      "date": "2026-08-01",
      "val": 142.0,
      "prior": 114.0,
      "pct_change": null,
      "announcement_datetime": 1788525000
    }
  ]
}

Fields that matter

• date is the reference period the release describes.
• val and prior support surprise and revision analysis.
• announcement_datetime is the publication time in epoch seconds.

Compared with a yfinance DataFrame

The yfinance calendar returns a scheduled time per event from a web table. FXMacroData returns the official publication second per release, with the same shape across all 22 currencies.

Takeaway: One documented schema with a publication timestamp is what turns a calendar entry into a joinable event for backtests and alerts.

Where yfinance Is Genuinely Stronger

yfinance earned its popularity, and for many jobs it remains the right first tool:

• Zero cost and zero signup. pip install yfinance and one line of Python returns years of daily prices.
• Asset breadth. Equities, ETFs, indices, mutual funds, crypto, FX, options chains, and company fundamentals in one library, far wider than a macro-focused API.
• Notebook ergonomics. Results arrive as pandas DataFrames, ideal for teaching, exploration, and quick charts.
• Community. A large, active open-source project with many examples, tutorials, and answered questions.

If the task is a personal study of equity returns or a one-off chart of a currency pair, yfinance is hard to beat on convenience.

Where FXMacroData Is Stronger

FXMacroData is stronger wherever the data has to be dependable and defensible: macro releases from official sources with provenance, second-level timestamps and a public speed record, published rate limits, a licence for programmatic and commercial use, and FX-specific context such as COT, yields, central-bank communications, and pair dashboards. It also connects directly to AI tooling through the official MCP server, which matters for teams building AI-assisted trading research.

FXMacroData pros

• Official-source macro data across 22 currencies.
• Second-level timestamps and a public release-speed record.
• Documented API, published limits, licence for programmatic use.

FXMacroData tradeoffs

• Non-USD data needs a paid plan after the trial.
• Focused on FX macro, not single-stock prices or fundamentals.
• Requires an API key for anything beyond the free USD tier.

yfinance pros

• Free and open source.
• Very broad multi-asset price coverage.
• Fast to start in Python notebooks.

yfinance tradeoffs

• Unofficial; not affiliated with or supported by Yahoo.
• Yahoo's terms restrict automated and commercial use.
• Unpublished throttling and periodic breakages.

Takeaway: yfinance is a strong exploration tool with weak guarantees; FXMacroData is a narrower but contracted macro data service built for automation.

Decision Matrix

Recommendation

Keep yfinance for what it does well: free, quick, personal exploration of prices across many asset classes. Do not build a production macro workflow on it. When the job involves official economic releases, exact publication times, scheduled automation, a team, or anything customer-facing, the absence of an official API, the restrictions in Yahoo's terms, and unpublished throttling all become real costs.

FXMacroData is built for that job. Start keyless on the free USD tier, check the measured release-speed record, read the API reference, and compare plans; Individual at $50/month comes with a 14-day trial and unlocks all 22 currencies, including the ECB policy rate and the rest of the euro-area calendar.

Bottom line: yfinance is a free, unofficial convenience layer over a website that never promised an API. FXMacroData is a licensed, documented, official-source FX macro API with second-level timestamps and published limits, at roughly the price of a Yahoo Finance Gold subscription that includes no API at all.

Takeaway: Prototype wherever you like; put official, licensed data under anything that trades, alerts, or ships.

Sources Checked

Claims about yfinance and Yahoo Finance are based on the public pages below, checked in October 2026. Where a figure is not published, this page says so instead of estimating it.

yfinance README

Not-affiliated disclaimer, research and educational purpose, personal-use note, Apache-2.0 licence.

View source

yfinance Calendars reference

Economic events calendar method and its parameters.

View docs

Yahoo Terms of Service

Automated collection, substitute data feeds, and commercial-use restrictions.

View terms

Yahoo Finance plans

Bronze, Silver, Gold pricing and the note that no API or developer plan is offered.

View plans

Yahoo economic calendar

Event, country, event time, actual, expectation, prior, and revised columns.

View calendar

yfinance rate-limit reports

Example issue documenting YFRateLimitError Too Many Requests.

View issue

FXMacroData pricing and docs

Plans, limits, trial, Commercial Redistribution, and API reference.

View pricing

Takeaway: Every yfinance and Yahoo claim on this page traces to a public README, reference page, terms document, plan page, or issue.

Related Reading

• FXMacroData vs Alpha Vantage for a comparison with a free-tier market data API that does publish an official API.
• Best economic indicator feeds for algo trading for a wider survey of macro feeds.
• FXMacroData vs Twelve Data for another price-first API compared with an FX macro layer.
• How to use MetaTrader 5 Python with FXMacroData to wire release data into a trading terminal.