Prepare the credentials#
Use a system-generated API key and secret compatible with the selected Bybit account form. Match mainnet or testnet credentials to that form’s environment. Regional Bybit services may use different endpoints and account rules.
Bybit’s official guide distinguishes HMAC key/secret credentials from self-generated RSA credentials. A key/secret form should not be filled with an RSA private-key file. Read Bybit’s current API guidance ↗.
Link the account in Schizo Terminal#
- Open the account manager and choose the appropriate Bybit entry.
- Name the account and enter its key and secret on your device.
- Match the product and testnet setting to your exchange account.
- Save the account, select it in the header and check private balances or positions.
Keep the device clock synchronized. Bybit checks request timestamps, so an incorrect clock can cause authentication failures even with the correct key.
If the account does not connect#
Check read/trade permissions, the key’s IP restrictions and whether the selected regional service is supported by the available form. A public Bitcoin chart does not confirm private account access.
Once connected, review the active account and contract before using the order-entry controls. Order availability and minimum quantities come from the exchange.