Skip to content
TradequixDocsOpen the terminal
OverviewStart here, search, progress
  • Introduction
  • Quickstart
  • How a script runs
  • Types and qualifiers
  • Operators, conditionals and loops
  • Functions and methods
  • Objects and enums
  • Arrays, matrices and maps
  • Strings and colours
  • Time and sessions
  • Bar states
  • Plotting
  • Inputs
  • Technical analysis
  • Drawings and tables
  • Multiple timeframes
  • Strategies
  • Alerts in scripts
  • Repainting
  • The Pine editor
  • Indicator settings
  • Coming from TradingView
  • The data
  • Publish and sell
  • Catalogue and community
  • Your dashboard and earnings
  • Errors and debugging
  • Limits
  • Coverage
  • Built-in catalogue
  • Cookbook
  • Write Pine with AI
  • FAQ
  • Glossary
  • Cheat sheet
  • Function reference
  • Will it run here?
  • Error index

On Tradequix

The data

What the live OTC feed gives a script, what it cannot, and how the editor tells you when a script asks for something missing.

View as MarkdownOpen in ClaudeOpen in ChatGPT

Pine on Tradequix runs on a live OTC candle feed. Most of Pine's language works exactly as documented; the differences come from what a candle feed can and cannot supply.

What every bar carries#

SeriesOn this feed
open, high, low, closeThe bar's prices, live
hl2, hlc3, ohlc4Derived from the above
volumeA tick count: how many price updates the bar received
timeWhen the bar opened, in milliseconds
bar_index0 on the oldest loaded bar
syminfo.tickerid, syminfo.mintickThe chart's symbol and its price step
timeframe.periodThe chart's timeframe as a Pine string

Volume is a tick count#

The feed reports how many ticks each bar had, not how much was traded. That is a fair measure of activity, so comparing volume between bars is meaningful: ta.obv, ta.mfi, volume spikes and plotting volume itself all work as you would expect. Indicators that treat volume as traded size, such as VWAP and accumulation/distribution, still compute, but their values mean something narrower than their names. The editor shows a warning whenever a script uses volume.

Timeframes#

Fourteen timeframes come from the feed: 5, 10, 15 and 30 seconds; 1, 2, 3, 5, 10, 15 and 30 minutes; 1 and 4 hours; and 1 day. Others are built from these. See Multiple timeframes.

What is not available#

A candle feed has no company data or order book. Scripts that ask for these still run; the request returns na and the console says why:

  • request.financial, request.earnings, request.dividends, request.splits, request.economic
  • request.footprint (needs order-flow data)
  • Modified tickers: Heikin Ashi, Renko, Kagi, Line Break, Point and Figure. These fail with an explicit error rather than serving ordinary candles under another name. Compute Heikin Ashi yourself instead; see the cookbook.

How much history a script sees#

A script runs on the bars loaded on the chart. Scroll back and more history loads; the script runs again over it. Long averages need warm-up: a 200-bar average is na for the first 199 bars it sees.

Tip

The docs' Run buttons use a fixed generated series of 300 five-minute bars, not the live feed. Behaviour that depends on the feed (other timeframes, the live last bar) is best tried in the terminal with Open in editor.

PreviousComing from TradingViewNext Publish and sell

On this page

  • What every bar carries
  • Volume is a tick count
  • Timeframes
  • What is not available
  • How much history a script sees

Use with AI

View as MarkdownOpen in ClaudeOpen in ChatGPT