Core Concepts

Core Concepts

Signal Deduplication

Every signal sent to TurboBridge should carry a unique Signal ID. If the same signal ID arrives more than once within the deduplication window, only the first is processed — all subsequent copies are silently dropped.

This protects you from double-trades caused by TradingView firing the same alert multiple times on a single bar close, network retries, or misconfigured Pine Script alert frequency settings.

Always use alert.freq_once_per_bar in your Pine Script to avoid generating duplicate signal IDs at the source.

Unlimited Signals

TurboBridge does not impose daily, weekly, or monthly limits on how many signals your bots can send or receive.

Your strategies can continue operating without app-level usage caps or subscription-based signal restrictions.

That said, some real-world limits still exist outside the platform:

* TradingView applies alert-frequency safeguards. TradingView may temporarily halt alerts if too many alerts trigger within a short time window from the same script instance.

* Exahnges like - Binance enforce API and order-rate limits on trading accounts to maintain exchange stability.

* During periods of extreme volatility, exchanges may take additional time to process or reflect orders on the interface.

TurboBridge also includes internal protection systems to help prevent accidental signal floods, duplicate alerts, and unstable execution behavior caused by misconfigured scripts or runaway automation.

For best reliability, strategies should avoid generating excessive alerts within very short time windows and should use properly structured signal logic with unique signal IDs.

Webhooks — Connecting Signals to Your Bot

Your bot needs a way to receive signals from your strategy.

Most users use TradingView alerts with webhooks, though any platform that supports webhook requests can work with TurboBridge.

A webhook is a secure URL link generated for your bot. When your strategy alert triggers, TradingView sends the alert data to that webhook automatically.

Typical TradingView setup:

* Paste your bot's Webhook URL into the TradingView alert settings

* Add your strategy's alert message payload ("Signal ID" and "Side")

Once connected, your strategy can automatically send BUY, SELL, and EXIT signals directly to your bot for execution.

Long & Short Positions

In Futures trading, you are trading the movement of the market price — not simply buying and holding the coin itself.

This allows traders to take positions in either direction:

* Long Position → expecting the market price to rise

* Short Position → expecting the market price to fall

Because of this, trading opportunities can exist in both bullish and bearish market conditions.

Compared to traditional spot trading, Futures trading gives strategies more flexibility since they are not limited to "buy low and wait for price to go up."

This is one of the main reasons automated strategies commonly use Futures markets — signals can react to market movement in either direction using predefined trading logic.

For your strategy alerts:

* Use BUY signals to enter Long positions

* Use SELL signals to enter Short positions

* Use EXIT signals to close active positions

This structure helps TurboBridge correctly understand and route your strategy signals for execution.

Margin Mode

Binance Futures supports two margin modes:

* Isolated Margin → risk is limited to the individual position

* Cross Margin → positions share available account balance

TurboBridge is designed to operate using Isolated Margin for more predictable and controlled bot execution.

The required margin mode and leverage are configured automatically during bot setup. Changing these settings manually later may cause execution issues or position conflicts.

For best reliability, keep your bot positions in Isolated Margin mode while using TurboBridge and do not change margin or leverage manually on the exchange if you have an active bot.

Auto-Pause Protection

If a bot encounters repeated order failures — such as execution errors or failed TP/SL placement — the platform automatically pauses it. This prevents the bot from continuing to act on signals in a broken state.

You will see the pause reflected immediately on your bot card. You can investigate the cause in your Logs, fix the underlying issue (such as insufficient margin or an expired API key), and resume the bot manually.

Auto-pause is a safety mechanism, not a penalty. It stops further damage when something goes wrong.
Platform & Behavior

Binance Support

TurboBridge currently supports Binance Futures (USDT-margined perpetual contracts). All active USDT-margined pairs on Binance Futures are supported — over 200 pairs including BTC, ETH, SOL, and more.

Support for additional exchanges is planned. When a new exchange is added, existing bots are unaffected. Each bot is tied to a specific exchange at creation time and cannot be migrated.

Core Concepts | TurboBridge | TurboBridge