Copying a bot
Copying creates a second bot with the same trading settings as the original — the amount, the entries, the targets, the stop, the leverage, the directions and the blacklist are carried over in full. Nothing has to be set up again: it is enough to send a new API key pair.
Where it is in the bot
Main menu → 🤖 Signal Bots → the bot → Bot settings → Copy bot.
When you need it
- The same set of settings on a second Bybit account or subaccount.
- A second bot on the same channel but with different keys — for example, to run part of the trades with a different amount by changing only one setting after the copy.
- A backup bot before experiments with the settings: you copy it, change the copy and the original stays untouched.
How to copy
- In the bot card press Bot settings → Copy bot.
- The bot asks: “Are you sure you want to copy this bot?” — press Confirm copy.
- The bot shows a summary of the original bot and asks: “To copy the bot and its trading settings, you need to set a new pair of API keys for it. To copy this bot, send API keys as text separated by a space”.
- Create a new key pair on Bybit with the required permissions — see API key permissions, IP whitelist and the unified trading account — and send it in one message: the key first, then the secret, separated by a space.
- The bot returns you to the list of bots, where the copy appears.
The keys are checked the same way as when a bot is created: exactly two values, a key of 18 characters and a secret of 36, the pair is not registered in the system yet, and the keys are valid and have the required permissions.
What is carried over into the copy
| What | In the copy |
|---|---|
| The trading settings (all the submenus of Trading settings) | Copied in full |
| The market type (spot or futures) and the exchange | The same as in the original bot |
| The connected channel | Kept |
| The name | The name of the original bot with the mark “(cloned)” — rename it with Rename bot |
| The API keys | New, the ones you sent |
| The trades | Not carried over — the copy starts with a clean history |
| Auto-trade | OFF — switch it on by hand in the card of the copy once you have checked the settings |
The copy takes a slot in the bot limit of your plan exactly like a new bot, see Plans and bot limit.
What is important to know
- The keys must be for the same market type: a spot bot is copied onto spot keys, a futures one onto keys with futures permissions. Spot and futures need different key pairs.
- If the copy works on the keys of the same Bybit account and is connected to the same channel, every signal opens two trades — one per bot. What the bots share and where the conflicts come from is described in Several bots on one account.
- Auto-trade is off in the copy on purpose: first check the Current settings: in the card, then turn the Auto-trade switch on.
Limits and allowed values
| Parameter | Value |
|---|---|
| The API key pair for the copy | New; one pair — one bot |
| Key / secret length | 18 / 36 characters |
| The bot limit | The copy counts as a new bot in the plan limit |
| Auto-trade in the copy | Off until you switch it on |
Common errors and what the bot says
- “This API key pair already exists in the system” — these keys are already linked to another bot; create a new pair on Bybit.
- “Send exactly TWO values separated by a space: the API key first, then the secret key. You sent 1 part(s). Example: AbCdEfGhIjKlMnOpQr 1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p7q8r” — the key and the secret must be in one message.
- “Invalid API key length: 20 chars (must be 18). Copy the full key from Bybit, without extra spaces.” / “Invalid secret key length: 30 chars (must be 36). Copy the full secret from Bybit, without extra spaces.”
- “🔒 Plan limit reached: 3 bots (3 in use). Stop or delete a bot, or switch to a plan with a higher limit.” — the copy does not fit into the subscription limit.
- “The data you sent does not match the API key format” — check that you sent exactly the key and the secret.