A connection to your existing exchange account.
An API key identifies an application connection to an exchange account. The associated secret signs requests so the exchange can check their authenticity. Some exchanges request an additional API passphrase. These credentials are separate from your terminal sign-in and your exchange website password.
Account access remains subject to the exchange’s permissions, product eligibility and security rules. Public charts can work without private credentials; balances and account actions require authenticated requests.
Read access and trading access do different jobs.
Read permissions let a connection request account information such as balances, positions and orders. Trading permissions allow supported instructions such as creating, amending or cancelling orders. A read-only key can therefore show account information while an order is rejected.
Enable only the permissions needed for your intended workflow. Withdrawals are not required for Schizo Terminal’s trading workflow. Set the permissions in the exchange’s API-management interface, then verify the connection using private data.
Match the environment and allowed network.
Live, Demo and Testnet are distinct environments where an exchange offers them. A key created for one is not a universal credential for the others. Choose a terminal connection that supports the intended environment, rather than changing a label and reusing the same credentials.
IP allowlists restrict the network addresses the exchange accepts. Schizo’s exchange traffic passes through the deployment’s relay, so the address seen by the exchange may differ from the public IP of your browser device. Use the current addresses for your actual deployment; another product’s published IP list will not establish access.
Understand what stays on the device.
Schizo stores exchange credentials in an encrypted device vault. Request signing happens on the device. Signed requests, API-key identifiers and exchange responses pass through the relay in memory. This design should be understood using the complete data-handling explanation, rather than assuming that a relay never sees account-related information.
Signing into a new browser does not automatically copy the vault. Export an encrypted backup when moving the setup. Clearing site data can remove the local vault and its device key.
Check a new connection methodically.
- Choose the supported exchange, product and environment.
- Name the connection clearly and enter its requested credentials on your device.
- Check that private balances, existing orders or positions load.
- If rejected, inspect permissions, environment, IP restrictions and device time.
- Review the intended account and contract before using the order controls.
For exact steps, use Connect an exchange or the Bybit setup guide. Do not include secret values when reporting a connection problem.