How should account routing work in a TradingView webhook?
Do not trust a free-form account number from an unauthenticated webhook. Map a connector/token or authenticated routing identifier to an authorized server-side account configuration.
What this means in practice
Do not trust a free-form account number from an unauthenticated webhook. Map a connector/token or authenticated routing identifier to an authorized server-side account configuration. This page is specifically about “How should account routing work in a TradingView webhook?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Connector ID maps to account
Inspect the mechanism named by “Scenario A — Connector ID maps to account” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Connector ID maps to account on question 69, use that evidence specifically to answer “How should account routing work in a TradingView webhook?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — User-supplied account field
Inspect the mechanism named by “Scenario B — User-supplied account field” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — User-supplied account field on question 69, use that evidence specifically to answer “How should account routing work in a TradingView webhook?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Revoked account mapping
Inspect the mechanism named by “Scenario C — Revoked account mapping” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Revoked account mapping on question 69, use that evidence specifically to answer “How should account routing work in a TradingView webhook?”; 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 “How should account routing work in a TradingView webhook?”, 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: Do not trust a free-form account number from an unauthenticated webhook. Map a connector/token or authenticated routing identifier to an authorized server-side account configuration.
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.