Collect TipRanks analyst and market data through one API request
Send a TipRanks ticker or analyst URL to a managed scraping endpoint and receive rendered HTML, Markdown, screenshots or structured JSON.
The service handles JavaScript execution, proxy rotation and common bot checks so your code can focus on ratings, fundamentals and insider activity.
What to collect and how to choose the output
Three recurring jobs fit this endpoint well. First, consensus tracking: gather buy, hold and sell signals together with price targets for a watchlist. Second, company context: pair each ticker with market capitalization, sector and industry so research can be segmented. Third, insider monitoring: record transaction date, role, share count and value to spot changes over time. A practical checklist before a run: confirm the URL is a public ticker or analyst page, decide whether you need raw rendered HTML or parsed fields, choose selector rules for stable layouts or AI rules for faster setup, and estimate credit use if JavaScript or stealth routing is enabled.
Four-step workflow
Create an account to obtain an API key, install the client for your stack, then send a GET request containing a TipRanks URL. The renderer loads the page, rotates proxies as configured and returns rendered HTML ready for parsing. When a page needs more than a basic fetch, add parameters for JavaScript rendering, stealth proxy handling, country targeting or AI extraction rules. Code examples are described for Python, Node.js, Ruby, PHP, Go and cURL, and a dashboard request builder can be used to test a URL before writing code.
Outputs beyond raw HTML
Beyond plain HTML, the endpoint supports several output styles. AI extraction lets you describe desired fields in natural language instead of maintaining selectors. Screenshots show how the page appears in a browser, which helps debug missing content. Markdown output is convenient for feeding page text into language-model summaries. JavaScript scenarios can click, scroll or wait for dynamic sections, and a no-code automation option can schedule ratings or earnings monitoring without writing a scraper. Use screenshots and scenarios when content appears only after interaction; use Markdown when the goal is summarisation; use structured rules when downstream systems need consistent fields.
Reliability, scale and privacy notes
Proxy rotation and browser rendering reduce IP-based blocking by mimicking ordinary browsing behaviour. The platform is described as scaling across many browsers and proxies during traffic spikes, with fast results even on JavaScript-heavy pages. For privacy, the service states it does not collect or store personal data from scraped sites unless explicitly requested. Before production use, validate success rate, latency and field completeness on your own ticker list, because page layouts and access controls can change.
Pricing and credit planning
Commercial terms are not asserted here. Confirm current plan prices, monthly credit allowances, concurrency limits, trial credits, VAT treatment and cancellation terms with the owner before publishing or purchasing. Credit consumption also depends on the options selected, so budget separately for basic requests, JavaScript rendering, premium proxies and stealth proxy use.
| Workflow | Fields to request | Useful output |
|---|---|---|
| Analyst consensus | Ratings, price targets, buy/hold/sell consensus | Structured JSON for watchlist comparison |
| Company fundamentals | Market cap, sector, industry, ticker details | Structured JSON for equities research segmentation |
| Insider activity | Transaction date, insider role, share count, transaction value | Structured JSON for smart-money tracking |
Fields are those described as available from public TipRanks pages; confirm layout coverage on your target URLs before production use.
| Parameter | Purpose | Choose it when |
|---|---|---|
| render_js | Enable JavaScript rendering | Ratings or fundamentals load dynamically |
| stealth_proxy | Use stealth proxy handling | Standard rendering encounters CAPTCHA or blocking |
| country_code | Set geographic targeting | Regional page variants matter |
| extract_rules | Map CSS selectors to fields | Layout is stable and precision matters |
| ai_extract_rules | Describe fields in natural language | Fast setup or changing layouts |
Parameter names are preserved from the described API workflow; exact request syntax must be confirmed against current documentation before implementation.
Frequently asked questions
Do I need a TipRanks account to use this?
No separate TipRanks login is needed. You use an API key from the scraping service, then send the public TipRanks URL you want to fetch.
Is collecting public TipRanks pages allowed?
Public pages are generally accessible, but you should check TipRanks' terms before running a job and stay away from content that requires sign-in.
Which TipRanks fields can be collected?
Anything visible on a public page can be targeted, including ratings, targets, consensus, market cap, sector, industry and insider activity. Selector-based rules or AI extraction rules can turn that rendered content into structured fields.
How do I receive structured JSON?
Map CSS selectors to field names with extract_rules, or describe the fields in natural language with ai_extract_rules. Either approach returns parsed JSON rather than raw markup alone.
Which languages and SDKs are supported?
Any language that can make an HTTP request works. SDKs and examples are described for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL is also supported.
What does a TipRanks run cost?
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.