TradingView to Telegram webhook JSON

Telegram's Bot API takes a JSON body with chat_id and text at its sendMessage URL. Build the message, check it as you type, and see the text your chat will get.

Updated 23 October 2026. Runs in your browser; nothing you type is uploaded.

Send to

Alert from

Alert message, as typed in TradingView's Message box

Placeholders for any alert

Strategy alerts only

Text placeholders go in quotes; a placeholder added outside a string comes with them.

Telegram, strategy alert

Valid JSON: TradingView sends it as application/json

0 errors, 1 thing to check. This is the Telegram preset for a strategy.

YOUR_CHAT_ID is still a stand-inCheck
Replace it with your own value before you create the alert.

What Telegram receives

Content-Type: application/json, with sample values in place of the placeholders.

{
  "chat_id": "YOUR_CHAT_ID",
  "text": "NQ1!: buy 2 at 18342.25"
}

Where it goes

Webhook URL: https://api.telegram.org/botYOUR_BOT_TOKEN/sendMessage Your bot's token goes straight after bot, with no slash.
The secret: In the URL: the bot token. Anyone holding it controls the bot.

sendMessage needs chat_id and text, 1 to 4,096 characters; the Bot API reads a JSON body.
parse_mode is optional. With MarkdownV2, characters such as . - ! and brackets must be escaped with a backslash, and a price has a dot, so plain text is safer.

From Telegram's docs, read 23 October 2026: sendMessage, formatting options.

Or build it in Pine, so the JSON is never inside other JSON

In the alert: Order fills only, and nothing but {{strategy.order.alert_message}} in the Message box. Each order passes the whole message as alert_message, with its own buy or sell.

//@version=6
strategy("Webhook message", overlay = true)

// Your own rules go here; this example crosses two averages.
fast = ta.sma(close, 10)
slow = ta.sma(close, 30)
qty = 1

// The whole message, built here. In the alert: Order fills only, and nothing but
// {{strategy.order.alert_message}} in the Message box.
webhookMessage(string action, string id, string position) =>
    string m = '{'
    m += '"chat_id": "YOUR_CHAT_ID",'
    m += '"text": "' + syminfo.ticker + ': ' + action + ' ' + str.tostring(qty) + ' at ' + str.tostring(close) + '"'
    m += '}'
    m

if ta.crossover(fast, slow)
    strategy.entry("Long", strategy.long, qty, alert_message = webhookMessage("buy", "Long", "long"))
if ta.crossunder(fast, slow)
    strategy.entry("Short", strategy.short, qty, alert_message = webhookMessage("sell", "Short", "short"))

The code for every preset compiles on TradingView with no errors or warnings. Put your own entry rules in place of the two averages, then check the script for repaint risks.

What Telegram reads

Format: JSON; it needs "chat_id", "text".
Webhook URL: https://api.telegram.org/botYOUR_BOT_TOKEN/sendMessage Your bot's token goes straight after bot, with no slash.
The secret: In the URL: the bot token. Anyone holding it controls the bot.

sendMessage needs chat_id and text, 1 to 4,096 characters; the Bot API reads a JSON body.
parse_mode is optional. With MarkdownV2, characters such as . - ! and brackets must be escaped with a backslash, and a price has a dot, so plain text is safer.

The two starting messages

From a strategy

{
  "chat_id": "YOUR_CHAT_ID",
  "text": "{{ticker}}: {{strategy.order.action}} {{strategy.order.contracts}} at {{strategy.order.price}}"
}

From an indicator

{
  "chat_id": "YOUR_CHAT_ID",
  "text": "{{ticker}} closed at {{close}} on the {{interval}} chart"
}

From Telegram's own docs, read 23 October 2026: sendMessage, formatting options.

TradingView's side of a webhook

Plan and 2FA: Webhook notifications are on Essential, Plus, Premium, Ultimate, not on the free Basic plan (pricing table), and webhook alerts are allowed only with two-factor authentication turned on.
Content-Type: application/json when the message is valid JSON, text/plain otherwise. TradingView sends a POST with the message as the body.
IP addresses to allowlist: 52.89.214.238, 34.212.75.30, 54.218.53.128, 52.32.178.7. Over HTTPS TradingView also sends a client certificate for webhook-server@tradingview.com (webhook authentication).
Ports, IPv6 and time: Ports 80 and 443 only; no IPv6; no localhost or private addresses. A request your server takes more than three seconds to answer is cancelled, and a 500 to 599 answer other than 504 is sent again after 5 seconds, up to 3 times (resubmission).
Message length: 4,000 characters in the alert's Message box; 40,960 from alert() or alert_message. The body has the same limits, and an emoji counts as several characters (size limits).
Secrets: TradingView asks you not to put login credentials or passwords in the webhook URL or message (credentials for webhooks).

From TradingView's How to configure webhook alerts and the pages linked above, read 23 October 2026.

Other receivers

TradingView to TradersPost webhook JSON JSON with ticker and action; the password is in the webhook URL.
TradingView to PineConnector alert message Comma-separated text, not JSON; the License ID leads the message.
TradingView to CrossTrade webhook JSON Flat JSON or key=value; text; the Secret Key goes in the message.
TradingView to 3Commas Signal Bot JSON v2 Signal Bot JSON; the v1 secret and bot_uuid format is retired.
TradingView to Discord webhook JSON JSON with content or embeds; the token is in the webhook URL.
Custom JSON for your own server and TradingView's placeholders in full.

Method and privacy

Method: Runs in your browser. The message is read as JSON with each TradingView placeholder as one token, typed as text or a number from TradingView's placeholder list, then read again by a JSON parser with sample values in their place. Telegram's rules come from its own docs, and TradingView's from its pages, both read 23 October 2026. It cannot see your Telegram settings or whether an alert was delivered: send a test alert before you trade on it.

Calculations run entirely in your browser — nothing you type is uploaded. Your last numbers stay in this browser so you can pick up where you left off; Forget them clears them. A link with your numbers carries them after the # sign, which browsers do not send to servers, and the page takes them out of the address before any analytics loads. Copy and download actions save your calculation locally. The site may record coarse tool actions under its privacy policy, without inputs, results, file contents or filenames.

Common questions

How do I send a TradingView alert to Telegram?

Point the webhook at https://api.telegram.org/bot followed by your bot's token and /sendMessage, and send JSON with chat_id and text, such as {"chat_id": "YOUR_CHAT_ID", "text": "{{ticker}} closed at {{close}}"}. Telegram's Bot API reads parameters from a JSON body, and TradingView sends the message as application/json when it is valid JSON.

Why does a Telegram alert fail with parse_mode MarkdownV2?

MarkdownV2 needs _ * [ ] ( ) ~ ` > # + - = | { } . ! escaped with a backslash, and a price such as 18342.25 has a dot. Leave parse_mode out for plain text, or use HTML and replace <, > and & with their entities.

How long can a TradingView alert to Telegram be?

sendMessage takes 1 to 4,096 characters of text after entities are parsed, and TradingView's Message box takes up to 4,000 characters, so the Message box is the tighter limit.

Alerts that already send the message

Signal Desk Premium A Pine v6 desk whose alerts write the message for you, as ticket text, JSON, TradersPost or PineConnector, with a Discord and Telegram relay. $49 once.
Pine Fixer An AI skill pack for 45 compiler-verified Pine v6 failure classes, with a repaint clinic. $9.99 once.

Goes deeper

Explore ProEA tools Pine Pro Library: TradingView desks with full Pine v6 source ($49 once)Pine Script v5 to v6 converter Complete Suite: every desk and tool, one payment