Finviz Fundamentals and Earnings API
Collect quotes, fundamentals, analyst ratings and earnings information from Finviz ticker and analyst pages through one API call, choosing structured JSON or rendered HTML for your pipeline.
What to collect and why
Three recurring jobs cover most teams: reading screener results, checking insider stakes, and reviewing analyst views for covered tickers. A ticker page can also supply price, P/E, EPS, dividend, market cap, institutional ownership and earnings-calendar entries. Decide first which dataset you need, because that choice determines whether rendered HTML or structured JSON is the cleaner output.
A practical four-step workflow
- Create an account and retrieve an API key. 2. Install the SDK for your stack, or use the dashboard builder to test a request without code. 3. Send a GET request with an API key and a Finviz URL. 4. Add parameters only when needed: render_js for JavaScript, stealth_proxy for CAPTCHA pressure, country_code for location-specific routing, and ai_extract_rules for natural-language extraction into structured JSON. Code samples are described for Python, Node.js, Ruby, PHP, Go and cURL. Budget note to confirm with the owner: API credits are valid for one month and don't roll over, and requests start at 1 credit each; concurrency is the number of requests that can be sent at the same time.
Choosing the right output mode
Use ai_extract_rules when you want fields such as ticker price, fundamentals, insider ownership and analyst ratings returned as structured JSON from a natural-language specification. Use screenshots for visual verification, JavaScript scenarios when content appears after clicking, scrolling or waiting, and Markdown or plain-text output when downstream processing benefits from a simpler format. An n8n workflow can automate screener and equity-data monitoring without writing scraper code. A separate Google Search route pulls Finviz-related results from search pages into structured output, which suits discovery and coverage checks rather than ticker-level fundamentals. For structured extraction, CSS or XPath extraction rules can target exact elements alongside full-page screenshots, and team management can invite multiple users with a custom quota of credits and concurrency.
Blocking, compliance and performance checks
Proxy rotation and headless-browser rendering reduce IP-based blocking risk by mimicking ordinary browsing. Before relying on either, check the current compliance documentation and any data-handling terms that apply to your use case, and confirm whether personal data is collected or stored unless a user explicitly requests it. For performance, treat response time and accuracy as things to measure on your own target pages rather than fixed promises: run a small sample of Finviz ticker and screener URLs, record success rates and latency, and compare rendered HTML against structured output. Geotargeting routes requests through 200+ countries and territories, or 40+ on classic proxies.
| Need | Best starting option | Key parameter or output |
|---|---|---|
| Dynamic page content | JavaScript rendering | render_js |
| Aggressive blocking or CAPTCHAs | Stealth proxy routing | stealth_proxy |
| Location-dependent content | Geo-targeted request | country_code; 200+ countries and territories (40+ on classic proxies) as captured |
| Fields without hand-written selectors | AI extraction rules | ai_extract_rules structured JSON |
| Exact elements without AI | CSS/XPath extraction rules | Targeted structured fields |
| Visual check | Screenshot capture | Full-page image |
| Finviz data via search results | Google Search results extraction as captured | Search-result data; captured description only, confirm before use |
Decision aid based on described capabilities; confirm current implementation, credit validity, geotargeting coverage and team quotas before publication.
Frequently asked questions
How do I start scraping Finviz?
Create an account, obtain an API key, then send a GET request containing the target URL. The service renders the page, rotates proxies and returns the collected data. Trial credit terms vary by provider and plan, so check the current signup page or account dashboard for the exact allowance before you start a large run.
Will I get blocked when scraping Finviz?
Residential proxy rotation and a real headless browser make requests resemble ordinary traffic. When a target responds aggressively, enable stealth_proxy on the request.
Can I scrape Finviz without writing code?
Yes. A dashboard request builder accepts a URL and parameters, then produces a ready snippet in Python, Node, Go, PHP, Ruby or cURL.
How do I handle JavaScript when scraping Finviz?
Set render_js=true. The page runs in a real headless browser on the server side and the post-render HTML is returned for parsing.
Can I scrape Finviz from a specific country?
Yes. Supply country_code to route the request through a residential IP in the chosen country, which helps when page content differs by location.
What is the rate limit for scraping Finviz?
Limits are based on plan concurrency rather than a per-target rate limit. Concurrency means the number of requests that can be sent at the same time. Space requests out or use multiple sessions if the target throttles aggressive patterns.