AI Summary
Show More
Quickly grasp the article's content and gauge market sentiment in just 30 seconds!
API trading allows external or self-built software connect to a Bybit EU account through an application programming interface, or API. Instead of completing every action manually through the website or app, users can connect software such as trading bots, custom terminals, portfolio dashboards or internal trading systems. Depending on the permissions granted, the connected software can retrieve data, monitor account activity and place or manage orders.
An API is a structured connection between Bybit EU and another software application. API trading can be used to:
Access market data
View balances and account information
Review orders and positions
Place, amend or cancel orders
Monitor order and execution updates
Retrieve permitted transfer or conversion records
Automate predefined trading processes
The API does not create a strategy or independently decide when to trade. It processes requests and instructions generated by the connected software. For example, a user may connect:
A trading bot that places orders when predefined conditions are met
A portfolio dashboard that displays balances and positions
A risk-monitoring system that tracks exposure
A custom trading terminal
A supported third-party application
The general process is:
The user creates an API key in their Bybit EU account.
The user selects what the key is permitted to access.
The key is connected to the selected software.
The software authenticates and sends requests to Bybit EU.
Bybit EU processes the requests and returns the relevant data, confirmation or error message.
The API key’s permissions determine what the connected software can do. A read-only key can retrieve approved information but cannot place or manage orders. A read-write key can perform the specific trading or account actions selected by the user.
A typical API integration uses both REST and WebSocket interfaces.
REST is used to send individual requests or instructions. For example:
Retrieve an account balance
View open orders
Place an order
Amend an order
Cancel an order
Request recent transaction information
Bybit V5 REST requests return a structured response containing a result, a response message and a success or error code.
WebSocket maintains a live connection between Bybit and the connected software. It can be used to receive ongoing updates about:
Market prices
Public trades
Order status
Trade executions
Positions
Account activity
Public WebSocket data does not normally require authentication. Private account and trading data requires an authenticated connection.
Log in to Bybit EU, open the profile dropdown menu and select API.
This opens the API Management dashboard, where API keys can be created, reviewed, edited and deleted.
Select Create New Key in the top-right corner to begin.
Users can choose between a system-generated API key and a self-generated API key.
System-Generated API Key | Self-Generated API Key |
A system-generated API key is created by Bybit EU and uses HMAC authentication.After the setup is completed, Bybit EU provides: An API key An API secret The connected software uses the API secret to sign authenticated requests. This is the standard setup for many trading bots, terminals and other integrations. | A self-generated API key uses RSA authentication.Before completing the setup, the user generates: An RSA public key A corresponding RSA private key The public key is submitted to Bybit EU. The private key remains under the user’s control and is used to sign requests.Bybit EU does not hold the RSA private key. |
The information required depends on the selected key type. Choose one of the following:
API Transaction: Select this option when connecting your own software directly to Bybit EU.
Connect to Third-Party Applications: Select this option when authorizing a supported external platform to connect to your Bybit EU account.
The required information depends on the selected key type.
For a system-generated key, enter a name for the API key. | For a self-generated key: Generate an RSA public and private key pair. Paste the public key into the Your Public Key field. Enter a name for the API key. |
Use a name that clearly identifies the key’s purpose, such as:
Spot Trading Bot
Portfolio Dashboard
Risk Monitoring Tool
Internal Trading System
Select the level of access required by the connected software.
Read-OnlyA read-only key can retrieve permitted information but cannot place, amend or cancel orders.This may be suitable for: Portfolio dashboards Reporting tools Tax software Account-monitoring systems Risk dashboards | Read-WriteA read-write key can perform the trading or account actions selected in the permissions section.Depending on the permissions granted, this may include: Placing orders Amending orders Cancelling orders Managing supported account functions Read-write access should only be enabled when required. |
Users can choose between IP-restricted and unrestricted access.
IP whitelistingOnly requests from approved IP addresses will be accepted.This is the recommended option when the connected software operates from a known server or fixed network location.A single API key can be associated with multiple approved IP addresses. The Bybit EU interface currently allows up to 100 IP addresses to be added to one key. | No IP restrictionThe API key may be used from any IP address.This provides more flexibility but increases the risk if the credentials are exposed. Some sensitive permissions may not be available without IP whitelisting.API keys without an IP address bound to them expire after 90 days. Binding the key to approved IP addresses removes this 90-day expiry condition. |
Choose which trading and account functions the API key can access. Available permissions include:
Unified TradingSpot Trading: View Spot order information and submit or cancel Spot orders. | AssetsAccount Transfer: Transfer assets. Subaccount Transfer: Transfer assets between Main Accounts and Subaccounts, view related transfer records and access the Subaccount list. Bybit Convert / Conversion History: Use Bybit Convert and view asset conversion records. |
Before submitting, review:
The key type
The API key usage
The key name
Read-only or read-write access
IP restrictions
Trading and account permissions
Once submitted, confirm your details via email authentication & Google 2FA
Select Submit once the configuration is correct.
Once submitted, confirm your details via email authentication & Google 2FA
After submiting, you will get a popup with your key key information
The API key name
The API key
The API secret
The selected permissions
The API secret is displayed only once. Copy it immediately and store it securely before selecting Understood. For a self-generated API key, retain the RSA private key created before the setup. The private key should not be submitted to Bybit EU or shared with another unauthorized party.
API secrets and private keys should never be:
Included in screenshots or videos
Stored in public source code
Uploaded to public repositories
Shared through unsecured messages
Provided to unauthorized people
After submission, the key appears in the API Management dashboard.From the dashboard, users can:
Review the key’s permissions
Edit its configuration
Add or update approved IP addresses
Enable a symbol whitelist
Delete the key
The API secret for a system-generated key will no longer be visible after the initial creation screen.
Once your API key is configured, use the Bybit V5 documentation to connect your software, authenticate requests and access the available API endpoints.
[Explore the V5 API Documentation]<https://bybit-exchange.github.io/docs/v5/guide>
For setup questions and ongoing support, join the Bybit API Telegram community.
For further assistance, contact our Customer Support team through Live Chat or submit a case using this form.