Understanding TradingView Alert JSON (Placeholders Explained)

Lesson 39 located the Webhook URL field. This lesson looks at the piece right next to it: the Message box - what actually gets sent when the alert fires - along with TradingView’s placeholder syntax that makes a single message automatically accurate, no matter what triggers it.

The Message Box, Briefly

Inside the same alert creation dialog from Module 8 and Lesson 39, the Message box is where you type the content that gets sent - whether that message ends up as an on-screen notification, an email, or (this module’s focus) a webhook message delivered to your configured URL.

What Is JSON? (One Sentence)

You’ll often see alert messages formatted in a particular structured style called JSON. In one simple sentence: JSON is simply a structured text format that many different software systems use to exchange data. That’s genuinely all you need to know conceptually for this lesson - no programming background required.

TradingView’s Placeholder Syntax

Rather than typing a fixed price or instrument name into the Message box (which would quickly become wrong the moment conditions change), TradingView provides placeholders - special text wrapped in double curly braces, like {{ticker}} - that get automatically replaced with real, current values at the exact moment the alert fires.

A few commonly used examples:

• {{ticker}} → replaced with the instrument’s ticker symbol (e.g., RELIANCE, NIFTY)
• {{close}} → replaced with the closing price at the moment the alert triggered
• {{time}} → replaced with the timestamp of the triggering candle
• {{strategy.order.action}} → replaced with the order action (e.g., buy or sell) from a strategy script’s logic, per Lesson 37’s strategy-vs-indicator distinction

   What you TYPE in the Message box:
   {{ticker}} crossed {{close}} at {{time}}

   What TradingView actually SENDS when it fires:
   RELIANCE crossed 2,847.50 at 2026-07-19 10:32:00

The same typed message automatically produces an accurate, current message every single time the alert fires - regardless of which instrument, price, or time is actually involved at that moment.

A Simple Worked Example: Composing a JSON-Style Message

Suppose a receiving system expects a small, structured message rather than a plain sentence. A trader might compose this in the Message box:

{"ticker": "{{ticker}}", "action": "buy", "price": {{close}}}

Reading this in plain English: it’s a structured message with three labeled pieces of information - a ticker (which will be automatically filled in with the real instrument symbol), an action (written here as a fixed value, “buy,” since this particular alert always means the same thing), and a price (automatically filled in with the real closing price). When the alert actually fires on, say, Reliance Industries at ₹2,847.50, TradingView would send something like:

{"ticker": "RELIANCE", "action": "buy", "price": 2847.50}

This example is illustrative, not universal. The exact field names (“ticker,” “action,” “price”), how many fields to include, and the precise formatting depend entirely on what the receiving platform expects and is built to parse - some systems might want additional fields, different names entirely, or a different structure altogether.

Real-Life Example: Two Alerts, Two Messages

Suppose a trader sets up two separate Bank Nifty alerts. The first, a simple price alert, uses the message "Bank Nifty crossed {{close}}" - plain text, meant mainly for a human reading a notification. The second, connected to a strategy script’s buy/sell logic, uses a JSON-style message like {"ticker": "{{ticker}}", "action": "{{strategy.order.action}}", "price": {{close}}} - meant for a receiving system that needs to programmatically read the ticker, action, and price separately. Same underlying placeholder mechanism, two different message styles, matched to two different purposes.

Analogy: A Fill-in-the-Blanks Form Letter

Think of a placeholder-filled alert message like a form letter with blanks: “Dear _, your appointment on _ at ___ is confirmed.” You write the template once, with blanks marked clearly, and the system fills in the real name, date, and time automatically each time a letter goes out - you never have to rewrite the whole letter for every single recipient. TradingView’s {{ticker}}, {{close}}, and similar placeholders work exactly the same way, just for alert messages instead of letters.

Common Beginner Mistakes

• Assuming JSON requires a programming background to understand conceptually. The one-sentence definition in this lesson (a structured text format for exchanging data) is genuinely sufficient to follow this entire module.
• Believing this lesson’s exact example fields are a universal standard. They’re illustrative only - the receiving platform always determines what fields and structure it actually expects.
• Misspelling a placeholder (like {{clsoe}} instead of {{close}}), which would likely prevent proper substitution - careful spelling matters here.
• Putting sensitive information directly into the message text, a security consideration covered fully in Lesson 42.

Practical Tips

• Before composing any real message, check what field names and structure your intended receiving platform actually expects - never assume this lesson’s example fields apply universally.
• Start with a simple plain-text message (no JSON) if you’re not yet connected to a system that needs structured data - JSON formatting is a choice, not a requirement, for the Message box itself.
• Keep a personal note of which placeholders you’ve tested and confirmed work as expected, before relying on any alert message for something important.

Conclusion

Placeholders like {{ticker}} and {{close}} are what let a single alert message stay accurate and specific, automatically, no matter which instrument or price actually triggers it. With the message itself understood, the next lesson zooms out to the full generic workflow - from a chart condition being met all the way to a receiving platform deciding what to do about it.