Updating API keys
Keys are replaced right in the bot settings: send a new pair in one message and the bot keeps working with it. There is no need to recreate the bot, the channels or the settings.
What it is
Replacing the key-and-secret pair on an existing exchange bot. You need it when:
- you reissued the key on Bybit (the old one was deleted or compromised);
- the key has expired — the bot reported “API keys have expired. (You can update them in bot settings)”;
- the key lost its permissions — “Your API key is invalid or lacks required permissions. Update API keys according to the instructions”;
- you want to restrict the key by IP and created a new one for that.
Where in the bot
Main menu → 🤖 Signal Bots → choose a bot → Bot settings → Update API keys.
How to set it up
- Create a new key on Bybit with the required permissions: for a
Bybit Spotbot — spot trading, forBybit Futures— derivatives trading (see API key permissions, IP whitelist and the unified trading account). A copy-trading master account key will not work. - In the bot, tap Update API keys. The bot writes: “Send a pair of API keys separated by a space to replace the current bot API keys”.
- Send the key and the secret in one message, separated by a space, the key first:
AbCdEfGhIjKlMnOpQr 1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p7q8r - The bot checks the format, the length, the uniqueness of the pair, its validity and its permissions. On success: “API keys successfully updated”. If the key was created without an IP restriction, a warning “⚠️ API key without IP whitelist” appears below with the address you can add to the whitelist on Bybit — that is a recommendation, not a requirement.
- Delete the old pair on Bybit so that nobody can use it.
Example
The bot “MY_FUTURES” sent a notification “API keys have expired. (You can update them in bot settings)”. You created a new key on Bybit with the derivatives trading permission and an IP restriction, opened 🤖 Signal Bots → “MY_FUTURES” → Bot settings → Update API keys and sent “key secret”. The answer “API keys successfully updated” means the channels, the trading settings and the Grid and DCA bots on this bot all stayed in place.
Limits and allowed values
| Parameter | Value |
|---|---|
| Input format | Exactly two values separated by a space: the key, then the secret |
| Key / secret length | 18 / 36 characters |
| Uniqueness | The pair must not be registered on any bot |
| Permissions | Spot Trading for a spot bot, Derivatives / Contract for a futures one |
| Copy-trading master account | Not accepted |
| IP whitelist | Recommended, not required |
Common mistakes and what the bot says
- “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 go in one message, separated by a space.
- “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 values again.
- “The data you sent does not match the API key format” — the message contains extra characters or is not a key pair.
- “This API key pair already exists in the system” — this pair is already used by another bot.
- “API key is invalid” / “Failed to verify API keys” — the key was deleted on Bybit, entered with a mistake, or the exchange did not answer; check it and try again.
- “API keys do not have the required permissions” — the key has no permission to trade on this bot's market (see API keys do not have the required permissions).
- “This API key belongs to a copy-trading master account. All your Grid/DCA orders would be automatically copied to your followers. Please use a regular account without copy-trading.”
