Control Bots Remotely with Webhooks

Last updated July 19, 2026

Webhooks let an outside service open and close your bot trades, so a charting alert, a signal service, or your own tooling can pull the trigger while tradeSteward handles the order work.

How webhook control works

A webhook is a small message sent to a tradeSteward web address. When the message matches one you configured on a bot, that bot opens a trade or closes its open trades. The most common pairing is an alert platform such as TradingView: your chart condition fires, the alert posts the webhook, and your bot enters.

Every webhook request is authenticated with your Bot Webhook Control Token, a secret key tied to your account.

Turn on webhook controls

  1. Go to Account Settings and find the Bot Preferences section.
  2. Turn on Enable Bot Webhook Controls.
  3. Copy your Bot Webhook Control Token from the same page. Treat it like a password.
  Anyone who has your token can open and close trades on your account. Never share it, and if you suspect it leaked, regenerate it immediately from Account Settings. Regenerating invalidates the old token on the spot, so any webhooks already configured on the client end, such as TradingView alerts, stop working until you update them with the new token.

Configure a bot for webhooks

Edit the bot and open its Webhook Remote Control section. There you will find the webhook URL to send messages to, plus two message fields:

  • Webhook Message to Open: the exact text that tells this bot to enter a trade.
  • Webhook Message to Close All Open Trades: the text that tells this bot to exit everything it has open.

Give each bot distinct messages so a single alert triggers exactly the bot you intend. The full request format, with ready-to-paste examples, lives in the Webhook Request Format Reference.

The bot form's Webhook Remote Control section with the Enabled toggle, the webhook URL, masked token, and the Webhook Message to Open body
Everything an alert platform needs lives here: the URL, your IDs, the masked token, and the exact message body to paste.
  Multi-Entry bots do not support webhooks. Converting a webhook-enabled bot to Multi-Entry disables its webhooks; tradeSteward warns you before the conversion completes.

Example: fire a bot from a TradingView alert

Here is the whole loop, end to end, using TradingView as the alert platform:

  1. Edit your bot, open Webhook Remote Control, and copy two things: the webhook URL and the Webhook Message to Open body.
  2. In TradingView, create an alert for your chart condition. In the alert's notifications settings, enable its webhook option and paste the tradeSteward webhook URL.
  3. Paste the Webhook Message to Open body as the alert's message, exactly as copied.
  4. When the alert fires, TradingView posts the message, and the bot opens its trade using its configured legs, strikes, and stops.
  5. Confirm the round trip on the Webhook Activity page, which logs the received message and the result.

Set up a second alert with the Webhook Message to Close All Open Trades body to exit on an opposite condition. The same pattern works for any service that can post a webhook, not just TradingView.

How webhook trades are sized

If the bot has Set Launch Now/Webhook Size enabled in its entry settings, webhook entries use the bot's own position sizing. Otherwise the size comes from the webhook request itself, as described in the format reference.

  Webhook and Launch Now entries skip entry filter checks. A bot that enters When Triggered trades whenever its message arrives, even if a VIX or underlying filter would have blocked a scheduled entry. Build the conditions into your alert instead.

Watch webhook activity

Open the Bots menu and choose Webhook Activity. Every received webhook is listed with its Time, Bot, Action, Quantity, Source, and Result, so you can confirm alerts are arriving and see how each one was handled.

Availability

Webhook remote control is available on subscription plans that include 15 or more bots. See Choose Your Plan for what each tier includes.

Was this helpful? Thanks for the feedback! Thanks for letting us know. Need a hand? Contact support.
Related
  Monitor Bot Activity and Open Positions Webhook Request Format Reference