tvdata-rs
tvdata-rs is a modern async Rust library for working with TradingView's unofficial data surfaces.
It is designed as a library, not an application framework. The crate gives you:
- high-level facades for common workflows
- low-level scanner access when you need precise field control
- typed models for quotes, fundamentals, analyst data, calendars, and history
- capability-aware validation against live TradingView scanner metainfo
- configurable HTTP and websocket transport with retry support
Why Use tvdata-rs
Most TradingView wrappers fall into one of two buckets:
- thin endpoint wrappers that expose payloads but leave semantics to the user
- convenience helpers that work for a few cases but become limiting for real scanning and research workflows
tvdata-rs aims for a cleaner middle ground:
- ergonomic APIs for the common cases
- low-level access for advanced cases
- typed models instead of ad hoc maps
- a library-first architecture that stays composable inside larger Rust systems
What The Crate Covers
- Screener queries via
scan - Live scanner metainfo via
metainfo - Capability-aware scan validation and filtering
- Symbol search via TradingView
symbol_search/v3 - Economic calendar events
- Market-wide earnings, dividend, and IPO calendars
- OHLCV history over TradingView chart websockets
- High-level
equity(),crypto(), andforex()facades - Equity analyst products, estimate history, and point-in-time fundamentals
- Embedded field registry generated from
deepentropy/tvscreener - Optional
sessionidcookie support for auth-aware HTTP and websocket requests
Installation
Add the crate to your Cargo.toml:
[]
= "0.1.0"
= { = "1", = ["macros", "rt-multi-thread"] }
Start Here
If you are new to the crate, use this rule of thumb:
| Goal | Best entry point |
|---|---|
| Get a quote, fundamentals, analyst data, or a stock overview | client.equity() |
| Work with crypto or FX snapshots and movers | client.crypto() / client.forex() |
| Download OHLCV series | client.history(...) or client.download_history(...) |
| Look up symbols and listing metadata | client.search_response(...) |
| Pull market-wide calendars | client.economic_calendar(...), earnings_calendar(...), dividend_calendar(...), ipo_calendar(...) |
| Build custom screeners | client.scan(...) with ScanQuery |
| Make custom scans safer | client.metainfo(...), validate_scan_query(...), scan_validated(...), scan_supported(...) |
If you only need one thing and want the shortest path, start with the high-level facades first. Drop to the low-level scanner only when you need custom fields or custom filter logic.
Quick Start
use ;
async
Common Workflows
Equity: Quotes, Fundamentals, Analysts
This is the best entry point for stock-oriented workflows.
use *;
async
The equity facade also exposes more specific analyst methods:
analyst_recommendations()price_targets()analyst_forecasts()earnings_calendar()analyst_fx_rates()
And historical analyst / fundamental products:
estimate_history()earnings_history()fundamentals_point_in_time()fundamentals_history()
These historical products use typed FiscalPeriod values and a shared HistoricalObservation<T> model.
Crypto And Forex Snapshots
use *;
async
OHLCV History
Use history(...) for a single series and download_history(...) / history_batch(...) for multiple symbols.
use ;
async
For multiple symbols:
use ;
async
Symbol Search
search_response(...) exposes the richer TradingView v3 search shape, including listing metadata and identifiers such as isin, cusip, and cik_code.
use ;
async
Typed convenience helpers are available for the most common asset classes:
search_equities(...)/search_equities_response(...)search_forex(...)/search_forex_response(...)search_crypto(...)/search_crypto_response(...)search_options(...)/search_options_response(...)
Macro And Corporate Calendars
tvdata-rs exposes both macro events and market-wide corporate calendars.
use ;
async
Custom Screener Queries
Use the low-level scanner when you need exact TradingView fields, custom filters, or a query builder that maps closely to scanner payloads.
use *;
async
Capability-Aware Scans
TradingView field support is not uniform across markets and can drift over time. The crate exposes live metainfo and scan validation to help with that.
Inspect Live Scanner Metainfo
use *;
async
Validate Before Executing
use *;
async
Filter Unsupported Columns For Multi-Market Queries
use *;
async
Configuration
Auth-Aware Sessions
If you have a TradingView sessionid cookie and want auth-aware requests, pass it through the client builder:
use ;
async
Retry And Endpoint Overrides
use Duration;
use ;
async
Design Notes
The crate intentionally separates:
- low-level TradingView payload composition
- transport concerns such as retries, cookies, and websocket framing
- user-facing typed models and high-level facades
It also intentionally does not include:
- built-in storage or database layers
- a crawler / browser automation layer
- a local persistence framework
- a non-Rust runtime or service wrapper
The goal is to stay useful as a clean Rust library that can be embedded into your own application, research pipeline, or service.
Important Caveat
TradingView does not provide a public end-user market data API for this use case. This crate works against unofficial, reverse-engineered surfaces.
That means:
- upstream schemas can change without notice
- field support can drift by market and over time
- rate limits and freshness characteristics are not officially documented
If you depend on a specific field set or scanner behavior, prefer capability-aware flows such as metainfo(...), validate_scan_query(...), and scan_supported(...).
Development
Examples live in examples/ and cover the main product surfaces:
- quotes and facades
- search
- metainfo and capability-aware scans
- history
- macro and corporate calendars
The field registry is embedded so low-level scanner workflows can still operate with a stable local field catalog even when live metainfo is unavailable.
Contributor workflow and quality gates are documented in CONTRIBUTING.md, and release-facing changes are tracked in CHANGELOG.md.