Yahoo Finance Scraper — Live Quotes & Stock History avatar

Yahoo Finance Scraper — Live Quotes & Stock History

Pricing

from $0.86 / 1,000 live stock quotes

Go to Apify Store
Yahoo Finance Scraper — Live Quotes & Stock History

Yahoo Finance Scraper — Live Quotes & Stock History

Scrape live stock quotes and historical OHLCV price data from Yahoo Finance. Supports stocks, ETFs, crypto, indices, and forex. Two modes: quote (real-time price snapshot for up to 100 symbols) and history (OHLCV bars with adjustable interval and range). No API key required. Pay per result.

Pricing

from $0.86 / 1,000 live stock quotes

Rating

5.0

(1)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

1

Bookmarked

101

Total users

27

Monthly active users

13 days ago

Last modified

Categories

Share

Yahoo Finance Scraper — Stocks, ETFs & Crypto | No API Key | from $1.50/1K

For quant analysts, portfolio trackers, and AI agents that need structured stock and crypto price data — without a $599/year Bloomberg terminal or a $25/month Yahoo Finance API subscription.

No API key required. No Yahoo Finance account. $1.50/1,000 quote snapshots · $0.50/1,000 OHLCV bars (Pay Per Event). Every record includes parse_confidence (0.0–1.0) and warnings. Symbols that fail to resolve are not charged.

Scrape live stock quotes and historical OHLCV price data from Yahoo Finance — stocks, ETFs, cryptocurrencies, market indices, and forex pairs, all in one actor. No API key, no authentication, no proxy required. Two modes cover the full financial data workflow: real-time snapshots and bar-level history for any date range. Pay per result.

Whether you need the current price of AAPL, 10 years of daily BTC-USD closes, or a 1-minute intraday chart for SPY, this actor delivers clean structured records at $1.50 per 1,000 results.


What data you get from Yahoo Finance

Quote mode — real-time price snapshot

One record per symbol with:

  • regular_price, prev_close, open, day_high, day_low
  • volume, market_cap, price_change_pct
  • fifty_two_week_high, fifty_two_week_low
  • trailing_pe, forward_pe, dividend_yield
  • market_state — REGULAR / PRE / POST / CLOSED
  • quote_type — EQUITY / CRYPTOCURRENCY / INDEX / ETF
  • name, symbol, currency, exchange
  • timestamp — ISO 8601 UTC quote time

History mode — OHLCV bars

One record per bar with:

  • date (YYYY-MM-DD for daily bars; ISO timestamp for intraday)
  • open, high, low, close, adj_close (split/dividend adjusted), volume
  • symbol, currency, mode

All records include parse_confidence (0.0–1.0) and warnings.


Supported symbol types

TypeExamples
US equitiesAAPL, MSFT, GOOGL, TSLA, NVDA
ETFsSPY, QQQ, VTI, GLD, TLT
CryptoBTC-USD, ETH-USD, SOL-USD, BNB-USD
Indices^GSPC (S&P 500), ^DJI (Dow), ^IXIC (Nasdaq)
ForexEURUSD=X, GBPUSD=X, USDJPY=X
InternationalASML.AS, 7203.T, BABA

How to use

Get live quotes for multiple symbols

{
"mode": "quote",
"symbols": ["AAPL", "MSFT", "GOOGL", "BTC-USD", "^GSPC"]
}

Get 1-year daily OHLCV history

{
"mode": "history",
"symbols": ["AAPL", "TSLA"],
"range": "1y",
"interval": "1d"
}

Get max historical daily closes for crypto

{
"mode": "history",
"symbols": ["BTC-USD", "ETH-USD"],
"range": "max",
"interval": "1d"
}

Intraday 5-minute bars (last 60 days)

{
"mode": "history",
"symbols": ["SPY", "QQQ"],
"range": "60d",
"interval": "5m"
}

Input parameters

FieldTypeDefaultDescription
modestringquotequote or history
symbolsstring[]requiredTicker symbols (e.g. ["AAPL", "BTC-USD", "^GSPC"])
rangestring1yHistory range: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max
intervalstring1dBar interval: 1m, 2m, 5m, 15m, 30m, 60m, 90m, 1h, 1d, 1wk, 1mo

Interval / range compatibility

IntervalMax range
1mlast 7 days only
2m–90mlast 60 days
1hlast 730 days
1d, 1wk, 1momax (full history)

Output schema

FieldTypeMode
symbolstringboth
namestringquote
quote_typestringquote
currencystringboth
exchangestringboth
regular_pricefloatquote
prev_closefloatquote
openfloatboth
day_high / day_lowfloatboth
volumeintegerboth
market_capfloatquote
price_change_pctfloatquote
fifty_two_week_high / lowfloatquote
trailing_pe / forward_pefloatquote
dividend_yieldfloatquote
market_statestringquote
timestampstringquote
datestringhistory
closefloathistory
adj_closefloathistory
modestringboth
scraped_atstringboth
parse_confidencefloatboth
warningsarrayboth

Why this beats competitors

Data sourceCostCoverageRequires account?
This actor$1.50/1K quotes, $0.50/1K barsstocks, ETFs, crypto, forex, indicesNo
Yahoo Finance API (official)$25–599/mosameYes + billing
Polygon.io$29–199/moUS equities onlyYes
Finnhub$0/mo free tier (limited)limited symbolsYes
Alpha Vantage$50/moUS stocksYes

Yahoo Finance's official API (YF Data API) costs $25–$599/month. This actor:

  • Uses Yahoo Finance's public endpoints — no API key, no registration
  • Accesses Yahoo Finance's public endpoints reliably from Apify cloud
  • Handles the crumb/cookie auth handshake automatically for quote mode — zero manual steps
  • Returns parse_confidence on every record — you know what to trust
  • Broad symbol support — stocks, ETFs, crypto, indices, forex, international tickers
  • PPE pricing — $1.50/1,000 quote records, $0.50/1,000 history bars, nothing for symbols that fail

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 live stock prices, historical OHLCV data, ETF quotes, or crypto prices mid-conversation — e.g. "what is AAPL's current price?", "show me the last year of daily closes for BTC-USD".

Point your MCP client at this tool:

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

Minimal input an agent can send:

{ "mode": "quote", "symbols": ["AAPL", "BTC-USD", "^GSPC"] }

Notes on edge cases

  • Index symbols (^GSPC, ^DJI) often have null volume — this is a Yahoo Finance limitation.
  • Crypto (BTC-USD) may have null market_cap in quote mode depending on market hours.
  • Intraday intervals (1m–90m) have limited history — use 1d for long-range data.
  • Pre/post market bars available in history mode via the includePrePost flag.

FAQ

Does it need a Yahoo Finance account or API key? No. Both the quote and history endpoints are public. Quote mode performs an automated crumb/cookie handshake — no manual steps required.

Can it fetch multiple symbols at once? Yes. Quote mode supports up to 100 symbols per run. History mode fetches one symbol at a time (per Yahoo's endpoint design) and batches automatically.

Does it work for international stocks? Yes. Append the exchange suffix — e.g. ASML.AS (Amsterdam), 7203.T (Tokyo). Coverage depends on Yahoo Finance's data licensing.

What is adj_close? The adjusted close price, corrected for stock splits and dividend payments. Use this for accurate long-term return calculations.


Pricing example

Pay per result (PPE). Charged per record pushed. Symbols that fail to resolve are not charged.

FetchRecordsCost
Live quote for 5 stocks5~$0.008
Live quotes for 50 stocks + ETFs50~$0.075
1 year daily OHLCV for 1 symbol~252 bars~$0.13
5 years daily OHLCV for 10 symbols~12,600 bars~$6.30
Intraday 5m bars, 30 days, 3 symbols~11,700 bars~$5.85

Integrations

Built for quant analysts and portfolio trackers feeding stock, ETF, and crypto price data into models without a paid data subscription — 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.

Not affiliated with Yahoo Finance or Yahoo Inc. This actor uses publicly accessible endpoints. Use responsibly.

Also in this finance family

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

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.