IMPORTANT NOTES!
An Isolated margin is not yet supported for API v5.
DCA bots:
If you switched to UTA for Bybit USDT-М, you can trade with or without the Hedge mode turned on. If you still use a Classic account, you must turn on the Hedge mode to trade.
Now, running a multi-pair DCA bot on Bybit USDT-M is available.
Grid bots:
For Classic Bybit USDT Perpetual Accounts:
Run GRID bots exclusively in Hedge Mode.
For Unified Bybit USDT Perpetual Accounts (UTA):
Enjoy the flexibility of running bots in Hedge or One-Way Mode.
Signal bot/SmartTrade:
For UTA account, the Hedge mode is supported for Bybit USDT-M.
Please don't use the subaccounts with UTA turned on, as it may result in an error like Error placing base order: OrderLinkedID is duplicate.
I. Fast Connect.
This method is preferable to be used.
It is valid for both UTA and non-UTA types of Bybit accounts. To learn more about the Unified Trading account (UTA), please read this article.
1. Log into 3Commas and Bybit accounts.
2. Before we continue, please, ensure you don't have active API keys created with Fast Connect.
You can go to the API Management page and delete old API keys created manually or by Fast Connect (this eliminates any possible errors while updating with Fast Connect):
3. On 3Commas, go to the My Portfolio page and click on the Connect a new account button.
If this is your first exchange to be connected, please click on the Connect exchangebutton:
4. Click on Exchanges and choose Bybit.
5. Open the Fast Connect tab and click on the Connect Bybit button
6. Authorize the connection request
7. Confirm the connection
You need to be logged in to Submit the connection.
Please don't change any permissions if you want to connect all the exchanges types:
8. You are done!
All 3 types of accounts are connected:
IMPORTANT NOTE!
If you already connected the exchange to 3Commas, you will receive an error telling you to delete the old API keys and reconnect the exchange with Fast Connect.
II. Update with Fast Connect.
If you need to connect a new API key, here's what to do:
a. Remove the Existing Key: Log in to your Bybit account and manually delete the current API key.
b. Reconnect on 3Commas: Follow the steps below to reconnect your new API key.
1. Go to the My Portfolio page and find the Bybit exchange that needs to be updated.
2. Click on the Update API Key button.
or
3. Click on the Reconnect button.
4. Log into Bybit account and/or Authorize the Request.
5. Confirm the API keys creation:
Please don't change any permissions if you want to reconnect all the exchanges types:
6. Now your connection is updated:
III. Manual API keys creation.
This method is valid for both UTA and non-UTA types of Bybit accounts.
To learn more about the Unified Trading account (UTA), please read this article.
1. Go to Bybit
Log in or create a new account at https://www.bybit.com/.
2. Open the API dashboard
Hover over the profile icon on the top right corner, then click API:
3. Click Create New Key
Note! You must enable 2FA to be able to add API keys.
If you see this dialog, click Confirm:
Click Settings and follow Bybit's instructions to enable 2FA:
4. Choose the System-genetated API Keys
5. Change to Connect to Third-Party Applications and choose 3Commas
6. Select permissions and click Submit
You need to select the following permissions:
Read-Write option;
Orders and Positions in the Contract section;
Trade in the Unified Trading section (needs to be checked in any way);
Trade in the SPOT section.
These permissions are responsible for the following markets:
Contract = Bybit Inverse Perp. market;
Spot = Spot market.
If you want to connect only a SPOT or a Futures account, you can choose them later in step 9.
7. Enter verification codes, then click Confirm
8. Copy API Key and API Secret somewhere safe
Or just don't close this window:
Click on Understood after copy-pasting the API keys.
9. Connect the exchange to 3Commas using created API keys with the help of this article:
For non-UTA accounts, you can choose between 3 markets:
For UTA accounts, you can choose between two markets:
IV. Update with new API keys.
To update the connection with new API keys, please follow the instructions from this article: