Import Data in TradingView: Chart Series, Portfolios and Datafeeds
“Import data into TradingView” can mean three different tasks: displaying an external series in Supercharts, importing portfolio transactions, or supplying a datafeed to a chart embedded on your own website. These workflows are not interchangeable.
Choose the Right Workflow
| Goal | Relevant approach |
|---|---|
| Analyze a series already supported by TradingView | Symbol search and supported Pine request.* functions |
| Plot a few static reference values | Explicitly encode permitted values and their availability timestamps in a script |
| Import transaction records | TradingView Portfolios' transaction import |
| Display your own OHLC database on your website | A separate chart-library integration with your datafeed |
The standard Pine environment is not a general local-file reader or arbitrary HTTP client. Do not expect a CSV on your computer or a subscription to an unrelated provider to become a new Supercharts symbol automatically.
Supported Sources and Static Values
TradingView documents supported requests in Other timeframes and data. Check the current function, provider and symbol coverage before relying on an old tutorial's Quandl code. This guide does not verify the old QUANDL:CHRIS/CME_CSC1 example or claim that buying a provider subscription enables it.
For a small static dataset, a script can encode values explicitly. Record each value's source, units and the timestamp when it actually became available. Using the period-end date for information published later can introduce lookahead bias. Updating those values requires updating the source; it is not live CSV ingestion.
Pine Seeds is another documented user-maintained data mechanism. Check its current repository-creation availability and feed maintenance before designing a new workflow around it. An example feed may not be regularly updated.
Import Portfolio Transactions
For transaction history, open the relevant Portfolio, then its Transactions section and the import control. Use the sample file supplied by the interface. TradingView's transaction-import guide lists fields including Symbol, Side, Qty, Fill Price, Commission and Closing Time.
Review whether the import merges records or replaces the full transaction history. Compare transaction counts and totals afterward. This records portfolio activity; it does not upload a new candle series or alter a broker's actual transactions.
Supply Data to Your Own Embedded Chart
TradingView's Advanced Charts Datafeed API is for an application you build separately. Its JavaScript methods include configuration, symbol resolution, historical bars and realtime subscriptions. You supply the data and must meet the library's access and licensing requirements.
Before integrating a CSV or database, define symbol metadata, price precision, session, timezone and supported resolutions. Return bars in chronological order and handle missing history and live updates consistently. A rendering library is not a bundled market-data license, and this API does not import data into your personal TradingView account.
Pineify can help draft Pine calculations for data that Pine can access. It cannot make an unsupported file or external endpoint available merely by generating code.
Can I upload any CSV as a Supercharts price symbol?
Do not assume so. Portfolio transaction import, embedded charts and supported Pine data requests solve different tasks.
Does transaction import create historical candles?
No. It adds portfolio records for supported instruments.
Can a website datafeed API run inside Pine?
No. The JavaScript Datafeed API belongs to a separate chart-library integration, not the Pine runtime.