How to create a Bybit API key manually

The easiest way to connect Bybit is the 🔐 Log in with Bybit button — the key is created automatically, see Log in with Bybit. A key you create yourself is needed, for example, for a second bot on the same Bybit account or if you want to choose the permissions and the IP binding yourself. It takes a couple of minutes.

Before you start

• A key can be created only on the Bybit website — the Bybit app has no such section. It is most convenient from a computer.
• Bybit may not let a new account create a key during the first 48 hours after registration.
• Bybit asks you to confirm the key creation with a two-factor code (Google Authenticator).
• Spot and futures need two different bots and two different keys. The steps are the same for both.

The names below are as on the English version of the Bybit website.

How to create the key

1. Log in on the Bybit website and open API management: the profile icon in the top right corner → API. Direct link: https://www.bybit.com/app/user/api-management
2. Click Create New Key.
3. In the key type window, choose System-generated API Keys.
4. In the API Key Usage block, leave API Transaction. In the Name for the API key field, enter any name, for example SYNC.
5. In the API Key Permissions block, choose Read-Write. With a Read-Only key the bot cannot trade.
6. Choose the IP restriction:
   • Only IPs with permissions granted are allowed to access the OpenAPI — and enter the SyncTrade server address 45.144.176.241 in the field. Recommended: such a key never expires and does not work from someone else's address;
   • No IP restriction — the key works from any address, but Bybit disables it 90 days after it is created. The bot reminds you in advance to replace it.
7. In the permissions table, tick Unified Trading — this checkbox turns on futures orders and positions and spot trading, and it is enough for a bot of any type. Do not tick the Earn and Assets blocks (wallet: transfers and withdrawals). If the list has P2P permissions, do not tick them either.
8. Click Submit and enter the confirmation code.
9. The Key successfully added window opens with the API Key and API Secret fields. Copy both with the Copy buttons: Bybit shows the secret only once, you cannot view it later. Click Understood.

How to send the key to the bot

• A new bot: 🏠 Home → 👛 Portfolio → ➕ Connect an exchange → exchange → trade type → name. On the screen “Send API keys as text separated by a space”, send one message with the key first, then the secret, separated by a space: AbCdEfGhIjKlMnOpQr 1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p7q8r. The bot deletes this message from the chat right away.
• Replacing the key of an existing bot: the bot card → 🔑 API keys, then the same way.
• On the website: Portfolio → Accounts → Add account — the API Key and API Secret fields, then confirmation in Telegram. See Exchange accounts on the website.

This article is opened by the 📖 How to create a Bybit key manually button on the key entry and key replacement screens in the bot, and on the website — by the “How to create a key on Bybit — step by step” link in the keys form.

The bot checks the key on the exchange. If the key was created without an IP binding, the bot shows “⚠️ API key without IP whitelist” with the server address once — this is a hint, not an error.

Limits and allowed values

Parameter	Value	Note
Where to create	Bybit website only	The Bybit app has no such section
Key type	System-generated API Keys	—
Permissions	Read-Write and Unified Trading	Fits both spot and futures
Withdrawals, P2P	Do not tick	The bot will not accept a key with them
Server address for the binding	45.144.176.241	A key bound to an IP never expires
Key without an IP binding	Valid for 90 days	Then Bybit disables it
One key	One bot	Spot and futures — a key each
Key / secret length	18 / 36 characters	Copy in full, without spaces

Common errors and what the bot says

• The Bybit app has no API section — this is normal: the key is created on the Bybit website.
• Bybit does not let a new account create a key — wait 48 hours after registration.
• “This API key is read-only. The bot needs trading permissions: create a key with Orders and Positions permissions.” — Read-Only was chosen at step 5. Create the key again with Read-Write.
• “API keys do not have the required permissions” — the Unified Trading checkbox is not ticked.
• “This API key has the withdrawal permission enabled…” — the Assets block is ticked. Remove the withdrawal permission in the key settings on Bybit or create the key again.
• “API key is invalid” / “Failed to verify API keys” — check that the key and the secret are copied in full and that the address at step 6 has no typos: 45.144.176.241.
• “Invalid secret key length: 30 chars (must be 36)…” — the secret was not copied in full. If the window with the secret is already closed, it cannot be recovered: delete the key on Bybit and create a new one.
• “This API key pair already exists in the system” — this key is already connected to another bot. For a second bot, create one more key.