TradingView Webhook Documentation

Example 1: MT4/MT5 Forex Trade with Stop Loss and Take Profit

{
  "exchange": "MT5",
  "symbol": "USDJPY",
  "action": "sell",
  "price": 154.872,
  "quantity": 1,
  "stop_loss": 155.500,
  "take_profit": 154.000
}

Example 2: Binance Crypto Trade

{
  "exchange": "binance",
  "symbol": "BTCUSDT",
  "action": "sell",
  "price": 86830,
  "quantity": 1
}

Example 3: Market Order (No Price)

{
  "exchange": "binance",
  "symbol": "ETHUSDT",
  "action": "buy",
  "quantity": 0.5
}

When price is omitted, the order executes as a market order at the current market price.

Example 4: All Optional Fields

{
  "exchange": "binanceusdm",
  "symbol": "BTCUSDT",
  "action": "buy",
  "price": 85000,
  "quantity": 0.1,
  "stop_loss": 84000,
  "take_profit": 90000,
  "order_type": "limit",
  "leverage": 10
}

Example 5: Routing to a Specific Account with accountName

{
  "accountName": "My Trading Account",
  "symbol": "BTCUSDT",
  "action": "buy",
  "price": 86000,
  "quantity": 0.05
}

Use accountName to route webhooks to a specific account. The exchange type is automatically determined from the account - no need to specify exchange separately. The account name must exactly match the name you set in your Traydar dashboard.

Example 6: Routing to Multiple Accounts Simultaneously

{
  "accounts": "Main Trading,Scalping Account,MT5 Broker",
  "symbol": "BTCUSDT",
  "action": "buy",
  "price": 86000,
  "quantity": 0.05
}

Use accounts to send the same order to multiple accounts simultaneously. Provide a comma-separated list of account names. This is the highest priority routing method - accounts can be across different exchanges and brokers (e.g., Binance, OKX, MT4, MT5). Each account name must exactly match a name in your Traydar dashboard.

Example 7: Percentage-Based Quantities

{
  "accountName": "My Trading Account",
  "symbol": "BTCUSDT",
  "action": "buy",
  "price": 50000,
  "quantity": "50%"
}

Uses 50% of available USDT balance to buy BTC at $50,000. For SELL orders, use percentage of total position size (e.g., "quantity": "100%" to close entire position). Valid range: 0% to 100%.

Example 8: Bypassing RiskAI Checks

{
  "exchange": "binance",
  "symbol": "BTCUSDT",
  "action": "buy",
  "price": 86000,
  "quantity": 0.1,
  "riskai": 0
}

Setting riskai: 0 disables RiskAI validation for this specific trade. The trade will execute without position sizing, portfolio heat, or behavioral checks. Use with caution! By default, riskai is 1 (enabled) if not specified.

Example 9: Executing a Trading Rule

{
  "rule": "my_trading_strategy",
  "symbol": "BTCUSDT",
  "action": "buy",
  "price": 86000,
  "quantity": 1.0
}

Instead of placing a direct order, this executes the trading rule named my_trading_strategy with the webhook data as context. The rule can add custom logic, stop losses, notifications, etc. See the Rule-Based Trading section for details.

Example 10: Triggering a Python Script

{
  "script": "price_alert_handler",
  "symbol": "BTCUSDT",
  "price": 98500.50,
  "alert_type": "resistance_break",
  "timeframe": "1h"
}

Triggers the Python script named price_alert_handler with the webhook payload. The script runs asynchronously and can access the data via get_trigger_payload(). Perfect for complex analysis, custom risk checks, or chaining multiple operations. See the Python Script Execution section for details.

Example 11: Sending a Message to a Long-Running Script

{
  "script_listener": "btc_monitor",
  "alert_type": "resistance_break",
  "symbol": "BTCUSDT",
  "price": 98500.50,
  "volume_spike": true
}

Sends a real-time message to the long-running script named btc_monitor (which must already be running). The script receives the message instantly via Redis pub/sub and can react immediately. Perfect for alerting monitoring bots or sending parameter updates to running strategies. See Message Listeners documentation.