Footprint Requests in Pine Script v6: How request.footprint() Changes Custom Order-Flow Work

Direct answer

request.footprint() is a real step forward for Pine Script because it gives you structured footprint data inside your own script instead of forcing you to look at a footprint chart and then manually rebuild the logic somewhere else.

That matters most for traders who want delta-aware confirmation, custom order-flow filters, or context around imbalance without pretending the answer is just another moving average.

Why this is genuinely trending in 2026

TradingView's March 2026 footprint release is one of the clearest examples of Pine Script moving deeper into workflow features that were previously awkward to reproduce. It is not hype for the sake of hype. It changes what a custom script can access.

When a platform adds a new data structure like this, the first wave of scripts is usually noisy. The builders who do well are the ones who keep the first version focused and readable instead of trying to build an entire order-flow empire in one pass.

What request.footprint() actually gives you

The official release introduced a footprint object you can request directly in Pine Script. That object can expose useful information such as buy volume, sell volume, and delta. In other words, the script can stop guessing at volume balance from candle shape alone.

What I like about this feature is not that it makes a chart look more advanced. It gives you a better input for custom decisions. That is a very different thing.

//@version=6
indicator("Footprint delta view", overlay = false)

footprint fp = request.footprint(100, 70)

float deltaValue = not na(fp) ? fp.delta() : na
float buyVolume  = not na(fp) ? fp.buy_volume() : na
float sellVolume = not na(fp) ? fp.sell_volume() : na

plot(deltaValue, "Delta", style = plot.style_columns,
     color = deltaValue >= 0 ? color.teal : color.red)
plot(buyVolume,  "Buy volume",  color = color.new(color.teal, 40))
plot(sellVolume, "Sell volume", color = color.new(color.red, 40))

How I would use it in a real build

I would start with one narrow job. For example:

• confirm whether the breakout bar is backed by strong positive or negative delta
• filter a reversal setup when aggressive volume is clearly one-sided
• mark context around a location where price is moving but participation is weak

That is usually better than turning the first footprint script into a buy-sell machine. Order-flow context becomes useful when it makes another decision cleaner, not when it becomes decoration.

Where traders usually get this wrong

The first mistake is assuming footprint data automatically produces a better strategy. It does not. Better inputs only help if the surrounding logic is still sane.

• not handling na values and then blaming the feature for gaps
• using footprint data on every bar without asking whether the setup really needs it
• trying to force a full strategy before understanding how the requested object behaves in practice
• treating footprint data like an authority signal instead of one layer of context

How I would keep the first version honest

If I were building this for a serious trader, I would keep version one small enough to answer a single question clearly. Is aggressive flow supporting the move, fading the move, or not saying much at all?

That kind of answer is already valuable. It keeps the script usable. It also gives you something that can still be checked on live bars instead of only looking clever in a screenshot.

What to read next

If you are exploring newer Pine Script capabilities right now, these are the best follow-ups.

• How to Fix Repainting in Pine Script
• Pine Script v6 vs v5
• Dynamic Requests in Pine Script v6 Libraries

Frequently asked questions