Quantiva Trade

Module overview

Get Quantiva Trade access in TradingView with your subscription, then deploy alerts with strict mode validation and execution controls.

Quantiva Trade, deployed.

Activate Quantiva Trade access in TradingView
Set position size per trade (USDT)
Reverse/flip in Futures One-Way and Hedge
Spot mode is long-only (reverse closes position)

Open App Workspace Access App

How this module fits the suite

Quantiva keeps routing, execution context and performance visibility connected across Trade, Live, Lab, and Edge.

Account-level routingShared session/authUnified workspace

Open Dashboard

Execution contract

Quantiva Trade signal schema (explicit)

Trade page defines the exact bridge from TradingView alert payload to execution routing. If mode does not match your profile, the order is rejected before exchange execution.

Explicit Quantiva Trade schema from TradingView payload to mode validation and execution routing

Payload expected from TradingView

Minimum fields required by Quantiva webhook before routing.

{
  "symbol": "BTCUSDT",
  "action": "sell",
  "execution_mode": "futures_hedge",
  "positionMode": "hedge_mode",
  "mode_sync_policy": "required_profile_match",
  "signalId": "tv-2026-04-17-001"
}

Mode normalization

Spot -> spot
Futures One-Way -> futures_oneway
Futures Hedge -> futures_hedge

Validation is always enforced for safety, including legacy signals with no mode_sync_policy.

Mismatch response contract

When profile mode and payload mode differ, execution is blocked and audited.

{
  "status": "rejected",
  "code": "MODE_MISMATCH",
  "message": "Mode mismatch: profile=futures_oneway, payload=futures_hedge",
  "action_hint": "Update QTrade Execution Mode or switch profile mode in Quantiva."
}