Finviz Stock Screener & Fundamentals | 83 fields | No API key

For quant analysts, screeners, and AI agents that want Finviz.com's fundamentals and technicals table as structured data — without copy-pasting from the site or paying for Finviz Elite.

No API key required. No login. $2.00/1,000 quote records · $1.00/1,000 screener rows (Pay Per Event). Every record includes parse_confidence (0.0–1.0) and warnings.

---

What data you get

Quote mode — 83-field fundamentals/technicals snapshot per ticker

One record per symbol, lifted from Finviz's snapshot-table2 (the same table shown on finviz.com/quote.ashx?t=<SYMBOL>):

• Identity: symbol, name, sector, industry, country
• Valuation: market_cap, enterprise_value, p_e, forward_p_e, peg, p_s, p_b, p_fcf, ev_ebitda, ev_sales
• Profitability: roa, roe, roic, gross_margin, oper_margin, profit_margin
• Growth: eps_this_y, eps_next_y, eps_next_5y, eps_past_3_5y, sales_past_3_5y, eps_q_q, sales_q_q
• Ownership: insider_own, insider_trans, inst_own, inst_trans, short_float, short_ratio
• Technicals: beta, rsi_14, atr_14, sma20, sma50, sma200, 52w_high, 52w_low, rel_volume, avg_volume, volume
• Performance: perf_week … perf_10y
• Price: price, prev_close, change, target_price, recom
• …and ~40 more (dividends, EPS surprise, debt ratios, employees, IPO date). See src/normalize.py::SNAPSHOT_FIELDS for the full canonical list.

Screener mode — preset signal screens

One record per matching ticker: symbol, name, sector, industry, country, market_cap_screener, pe_screener, price_screener, change_screener, volume_screener, rank, signal.

---

Access path & compliance (read this before using filters)

Both endpoints are server-rendered HTML, no Cloudflare/JS challenge — fetched with curl_cffi browser-TLS impersonation, no browser or residential proxy required (verified live 2026-07-15).

• quote.ashx (quote mode) is fully clean: finviz.com/robots.txt does not restrict it at all.
• screener.ashx (screener mode) is restricted: robots.txt has a blanket Disallow: /screener?*, but then explicitly Allow:-lists ~32 named preset "signal" screens (top gainers/losers, new highs/lows, overbought/oversold, unusual volume, chart patterns, insider trades, analyst up/downgrades, earnings timing, major news). This actor's signal input uses exactly that allow-listed set — screener mode with signal set is 100% robots.txt-compliant.
• The filters input (raw Finviz filter string, e.g. sec_technology,cap_large) is exposed as an opt-in advanced option. It is technically served by the site (HTTP 200) but falls outside the robots.txt allow-list for /screener. The actor logs a warning when used. Left blank by default — you must explicitly set it.

This is a deliberate, disclosed trade-off: rather than silently building an unrestricted custom-filter screener (matching some competing Finviz scrapers) or refusing to build screener mode at all, the default path (signal) stays inside the site's own declared policy, and the wider capability is there for buyers who choose to use it.

---

Input

Field	Mode	Description
mode	both	quote or screener
symbols	quote	Ticker list, e.g. ["AAPL","MSFT"]
signal	screener	One of 32 robots.txt-allowed presets, e.g. ta_topgainers
filters	screener	Advanced, opt-in raw filter string — see compliance note above
view	screener	Finviz view id (default 111 Overview); ignored when signal is set
maxItems	screener	Max rows to return, paginated 20/page

Output example (quote mode, abridged)

{
  "symbol": "AAPL",
  "name": "Apple Inc",
  "sector": "Technology",
  "industry": "Consumer Electronics",
  "country": "USA",
  "price": 314.86,
  "market_cap": 4624460000000.0,
  "p_e": 38.09,
  "eps_ttm": 8.27,
  "roe": 141.47,
  "mode": "quote",
  "scraped_at": "2026-07-15T10:00:00Z",
  "parse_confidence": 1.0,
  "warnings": []
}

Edge cases

• Unknown/delisted ticker: the record is still pushed with warnings: ["fetch_failed"], parse_confidence: 0.0, all data fields null. Not charged for failed quote fetches beyond the base record.
• ETF / fund tickers: many equity-only fields (P/E, EPS, margins) are legitimately absent on Finviz for ETFs — those come back as null, not an error.
• Empty screener result: returns zero rows with totalItems: 0 in OUTPUT, not an error.
• Rate limiting (HTTP 429): retried with exponential backoff (up to 3–4 attempts); persistent 429 surfaces as a run-level error in OUTPUT.

Known limitations

• Screener mode's field set (11 columns: ticker/company/sector/industry/country/market cap/P-E/price/change/volume) is the Overview view only — Finviz has richer views (Valuation, Financial, Ownership, Technical) selectable via view, but only Overview's column layout is currently parsed. Switch to quote mode on the resulting tickers for the full 83-field detail.
• No historical/intraday price data (that's Yahoo Finance Scraper's history mode in this fleet, not Finviz's).

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.