PineScript Verification workflow
Compare a Pine Script API result with TradingView.
Compare a PineScript API backtest with TradingView using the same Pine Script, symbol, timeframe, dates, costs, and execution assumptions.
Start from the same experiment
Two reports are only comparable when their inputs match. Copy the exact Pine Script used by the API result into the TradingView Pine Editor, then align the market, timeframe, date range, input values, initial capital, commission, and slippage.
Comparison checklist
Why results may still differ
Dataset coverage
Two providers may load different history or revise bars at different times.
Session boundaries
Timezone and exchange-session rules can change which bars enter the test.
Order processing
Stop, limit, and on-close behavior can vary when only OHLC values are available.
Unsupported features
A complex strategy may rely on behavior the public compatibility engine rejects.
Record the difference instead of guessing
- 1
Run the exact script in both environments
Keep the market, timeframe, dates, inputs, costs, and execution settings aligned.
- 2
Tell the GPT: “It differs from TV.”
The mismatch workflow only starts when you explicitly report the difference.
- 3
Save the review context
The report records the Pine source, API result, resolved settings, dataset information, engine build, fingerprints, and your notes.
- 4
Keep the mismatch report ID
Use the returned ID to track the maintenance signal and investigate the first divergent trade.
PineScript API does not independently access or verify a private TradingView chart. A mismatch report is a maintenance signal submitted by the user; it is not proof that either environment is incorrect.