What the API does and who it is for
Yahoo Finance Real Time packages the full breadth of publicly visible Yahoo Finance data into a structured REST interface. If you can see it on finance.yahoo.com — a stock's summary page, SEC filings, earnings history, options chain, ESG ratings, or the day's top movers — you can pull it programmatically through this API.
The intended audience is broad: indie developers building portfolio trackers or stock screeners, fintech startups that need market data without negotiating a Bloomberg or Refinitiv contract, and data engineers who want to backfill historical series or capture real-time ticks. Because it mirrors a public consumer site rather than a premium exchange feed, the data carries caveats (discussed below), but for many use cases it is entirely sufficient.
Endpoint walkthrough
The 48 endpoints fall into three logical groups.
Market-level data
The nine /market/ endpoints cover aggregate market health. /market/get-summary returns a live regional market summary — useful as a dashboard header. /market/get-movers streams the day's gainers, losers, and most-active tickers, which is a natural data source for a trending-stocks widget. /market/get-trending-tickers pairs with /market/get-spark to provide the miniature sparkline charts Yahoo Finance renders alongside trending names. The watchlist endpoints (get-popular-watchlists, get-watchlist-details, get-watchlist-performance) let you replicate curated lists or track performance of themed baskets without managing your own universe.
Per-ticker stock data
The bulk of the surface area — roughly 30 endpoints — lives under /stock/. These endpoints decompose a ticker page into its constituent sections:
- Price and quotes:
get-quote-summary,get-chart,get-timeseries,get-statisticscover everything from the headline price to quarterly data series. - Fundamentals:
get-financials(income statement),get-balance-sheet,get-cashflow, andget-earningsdeliver the standard three-statement model plus earnings history. - Ownership:
get-major-holders,get-holders,get-insider-transactions, andget-insider-rosterexpose institutional and insider data that is otherwise tedious to scrape. - Analyst views:
get-analysis,get-recommendation-trend,get-upgrades-downgrades, andget-insightssurface sell-side signals without requiring individual brokerage data agreements. - ESG:
get-esg-scores,get-esg-peer-scores, andget-esg-chartare increasingly important for sustainable-finance applications and are rarely available in cheaper data tiers elsewhere. - ETF-specific:
get-fund-profileandget-top-holdingshandle ETF use cases distinctly from individual equities. - Derivatives:
get-optionsandget-futures-chainround out the coverage for more sophisticated trading applications.
Screeners
A single /screeners/get-list endpoint exposes Yahoo Finance's predefined screener filters, which you can use as a starting point for filtering universes without rolling your own criteria.
Pricing breakdown
The freemium model has four tiers:
| Plan | Monthly fee | Requests included | Rate limit | Overage per request |
|---|---|---|---|---|
| BASIC | $0 | 500 | — | — |
| PRO | $10 | 50,000 | 10 / sec | $0.0010 |
| ULTRA | $25 | 300,000 | 10 / sec | $0.0005 |
| MEGA | $180 | 4,000,000 | 10 / sec | $0.0005 |
The BASIC tier is genuinely useful for prototyping — 500 requests is enough to evaluate response shapes and build out your data model before committing to a paid plan. It does not appear to carry a formal rate limit in the data, though practical throttling likely applies.
PRO at $10/month is a reasonable entry point for a live application with modest traffic. Fifty thousand requests per month works out to roughly 1,600 per day, which is adequate for a small portfolio app polling a few dozen tickers every few minutes. If you exceed the quota, overage is billed at $0.001 per request — meaning an extra 10,000 calls costs $10, effectively doubling your bill if you are not careful.
ULTRA is the most cost-efficient paid tier on a per-request basis for moderate-volume workloads. Three hundred thousand requests at $25 is about $0.000083 per request before overage kicks in at $0.0005. A screener that checks 500 tickers across 5 data points three times a day would consume about 2.25 million requests monthly, which pushes you firmly toward MEGA.
MEGA at $180/month and 4 million included requests suits production applications with continuous data refresh — think a financial news aggregator or an institutional-grade screener running on a cron.
Practical use cases
- Portfolio tracker: Combine
get-quote-summaryfor live prices withget-chartfor historical series andget-earningsfor upcoming catalysts. - Stock screener: Use
get-moversandscreeners/get-listto build a starting universe, then enrich each ticker withget-statisticsandget-analysis. - ESG dashboard: Pull
get-esg-scoresandget-esg-peer-scoresto benchmark a company against its sector peers — a feature that is surprisingly hard to source cheaply elsewhere. - Insider activity monitor: Schedule periodic calls to
get-insider-transactionsandget-insider-rosterto surface significant buying or selling by executives. - Earnings calendar app:
get-earningsandget-recommendation-trendtogether give the core data for a pre-earnings briefing tool.
Limitations and things to check before integrating
Latency: The average response time is 817 ms. That is acceptable for user-triggered requests but too slow for tick-by-tick trading automation. This is not an exchange co-location feed — treat it as near-real-time consumer data.
Success rate: The reported average success rate is 93%. A 7% failure rate is non-trivial in production. Build retry logic and graceful degradation from the start; do not assume every call will succeed.
Data provenance: The API surfaces what Yahoo Finance displays, which itself aggregates from exchange data with typical 15-minute delays for equities on some exchanges (unless Yahoo Finance has a direct real-time agreement for a given market). Verify the freshness guarantees for your target instruments before committing to this source for anything latency-sensitive.
Rate limits: All paid plans share a 10 requests-per-second ceiling. If your architecture fires parallel requests — for example, enriching 100 tickers simultaneously at startup — you will need a queue or throttle client-side to stay within bounds.
Terms of use: Because this API proxies Yahoo Finance content, review the terms of service for both the API provider and Yahoo Finance itself before using the data in a commercial product.
Getting started
Subscription and key issuance happen through the RapidAPI marketplace, where the API already has over 3,000 active subscribers. The BASIC tier requires no credit card, so you can start exploring endpoints and inspecting response payloads immediately. Once you understand which endpoints your application actually needs, map your expected daily call volume to a monthly total and pick the tier whose included quota covers it with some headroom — given the 93% success rate, you will want buffer for retries anyway.