Webhooks, Delivery & Reliability

When an alert fires, TradingView sends an HTTP POST to the configured URL. Valid JSON is sent as application/json; otherwise the body is text/plain.

Enable 2FA, create the correct alert, add a secure webhook URL, provide a valid message and test the full route on demo first.

Use explicit fields such as action, symbol, volume/risk, optional SL/TP and a unique signal ID. Never include broker passwords or sensitive credentials.

Alert generation and webhook delivery are separate. Invalid URL/TLS, redirects, authorization, malformed data, rate limits, server errors and slow responses are common causes.

3xx means redirect; 4xx means the receiver rejected the request/data/access; 5xx means the receiving server failed to process it. Timeouts and TLS failures are separate.

TradingView requires a response within three seconds. A robust receiver validates and safely accepts the signal quickly instead of waiting for slow broker execution.

Measure signal calculation, alert, webhook, receiver, cTrader transport, order submission and broker fill separately. Each stage has different causes.

Duplicates can come from Pine logic, duplicate alerts, duplicate execution instances or retries. TradingView can resend certain 5xx webhooks three times, so one trigger can…

Idempotency means receiving the same signal multiple times does not create multiple trading effects. It is essential because networks retry and TradingView can resend certain…

A signal ID should identify one intended action and stay identical when that same action is retried. Store processed IDs so repeated delivery can be acknowledged without…

TradingView can resend webhook requests that receive HTTP 500–599 except 504 after five seconds, up to three resends. One trigger can therefore produce at most four sends.

HTTP 200 should mean the receiver accepted the HTTP/application request, not that the broker guaranteed a fill. Track execution as a separate state after acknowledgement.

Treat webhook acceptance and cTrader execution as separate statuses. If cTrader later rejects the operation, log and expose the exact execution error instead of pretending…

Give time-sensitive signals an explicit creation time and expiry policy. A delayed entry that was valid 30 seconds ago may be dangerous after a disconnect or market move, so…

The system needs an explicit policy: reject immediately, queue with a short expiry, or hold for manual review. Blindly replaying every signal after reconnection can open trades…

A partial-close command should identify the target position/strategy scope and an explicit quantity or percentage to close. Do not use an ambiguous SELL command when the intent…

Correlate ENTRY and EXIT by identity and reconcile actual cTrader state. An EXIT arriving first must not blindly become an opposite entry.

Where sequence matters, carry identity, timestamps and/or sequence numbers. Reject, defer or reconcile stale/out-of-order commands instead of processing them blindly.