TradingView webhook trading from alert to execution starts with a simple HTTP POST, but reliable automation requires validation, routing and a traceable execution result after the request arrives.
TradingView’s current webhook documentation says an alert can send an HTTP POST to the URL you configure. If the body is valid JSON, TradingView uses application/json; otherwise it sends text/plain. Your message therefore has to match what the receiver expects.
TradingView currently allows webhook URLs on ports 80 and 443, requires 2FA for webhook alerts and cancels a request if the remote server takes more than three seconds to process it. It also notes that delivery can occasionally fail and provides webhook status in the alert log.
A successful HTTP response only proves that the receiver accepted the request. Validation, account and symbol routing, cTrader connectivity and broker acceptance still have to happen. NRUNO separates these stages.
TradingView warns not to place login credentials or passwords in the webhook URL or body. A webhook should carry the instruction, while authentication to the execution system remains separate. HTTPS and controlled endpoints are important.
NRUNO receives the request, validates supported instructions and routes them to the connected cBot. The cBot handles the cTrader side and can apply configured filters or trade-management rules.
Primary sources: TradingView webhooks · Webhook security
Yes. Valid JSON alert bodies are currently sent as application/json.
Because HTTP receipt and cTrader/broker execution are separate stages.
Yes, according to its current webhook documentation.
No. TradingView explicitly warns against sending sensitive credentials in webhooks.