What should a TradingView webhook message contain?
Use explicit fields such as action, symbol, volume/risk, optional SL/TP and a unique signal ID. Never include broker passwords or sensitive credentials.
What this means in practice
Use explicit fields such as action, symbol, volume/risk, optional SL/TP and a unique signal ID. Never include broker passwords or sensitive credentials. This page is specifically about “What should a TradingView webhook message contain?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Minimal BUY
Keep the webhook contract explicit. The receiver should know exactly which field represents action, symbol, size and optional protection, and reject missing or ambiguous values rather than guessing. For Scenario A — Minimal BUY on question 7, use that evidence specifically to answer “What should a TradingView webhook message contain?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — BUY+SL/TP
Keep the webhook contract explicit. The receiver should know exactly which field represents action, symbol, size and optional protection, and reject missing or ambiguous values rather than guessing. For Scenario B — BUY+SL/TP on question 7, use that evidence specifically to answer “What should a TradingView webhook message contain?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Explicit close
Inspect the mechanism named by “Scenario C — Explicit close” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Explicit close on question 7, use that evidence specifically to answer “What should a TradingView webhook message contain?”; keep it separate from the evidence for the other scenarios on this page.
Scenario D — Signal ID
Validate the structured payload semantically: required fields, allowed actions, numeric ranges and signal identity. A retransmission of the same logical instruction should keep the same ID. For Scenario D — Signal ID on question 7, use that evidence specifically to answer “What should a TradingView webhook message contain?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- TradingView alert log and exact send time
- HTTP status and receiver timestamp
- validated payload plus signal ID
- cTrader result only after transport is proven
Practical rule
For “What should a TradingView webhook message contain?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.
Decision summary
Direct answer: Use explicit fields such as action, symbol, volume/risk, optional SL/TP and a unique signal ID. Never include broker passwords or sensitive credentials.
Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.