TradingView

Receive signals from TradingView alert webhooks. The most common Signalync setup.

Prerequisites

You need a TradingView account on the Pro plan or higher. The free plan does not support webhook alerts. Any paid tier (Pro, Pro+, Premium) works.

Already on a paid plan?

You can add the webhook URL to any existing alert, no new indicator or strategy is required.

Setup

Follow these steps to connect TradingView to Signalync.

  1. 1

    Create a TradingView source

    In the Signalync dashboard go to Sources → New Source and select TradingView.
  2. 2

    Name it

    Give the source a descriptive name, e.g. “TV — BTC strategy” or “TV — EURUSD scalper”.
  3. 3

    Save and copy the webhook URL

    Click Save. Signalync shows a unique webhook URL, copy it. It looks like: https://signalync.com/api/inbound/tv_XXXXXXXXXXXX
  4. 4

    Create a TradingView alert

    In TradingView, open the Alerts panel (clock icon) and click Create alert. Set your condition as usual.
  5. 5

    Set the webhook URL

    In the alert dialog, enable Webhook URL and paste the URL you copied from Signalync.
  6. 6

    Set the message body

    In the Message field, enter your signal payload. See the signal format section below for examples.
TradingView fires the alert and POST-s the message body to your webhook URL immediately when the condition triggers. Signalync receives it, parses the signal, and routes it to your MT5 target via the Route you have configured.

Signal format

The message body you enter in TradingView's alert dialog is the signal payload. Signalync uses a compact, comma-separated format.

Minimal example

{{ticker}},buy,vol=0.1
signal

With stop loss and take profit

{{ticker}},{{strategy.order.action}},vol=0.1,sl_pips=50,tp_pips=100
signal

Multi-TP with risk-based sizing

XAUUSD,sell,vol_pctbal_loss=1,sl_pips=40,tp1_pips=40,tp2_pips=80,tp3_pips=120
signal

Pending order

GBPUSD,buylimit,entry=1.2650,vol=0.5,sl_pips=30,tp_pips=60
signal

TradingView placeholders

Use {{ticker}} to insert the chart symbol automatically, and {{strategy.order.action}} to insert the strategy action (buy / sell) when firing from a Pine Script strategy.

See the full signal format reference for all volume, stop loss, take profit, trailing stop, and order type parameters.

HMAC security (optional)

By default, anyone who knows your webhook URL can send signals to it. To restrict this, set an HMAC secret on the Source.

When a secret is set, Signalync requires every inbound request to include an X-Signature header containing a SHA-256 hex digest of the raw request body, keyed with your secret. Requests without a valid signature are rejected with 401.

TradingView does not support custom headers

TradingView webhooks cannot send custom headers. HMAC signing is therefore only useful if you are proxying TradingView alerts through your own server before forwarding to Signalync. For most setups, the security of an unguessable URL is sufficient.

Troubleshooting

Alert fired but no signal appeared in Signalync

Check that the TradingView alert is still Active (not expired or paused). Open the Alerts panel and look for a warning icon. Also verify the webhook URL in the alert matches the one in your Signalync source.

Signal received but not parsed

Open the signal in the Signals table and expand the detail drawer, it shows the raw payload and the parse error. Check the signal format reference and make sure there are no stray spaces or unexpected characters in the message body.

401 Unauthorized

The webhook URL contains the wrong source key. Re-copy it from the Source detail page in Signalync and update the TradingView alert.

HMAC signature mismatch

The secret must match exactly (case-sensitive) on both sides. The signature is computed over the raw bytes of the request body, any encoding difference will break the comparison. As noted above, TradingView cannot send the required header, so disable HMAC on any source that receives direct TradingView webhooks.