Check availability before creating a key
Bybit is on SharkRule’s roadmap and is not available in the current dashboard. This guide explains the provider’s access and permissions. Wait until your dashboard offers the connection before creating or sharing credentials.
This supports global Bybit Spot without leverage or borrowing, not futures, Bybit EU or other regional APIs. Check your eligibility with Bybit; do not bypass restrictions through a region change or VPN.
Create the key on Bybit’s website
- Open https://www.bybit.com/app/user/api-management and sign in. On desktop, API is also available in the profile menu.
- On a smartphone, open the official website in your browser. Bybit says API keys cannot be created in the app. Request the desktop website or use a computer if necessary.
- Choose Create New Key, then a system-generated HMAC key. SharkRule does not accept RSA private keys. Choose manual API trading, not an unrelated third-party application.
- Name the key clearly, for example SharkRule Spot, to recognize it when reviewing or revoking access.
Allow Spot trading, with no wallet permissions
Choose Read-Write and enable Spot trading. SharkRule needs account/balance and order information, plus permission to place Spot orders. Leave futures, options and other unnecessary permissions off.
Keep all Wallet permissions empty: no withdrawals, account transfers or subaccount transfers. Disabling withdrawals alone is insufficient if transfers remain enabled. SharkRule checks the saved permissions.
- Allowlist the exact IP on your signed-in SharkRule connection page, not your phone or home IP. If no server address appears, stop; do not remove the restriction.
- Complete security verification on Bybit, including any required two-factor check. Save the key and secret securely. Never share them through email, chat or screenshots.
When the connection becomes available
Your dashboard will show the supported account type, credential fields and server IP when this connection is available. Follow those instructions then. Verifying a connection and approving a trading strategy are separate steps; reading this guide never activates trading.
Check the cause of a rejected connection
Bybit says new accounts may be unable to create API keys during their first 48 hours. Complete the exchange’s requirements and wait where instructed; another device does not remove an account restriction.
For verification errors, check the key and secret, Read-Write mode, Spot trading, the entirely empty Wallet permission group and saved IP list. Check whether the key expired or belongs to testnet or a regional service. Do not enable extra transfer rights as a workaround.
Remove access at the provider
Review active orders directly at Bybit. Delete the dedicated API key or revoke the API-wallet approval through its official settings to remove that access. Revocation does not sell holdings or undo orders already accepted. If credentials are exposed, revoke promptly and review the account’s activity.
Frequently asked questions
Why can a key be rejected with withdrawals disabled?
Wallet transfer permissions may remain enabled. SharkRule requires that entire permission group to be empty, alongside Read-Write and Spot trading.
Official documentation and references
Prepared with AI assistance from the linked official documentation. Examples are hypothetical; no live account tests or return comparisons were performed.