How a TradingView Webhook Reaches Your Broker
One alert, one webhook URL, one JSON payload — this is the exact path a TradingView signal travels to become a live order at Tradovate, Rithmic, Interactive Brokers, or any of PickMyTrade's 10 supported brokers.
See the Webhook PayloadWhat Is a TradingView Webhook?
A TradingView webhook is an outbound HTTP request that TradingView fires the moment a price alert or strategy alert condition is met. Instead of a popup or email, TradingView sends a JSON message to a URL you specify — in this case, a PickMyTrade endpoint that reads the payload and places the corresponding order at your connected broker.
Webhook alerts are a paid TradingView feature (Pro, Pro+, or Premium plans) — the free plan cannot send them. Beyond that requirement, there is nothing to install: no VPS, no bridge software running on your machine, and no code to write.
The Three-Hop Path From Signal to Order
1. TradingView Fires the Alert
A Pine Script strategy, a Pine Script indicator, or a manual price alert triggers. TradingView sends an HTTP POST containing your JSON alert message to the webhook URL saved in the alert's Notifications tab.
2. PickMyTrade Parses and Routes It
PickMyTrade's webhook endpoint authenticates the request via your account token, parses the JSON fields (symbol, action, quantity, risk parameters), and maps them to an order for your connected broker account — live, demo, or prop-firm evaluation.
3. The Broker Executes the Order
The order reaches your broker through an OAuth-authenticated or API-key connection and executes under normal market conditions in well under a second end to end. Fills, rejections, and errors are logged back to your PickMyTrade dashboard.
Anatomy of a Webhook Alert
Every PickMyTrade webhook alert has two parts: a webhook URL (where TradingView sends the request) and a JSON alert message (what it sends). Both are generated for you in the PickMyTrade dashboard — you paste them into TradingView's alert dialog, you do not hand-write them.
Webhook URL — pasted into the TradingView alert's Notifications tab with the Webhook URL option enabled.
JSON alert message — pasted into the TradingView alert's Message field. A generated example:
symbol The instrument TradingView is alerting on, e.g. NQ1! for the E-mini Nasdaq continuous futures contract.
data The action: buy, sell, or an exit signal.
quantity / risk_percentage Contracts or units to trade. Can also be sized dynamically via risk_percentage instead of a fixed number.
order_type MKT for market orders; limit and stop variants are also supported.
token Your account authentication token, generated per alert in the PickMyTrade dashboard — never shared across accounts.
multiple_accounts An optional array that fans the same alert out to additional connected accounts, each with its own token, account ID, and size multiplier — this is what powers multi-account trade copying from a single alert.
{
"symbol": "NQ1!",
"date": "{{timenow}}",
"data": "buy",
"quantity": 2,
"risk_percentage": 0,
"order_type": "MKT",
"token": "At8tLtTtYtEt8t8tHtWtPtOtR",
"multiple_accounts": [
{
"token": "UnyTGjYrtvhSW65-Iuds",
"account_id": "DEMO2001",
"quantity_multiplier": 1
}
]
} Security and Reliability of the Webhook Path
Because a webhook alert can place real orders, the connection between TradingView, PickMyTrade, and your broker is authenticated and encrypted at every hop.
OAuth 2.0 Authentication
Tradovate and other OAuth-supported brokers connect via OAuth 2.0 — PickMyTrade never sees or stores your broker password.
AES-256 Encryption
Account tokens and connection data are encrypted at rest and in transit (TLS/SSL).
Audit Logging
Every webhook received and every order it produced is logged to your dashboard, with access controls modeled on SOC 2 Trust Services Criteria.
Sub-Second Target Latency
PickMyTrade targets sub-200ms execution from webhook receipt to order placement; real-world end-to-end latency (including TradingView's own outbound delay) typically lands in the 200–600ms range.
Common Webhook Problems (and the Fix)
Most webhook alerts that never execute trace back to one of these four causes.
Alert Never Fires
Usually a TradingView plan issue — webhook alerts require Pro, Pro+, or Premium. Confirm the alert actually triggered in TradingView's own alert log before assuming PickMyTrade is at fault.
Webhook URL Not Enabled
TradingView requires the Webhook URL checkbox to be checked in the alert's Notifications tab, with the URL pasted in — a checked box with an empty field, or vice versa, silently drops the alert.
Invalid JSON in the Message Field
A missing comma or an extra brace makes the whole payload unparsable. Copy the generated message from the PickMyTrade dashboard rather than hand-editing it, and re-copy after any change to the alert.
Token or Account Mismatch
Each token maps to one specific connected account. Reusing a token from a different account, or from a demo account against a live one, sends the order nowhere your broker recognizes.
Frequently Asked Questions
It's an outbound HTTP POST request that TradingView sends to a URL you specify the moment an alert condition is met. The request body is a JSON message you configure in the alert. PickMyTrade's webhook endpoint receives that request and converts it into a broker order.
No. PickMyTrade generates both the webhook URL and the JSON alert message for you in the dashboard. You paste them into TradingView's alert dialog — there is no code to write and no Pine Script requirement.
Tradovate, Rithmic, Interactive Brokers, TradeStation, TradeLocker, ProjectX/TopstepX, Match-Trader, Tradier, Binance, and Bybit. The webhook format is the same regardless of which broker your account connects to.
TradingView needs to be able to evaluate your alert condition, which for most alert types does not require the browser tab to stay open once the alert is created. Once TradingView sends the webhook, PickMyTrade executes it cloud-side — you do not need a VPS or any bridge software running.
A paid plan — Pro, Pro+, or Premium. TradingView's free plan cannot send webhook alerts at all, regardless of which automation tool you use.
PickMyTrade targets sub-200ms execution from webhook receipt to broker order placement. End-to-end, including TradingView's own outbound webhook latency, most orders land in the 200-600ms range.
Yes. The JSON alert message supports a multiple_accounts array, letting a single TradingView alert fan out to every connected account you specify, each with its own size multiplier.
Yes. OAuth 2.0 authentication (no stored broker passwords), AES-256 encryption at rest and in transit, audit logging, and account tokens scoped to a single connected account are all part of the webhook path.
Ready to Route Your First Webhook?
Generate a webhook URL and JSON alert in minutes, then paste them into a TradingView alert. 5-day free trial, no credit card required.