Bitget Futures Signal Bot: Automated Trading Enabled via TradingView Signals
Before you start using a Bitget Futures signal bot, read the following carefully:
● You must be a paying subscriber of TradingView (Pro/Pro+/Premium) to be able to use webhooks.
● Do not disclose your webhook URL to others to avoid receiving scams, fraudulent messages, or fake orders submitted by others.
● The TradingView alerts you will be based on your configuration. Bitget shall not be liable for any trading losses.
● Note that the triggering of signals relies on a third-party platform, and there may be a risk of signal loss or delay. Thank you for your understanding.
● This feature is only available for USDT-M perpetual futures trades where the price source is Bitget. Please make sure that the price source is set correctly in TradingView.
● The total fund available for the Bitget Futures signal bot depends on the amount of funds you put into the bot sub-account when you create the bot, and the fund you have in your futures account will not be used as margin, nor will it incur a loss.
● Make sure that your strategy script do not run under hedging mode, because TradingView signal trading is only supported for one-way mode.
● The bot supports multiple trading pairs, but orders will only be placed on pairs where the Bitget Futures signal bot matches the TradingView signal.
Each webhook needs to be configured with a single TradingView alert. If a webhook is configured with multiple TradingView alerts, it will result in abnormal order placing, leading to a loss of funds for which Bitget shall not be held liable.
● Choose the follow mode that matches your desired results based on the strategy function you are calling and your specific strategy script.
If you choose to follow signals after the TradingView's strategy script closes the existing theoretical open positions, then when the bot on Bitget starts running, if there is already a theoretical open position, the signals will not be followed until the position is closed, so that the orders triggered by each signal are the same as the script order expectations.
If you choose to follow from the first signal, then as soon as there is a signal comes in after the bot starts running, it will be followed. Each time the order is executed on Bitget will make your positions on Bitget in line with the script theoretical positions. Note: If you have an existing theoretical position in TradingView's strategy script, or if the signal gets lost in the middle of the process, this may result in a situation where the buy or sell direction or quantity on Bitget does not match the signal. But the direction and quantity of the position will always be corrected when the next signal is transmitted, matching exactly with the strategy script position expectations.
● In order for Bitget to receive signals correctly, it is recommended that qty be defined in the function you call to control the number of orders placed. If not defined in the script, based on the rules of TradingView, the order quantity will be executed according to the default value of "NaN".
This article will explain how to configure and use webhooks on Bitget. Before you start, make sure you are a paying subscriber of TradingView (Pro/Pro+/Premium).
Creating signals on Bitget
First, choose the futures signal bot
Step 1: Create signals
Customize signal names and descriptions based on strategy script
Step 2: Configure the script
Select the USDT-M perpetual futures that has Bitget as its price source
Write your strategy in the TradingView Pine Editor
Note that Webhook signal trading is only used for executing strategies and not for indicators. To determine whether an indicator or a strategy is used on the chart, refer to the initial segment of the Pine Script source code. If "Strategy" is displayed, it means strategy is being used. On the contrary, if "Indicator" is displayed, it indicates that indicator is being used.
Pine Script® language reference manual
Add strategy to the chart
Backtest strategy script ROI
Open bot settings and parameters
Set the initial funds to the amount in your bot subaccount. Although the initial funds parameter does not really affect order placement, it is recommended that you fill in the field with the amount invested in your bot subaccount so that the backtest data will be more accurate.
In order for Bitget to receive signals correctly, it is recommended that you define the order size in the strategy code. If you set the size in the strategy function to "NaN", then only "Order Size" is a mandatory parameter in the setup. TradingView will transmit the size for each order to Bitget according to the default parameter rules. The actual total number of orders that can be placed depends on the available balance in your account.
Step 3: Signal configuration
Click the Alerts icon on the strategy tester to create an alert for your strategy and paste the message template and Webhook URL into the Alerts pop-up window.
Copy the message template from the Bitget page and paste it into the message box in the alert settings.
Copy the Webhook URL from the Bitget page and paste it into the URL box in the alert settings.
Click "Create", and the alert is created. Go back to Bitget to view your signals and create a bot.
Creating a bot with signals
Step 1: Select a trading pair that matches the TradingView strategy
Step 2: Select the signal following mode that meets your expectations
Step 3: Select leverage and deposit the margin for the bot
Step 4: Create the bot
At this point, you have successfully set up your futures signal bot. You will:
● Receive push notifications on the Bitget app or website about the strategy signals
● See the strategy signals your received on the chart of the bot trading page.
● Have your orders executed according to your bot parameters when receiving signals
Note: Orders placed on Bitget at the time of receiving signals are market orders, limit orders are not supported for the time being. In order to avoid excessive deviation of the order price, please select the price source as USDT-M perpetual futures trading pairs on Bitget.
Viewing signal details
To view the details of the signal, click the Details button next to it, then you will see the Webhook URL and message template. Additionally, you can view a log of the signals sent from TradingView.
Viewing bot details
Switch to the "Current bot" tad to view the details of the signal bot.
Termination of the futures signal bot
Terminate manually
Upon manual termination, the open positions in your bot will be closed at market price.
Terminate automatically
Webhook signal bot may be automatically terminated in the following cases:
1、 Your position gets liquidated
2、 Your account gets restricted
3、 The loss of your signal, if detected, may also lead to the termination of your bot.
Amount limits
Each user can create up to 10 signals at once, and each signal can be associated with up to 20 strategies at the same time. You will not be able to create new signals or strategies after reaching the above limits.
Order restrictions
Note that orders submitted through the Webhook bot are subject to the same order restrictions as manually placed perpetual futures trading orders, including minimum or maximum order sizes, Futures price limitations, etc.
Reasons for webhook signal bot order placing failure:
| Error message |
Note |
| Signal reception is delayed and the order has been canceled. |
Signal delayed. Placing an order and executing it now may cause the order to deviate. The order was canceled as a result. |
| The trade pair is invalid and the order failed. |
Trading pair not supported or delisted by Bitget |
| The order parameters are missing. Please copy and paste them again and use the message template. |
The parameter settings are incomplete. Please run Webhook again. |
| Balance available is insufficient to place an order. |
Your margin balance is insufficient to place an order. Please make a transfer to your futures account or unified account. |
| The risk limit was exceeded and the order failed to execute. |
Placing an order will exceed the currently set risk limit. You can adjust your risk limit in the "Trading preferences" section. |
| The maximum number of open positions is exceeded and the order cannot be placed. |
Placing an order will exceed the maximum number of open positions allowed. |
FAQ
1. Do I need to fill in all the parameters on TradingView?
In order for Bitget to receive signals correctly, it is recommended that you define the order size in the strategy code. If you set the size in the strategy function to "NaN", then only "Order Size" is a mandatory parameter in the setup. TradingView will transmit the size for each order to Bitget according to the default parameter rules. The actual total number of orders that can be placed depends on the available balance in your account.
Although the initial funds parameter does not really affect order placement, it is recommend that you fill in the field with the amount invested in your bot subaccount so that the backtest data will be more accurate.
2. How is the futures trading order size controlled on TradingView?
Each strategy script must have a bot function called. Please define qty in your bot script. If the quantity parameter is "NaN", set "OrderSize" in the property settings to "Futures" mode. For USDT-M perpetual futures, 1 contract is equal to 1 token, and entering the order size as a percentage of USD value or net value may result in a failed order. This is due to the fact that TradingView and Bitget have different logic for calculating contract values.
3. How do I adjust the order size?
It is recommended that you control the order size through the quantity parameter in the bot function. Please note that once you change your order size, you must also save the changes to your bot alerts.
4. How do I save my strategy changes to my strategy alerts?
Whenever any changes are made to your strategy settings (including inputs, parameters, etc.), you must save the changes to the strategy alerts to make sure that the signals sent to Bitget for order placement are also updated.
To save changes to your strategy alerts, go to Alerts located on the right side of the TradingView page and click on the Settings icon to edit your strategy alerts. Select the latest changes to the alerts from the "Conditions" drop-down list and click "Save".
5. Can I change my Webhook message template?
We do not recommend modifying the message template as it is critical to send signals from the TradingView to the Bitget to successfully place an order.
6. Why do I see my Webhook signal triggered but no transaction history is displayed?
This is most likely due to missing or incorrect property settings for the strategy on TradingView, such as an order size entered that does not meet the minimum order size requirement or a message template that is not copied correctly.
For detailed information, click Signal Log to view the signal source code.
7. How can I check the status of my orders?
Go to Strategy details to check the status of your orders. If your order fails, move your cursor on the order to see why.
8. What are the limitations of Webhook signal trading?
The TradingView Webhook feature is designed to send alerts and notifications to external systems or services when certain conditions are met. While it can be used for a variety of purposes, like executing trades, there are some limitations that need to be considered when placing orders through the TradingView Webhook:
Functionality: The TradingView webhooks are primarily used to send signals or alerts to external systems. They provide a way to trigger actions in response to certain events on the chart, but they do not have the built-in functionality to execute trades directly or place orders on the exchange. Therefore, when Bitget receives a signal, the market order is executed.
Limitations of webhooks: webhooks are typically used for one-way communication where TradingView sends data to an external system. Placing an order, however, requires a two-way communication process where the trading platform confirms the order as placed and provides feedback or status updates. Webhooks alone may not provide the two-way communication needed to place an order.
9. Pine Script® language reference manual
See Pine Script® language reference manual for details.
