Dear traders,
A new field, xstockMultiplier, has been added to the GET /v5/market/instruments-info AND /v5/account/instruments-info response when category=spot.
Note
- This field is only meaningful when symbolType=xstocks. For all other symbol types, it returns a default value of "1".
- The value reflects cumulative adjustments from corporate actions (dividends, stock splits, reverse splits) on the underlying US equity.
- Values may appear as high-precision decimals (e.g., "1.0000658218334353"). This is expected — minor deviations from 1 are caused by accumulated dividend adjustments, not data errors.
How to Use
You can apply this multiplier to calculate the actual price and quantity of an xStocks token relative to its underlying US stock:
- Adjusted Price = xStocks Token Price / xstockMultiplier
- Adjusted Quantity = xStocks Token Quantity × xstockMultiplier
This is an additive change and will not impact existing integrations.
Dear Traders,
Bybit plans to list CLUSDT Perpetual Contract (Oil Perps) on 24 Mar.
Before trading this contract, you are required to sign the oil agreement. You may complete the agreement via Web/App once the contract is officially listed. However, to ensure you can start trading immediately when the contract goes live, we recommend completing the agreement in advance via the Open API.
Agreement Signing API (category=3):
https://bybit-exchange.github.io/docs/v5/user/sign-agreement
Note: Only the master account is required to sign the agreement. Once completed, all subaccounts will be eligible to trade.
Mark/Index Price Calculation:
https://www.bybit.com/en/help-center/article/Introduction-to-TradFi-Perpetual-Contracts
Oil Perps Agreement:
https://www.bybit.com/en/legal/service-specific-terms/Derivative-Contract-Terms-Oil-Perps
If you attempt to trade without signing the agreement, the following error will be returned:code=110125, msg=You must agree to the Trading Terms before trading this contract
Once the contract is live, you can retrieve the trading parameters via the API. The contract will have symbolType="commodity", which can be filtered through Get Public Instrument Info or Get Account Instrument Info
Please complete the agreement in advance to avoid any delay when trading becomes available.
Websocket Spot Orderbook Level 200 Update
Dear Traders,
We are pleased to inform you that the push frequency for the Websocket Spot Orderbook Level 200 data will be improved from 200 ms to 100 ms
https://bybit-exchange.github.io/docs/v5/websocket/public/orderbook
Go-Live Time:
March 19, 2026, at 7:00 AM (UTC)
If you have any questions, please feel free to contact our Support team.
The Bybit Team
Dear Users,
Starting Mar 17, 2026 (gradual rollout, fully released on Mar 24, 2026), BYUSDT will be supported as a repayment asset.
Users will be able to use BYUSDT to repay liabilities via the following API endpoints:
Repayment endpoints:
◦ https://bybit-exchange.github.io/docs/v5/account/repay
◦ https://bybit-exchange.github.io/docs/v5/account/repay-liability
◦ https://bybit-exchange.github.io/docs/v5/account/no-convert-repay
For more details, please refer to the changelog:
https://bybit-exchange.github.io/docs/changelog/v5#2026-03-24
The Bybit Team
Dear Traders,
Bybit plans to list XAUUSDT and XAGUSDT Perpetual Contracts.
Before trading these contracts, you are required to sign the relevant trading agreement. You may complete the agreement via Web/App once the contracts are officially listed. However, to ensure you can start trading immediately when the contracts go live, we recommend completing the agreement in advance via the Open API.
Agreement Signing API:
https://bybit-exchange.github.io/docs/v5/user/sign-agreement
Note: Only the master account is required to sign the agreement. Once completed, all subaccounts will be eligible to trade.
Mark/Index Price Calculation:
https://www.bybit.com/en/help-center/article/Introduction-to-TradFi-Perpetual-Contracts
Trading Agreement:
https://www.bybit.com/en/legal/service-specific-terms/Derivative-Contract-Terms-TradFi-Perps
If you attempt to trade without signing the agreement, the following error will be returned:code=110123, msg=You must agree to the Trading Terms
Once the contracts are live, you can retrieve the trading parameters via the API. These contracts will have symbolType="commodity", which can be filtered through Get Public Instrument Info or Get Account Instrument Info
Please complete the agreement in advance to avoid any delay when trading becomes available.
Upcoming Listing: XAU & XAG Perpetual Contracts
We are pleased to share that XAU (Gold) Perpetual and XAG (Silver) Perpetual contracts will be listed soon.
Please review the important updates below:
1. Agreement Signing Required
A new endpoint will be available shortly:
POST /v5/account/agreement/sign
Master account must complete the required agreement signing before trading XAU or XAG perpetual contracts.
2. API Documentation Updates
- Market Instruments
https://bybit-exchange.github.io/docs/v5/market/instrument
- Account Instruments
https://bybit-exchange.github.io/docs/v5/account/instrument
Response messages will introduce a new symbol type: "commodities".
Please stay tuned for the official announcement for full details, including launch timing and trading specifications.
If you have any questions, please contact your Relationship Manager or our Support Team.
The Bybit Team
Dear Institutional Clients,
To further enhance the robustness and market adaptability of the trading system and optimize the risk control effectiveness of the spot trading price limit mechanism, our exchange plans to adjust the update rules for the price limit parameters in the current spot trading price limit mechanism. The relevant matters are hereby announced as follows:
1. Details of the Adjustment
Effective from the date of implementation, the parameters X and Y in the spot trading price limit mechanism will be adjusted as follows:
Update Frequency: Once per week
Update Time: Every Monday at 06:00 UTC
Update Method: Automatically updated by the system, no manual intervention required
2. Update Logic Explanation
The update of the spot trading price limit parameters will be dynamically calculated based on the comprehensive indicator score of the corresponding trading pair over the past 30 days. The comprehensive indicator score will be evaluated using multi-dimensional market data (including but not limited to liquidity, volatility, and trading activity) to ensure that the price limit parameters more accurately and promptly reflect market conditions.
3. Parameter Details Inquiry
For specific price limit parameters of each trading pair and related information, please refer to the following official page:
👉 https://www.bybit.com/en/announcement-info/spot-trading-rules/
You can obtain the price limit parameter values via the following API:
👉 https://bybit-exchange.github.io/docs/v5/market/instrument
You can obtain the highest bid price and lowest ask price via the following API:
👉 https://bybit-exchange.github.io/docs/v5/market/order-price-limit
4. Impact Explanation
This adjustment only involves the update mechanism of the spot trading price limit parameters and does not affect the existing trading rules or matching logic. Institutional clients are advised to evaluate and adjust their systems and risk control strategies accordingly in advance.
If you have any questions about this adjustment, please feel free to contact us through official channels. Thank you for your continued support and trust in our exchange.
Notice hereby given.
Bybit Spot Risk Control Team
Release Date: February 1, 2026
Dear traders,
As the data volume continues to grow, Bybit will update the API rate limit for the Transaction Log endpoint to help prevent potential service instability caused by high server load.
Rate limit change
• Before: 50 requests per second per user ID
• After: 30 requests per second per user ID
Affected endpoint
Get Transaction Log: /v5/account/transaction-log
Deployment time
5 Feb 2026, 02:00 UTC
Please adjust your integration accordingly to avoid being rate limited after the change.
If you have any questions, feel free to contact us.
Dear traders,
To strengthen stability and risk controls for UTA Loan manual repayments, we're upgrading:
- How we calculate coin-conversion repayment fees
- The repayment limit for coin-conversion repayments
This update takes effect on Feb 10, 2026, 8AM UTC.
Please refer to: https://announcements.bybit.com/en/article/uta-loan-manual-repayment-update-bltbef3f1ad72a8295d/
Upcoming Update: Fee Rate Endpoint Infrastructure Optimization
Dear Users,
To improve system stability and reduce the load, we will update the Fee Rate Query API underlying service.
GET /v5/account/fee-rate
Documentation: https://bybit-exchange.github.io/docs/v5/account/fee-rate
Effective Date: January 20, 2026
After the switchover, the fee rate query will no longer be returned in real-time. As a result, responses may experience a slight additional latency of approximately 10–20 ms. Other functionalities and response structures remain unchanged.
This change helps enhance overall system performance, stability, and reliability for all users.
If you have any questions or feedback, please feel free to contact us.
The Bybit Team
📢 Important Announcement — MNT Repay Feature Update
Dear OpenAPI Users,
We would like to inform you of an important update regarding the MNT Repay and Repay All features.
Due to ongoing system maintenance, the following features are temporarily unavailable.
Effective Dec 18, 2025, 03:00 (UTC):
UI (Web/App)
- Repaying MNT using non-MNT assets is temporarily unavailable.
- Selecting MNT as repayment coin via One-Click Repay All is temporarily unavailable.
API
The following temporary changes apply:
- Manual Repay with Asset Conversion ( POST /v5/account/repay )
➜ MNT is temporarily not supported by this endpoint.
- Manual Repay Without Asset Conversion ( POST /v5/account/no-convert-repay )
➜ MNT remains supported and can still be used as a repayment asset.
Relevant API Documentation
- Manual Repay (MNT not supported):
https://bybit-exchange.github.io/docs/v5/account/repay
- Manual Repay Without Asset Conversion (MNT supported):
https://bybit-exchange.github.io/docs/v5/account/no-convert-repay
We will provide further updates once the maintenance is completed and the features are restored. Repayment for other coins is not affected.
We appreciate your understanding and continuous support.
Dear INS Loan Users,
Under certain circumstances, the LTV ratio cannot be calculated accurately. To avoid confusion, Bybit will update the response structure of the Get LTV API (https://bybit-exchange.github.io/docs/v5/otc/ltv-convert). Please make sure to adapt to this change in advance.
Changes:
1. A new field liqStatus (integer) will be added.
Values:
• 0 — Normal (default)
• 1 — Liquidating
• 2 - Manual repaying
• 3 - Transferring
2. When liqStatus != 0:
• ltv, unpaidAmount, balance will return an empty string ""
• unpaidInfo, balanceInfo will return an empty array []
Example:{"retCode": 0,"retMsg": "","result": {"liqStatus": 3,"ltvInfo": [{"liqStatus": 3,"ltv": "","parentUid": "1002883059","subAccountUids": ["1002883059"],"unpaidAmount": "","unpaidInfo": [],"balance": "","balanceInfo": [],"rst": ""}]},"retExtInfo": {},"time": 1765372838052}
Effective Time:
Mainnet: Deployment will be started from 02:00 UTC, 25 Dec
Dear OpenAPI Users,
We would like to inform you of an upcoming API deprecation related to the Market Delivery Price endpoint.
Deprecation Notice:
GET /v5/market/delivery-price will be deprecated on December 11, 2025:
(Reference: https://bybit-exchange.github.io/docs/v5/market/delivery-price)
Replacement Endpoint:
Please migrate to the new endpoint below:
GET /v5/market/new-delivery-price
(Reference: https://bybit-exchange.github.io/docs/v5/market/new-delivery-price)
We recommend updating your integration as soon as possible to ensure continued access to delivery price data.
Dear Traders
We’re enhancing the Unified Trading Account (UTA) Manual Borrowing experience. A new fixed-rate borrowing option will roll out in phases starting Dec 08, 2025 (the full launch date may vary based on readiness).
Please refer to:
https://announcements.bybit.com/en/article/bybit-uta-manual-borrowing-fixed-rate-option-coming-soon-bltbc3b81ddfc8563cd/
Dear Option Traders,
Due to the high server load currently observed on the Option instrument endpoint, we will be implementing an urgent adjustment to its traffic rule.
New Rate Limit (per IP):
• 40 requests per second
• 100 requests per 10-second window
Affected Endpoint:
/v5/market/instruments-info (category=option)
Effective Time:
08:00 UTC, November 6, 2025
Please let us know if you have any concerns or feedback regarding this change.
Dear Trader,
To further enhance our derivatives offerings, we are pleased to announce the upcoming launch of XAUT USDT-margined Futures and Options contracts. The launch schedule is as follows:
XAUT Futures and Options
- Mar 30, 2026, 8AM UTC: Launch of XAUTUSDT Futures contracts expiring Apr 3 and Apr 10
- Mar 31, 2026, 8AM UTC: Launch of XAUTUSDT Options contracts expiring Apr 1 and Apr 3
- Apr 1, 2026, 8AM UTC: Launch of XAUTUSDT Futures contracts expiring Apr 17 and May 29
- Apr 2, 2026, 8AM UTC: Launch of XAUTUSDT Options contracts expiring Apr 4, Apr 5, Apr 10, Apr 17, Apr 24 and May 29
Starting Apr 3, 2026, XAUT Options contracts will be generated on a regular basis.
If you have any questions or need assistance, our Customer Support team is always available to help.
Thank you for your continued trust and support.
Best regards,
The Bybit Team
🚀 Bybit AI Skills Just Got an Upgrade
Smarter tools. Greater control. More secure execution.
Here’s what’s new 👇
🤖 Copy Trading – Instantly discover and follow top-performing traders
⚙️ Advanced Bots – Spot Grid, DCA, Futures Grid, Martingale, and more
📊 Strategy Trading – Chase Limit, Iceberg & TWAP now live
🔐 Dual-Source Verification – Enhanced protection against supply chain attacks
Trade smarter. Build faster. Execute with confidence.
🔗 https://www.bybit.com/ai
🔗 https://github.com/bybit-exchange/skills
Dear Traders,
We’re excited to introduce Bybit AI Hub (https://www.bybit.com/en/ai), a new initiative designed to make it easier for developers and AI agents to connect directly with Bybit services.
With Bybit AI Hub, you can seamlessly integrate your AI agents with Bybit through official tools and APIs.
What’s available now:
◦ Official Skills are now ready for use: https://github.com/bybit-exchange/skills
◦ OpenAPI Specifications have been updated to support AI integrations
◦ More AI agent features will be released soon to further enhance automation and intelligent trading workflows
Stay tuned as we continue expanding the AI ecosystem on Bybit.
The Bybit Team
Dear Traders,
Delta Neutral Mode is now available.
Delta Neutral Mode is designed to enhance the trading experience for users running delta-neutral strategies. When enabled, positions that meet the Delta Neutral criteria will be ranked lower in the ADL (Auto-Deleveraging) queue, reducing the risk of being auto-deleveraged during extreme market conditions.
For more details, please refer to the help article:
https://www.bybit.com/en/help-center/article?id=1772092051700
The corresponding OpenAPI endpoints are now live. For implementation details, please refer to:
https://bybit-exchange.github.io/docs/v5/account/set-delta-mode
https://bybit-exchange.github.io/docs/changelog/v5#2026-03-12
The Bybit Team
Dear Traders
To better support users running hedging strategies, we will officially launch Delta-Neutral Mode on Mar 12, 2026.
This feature is available to VIP 3 and above users with a UTA 2.0 account.
For more details, please refer to the official announcement:
https://announcements.bybit.com/article/delta-neutral-mode-now-available-bltf867a117c6432821/
The Bybit team
Important Update to Perpetual Contract Funding Settlement Frequency
Dear Traders,
Starting from February 26, 2026, at 3:00 AM UTC, if a Perpetual Contract’s funding settlement frequency has been automatically adjusted to 1 hour, it will revert to its default settlement interval once the specified threshold conditions are met.
Please refer to the official announcement for full details:
https://announcements.bybit.com/article/important-update-to-perpetual-contract-funding-settlement-frequency-blt9e1f8c588fe457c7/
Thank you for your continued support.
Best regards,
The Bybit Team
Dear traders,
To enhance account security, Bybit will restrict IP whitelist and fiat-related permission modifications for master account API keys via Open API.
If you need to perform these operations, please proceed through the Bybit website.
Before the change:
You could add/remove IP whitelist entries and modify fiat-related permissions via API.
After the change:
You will no longer be able to add/remove IP whitelist entries or modify fiat-related permissions via API.
Affected endpoint:
Modify Master API Key
https://bybit-exchange.github.io/docs/v5/user/modify-master-apikey
Deployment time:
10 Feb, 2026, 02:00 UTC
If you have any questions, please feel free to contact us.
Dear traders,
To strengthen stability and risk controls for Crypto Loan manual repayments, we're upgrading:
• How we calculate coin-conversion repayment fees
• The repayment limit for coin-conversion repayments
This update takes effect Jan 28, 2026, 8AM UTC.
Please refer to: https://announcements.bybit.com/article/crypto-loan-manual-repayment-update-bltde33509ddde5e8fd/
Dear Users,
Due to adjustments in our technical roadmap, the Set Auto Repay Mode endpoint functionality will be postponed.
Affected Endpoint:
POST /v5/spot-margin-trade/set-auto-repay-mode
Documentation:
https://bybit-exchange.github.io/docs/v5/spot-margin-uta/set-auto-repay-mode
Effective Date:
January 8, 2026, 02:00 (UTC)
We recommend planning your integration and using this endpoint after the effective date. Please adjust your implementation accordingly.
If you have any questions or feedback, please feel free to contact us.
Thank you for your understanding.
The Bybit Team
Upcoming Feature: Auto-Repay Mode for Spot Margin Trading
Dear Traders,
We are pleased to announce the upcoming launch of the Auto-Repay Mode for Spot Margin trading, along with two new API endpoints that allow users to configure and query this feature.
New Endpoints:
1. Set Auto-Repay Mode
POST /v5/spot-margin-trade/set-auto-repay-mode
Configure whether to enable or disable Auto-Repay for a specific currency.
Documentation: https://bybit-exchange.github.io/docs/v5/spot-margin-uta/set-auto-repay-mode
2. Get Auto-Repay Mode
GET /v5/spot-margin-trade/get-auto-repay-mode
Check whether Auto-Repay is currently enabled for Spot Margin trading.
Documentation: https://bybit-exchange.github.io/docs/v5/spot-margin-uta/get-auto-repay-mode
Feature Behavior:
When Auto-Repay is enabled for a specific currency, the system will automatically execute repayments without asset conversion at 00 and 30 minutes every hour.
Transfers or Spot trading activities (buy/sell) will increase the user’s spot available balance but will not trigger immediate repayment.
Effective Time:
Testnet: Already live
Mainnet: January 6, 2026
Thank you for your continued support.
The Bybit Team
Dear OpenAPI Users,
Based on feedbacks from institutional clients, we have made several requirement adjustments to the previously announced changes (Ref: /channel/Bybit_API_Announcements/386).
We would like to inform you of upcoming updates to the ADL Alert and Insurance Pool data refresh mechanisms for both REST API and WebSocket endpoints.
These changes will take effect on Mainnet starting December 18.
1. REST API Updates
1.1 Endpoint: GET /v5/market/adlAlert
Documentation:
https://bybit-exchange.github.io/docs/v5/market/adl-alert
Key Changes:
For shared insurance pool, the "balance" field will follow a T+1 refresh mechanism and will be updated daily at 00:00 UTC.
The "maxBalance" field will be deprecated and will return an empty string.
1.2 Endpoint: GET /v5/market/insurance
Documentation:
https://bybit-exchange.github.io/docs/v5/market/insurance
No changes. This endpoint will remain unchanged.
2. WebSocket Updates
2.1 Topic: adlAlert.{coin}
Documentation:
https://bybit-exchange.github.io/docs/v5/websocket/public/adl-alert
Key Changes:
For shared insurance pool, the "b" field will follow a T+1 refresh mechanism and will be updated daily at 00:00 UTC.
The "mb" field will be deprecated and will return an empty string.
The other fields remain unchanged.
2.2 Topic: insurance
Documentation:
https://bybit-exchange.github.io/docs/v5/websocket/public/insurance-pool
No changes. This topic will remain unchanged.
Effective Time:
Mainnet: December 18
If you have any questions or require further clarification, please feel free to reach out to us.
Thank you for your continued support.
Dear openAPI Users,
We would like to inform you of upcoming updates to the ADL Alert and Insurance Pool data refresh mechanisms for both REST and WebSocket endpoints.
These changes will take effect on Mainnet starting December 18.
1. REST API Updates
1.1 Endpoint: GET /v5/market/adlAlert
Documentation: https://bybit-exchange.github.io/docs/v5/market/adl-alert
Key Changes:
Data refresh frequency will change to once every 24 hours, updated daily at 00:00 UTC, replacing the previous 1-minute update cycle.
"balance" field will follow T+1 refresh, updated daily at 00:00 UTC.
"maxBalance" field will be deprecated and will return an empty string.
1.2 Endpoint: GET /v5/market/insurance
Documentation: https://bybit-exchange.github.io/docs/v5/market/insurance
Key Changes:
Both isolated and shared insurance pool balances will now update every 24 hours, at 00:00 UTC.
"balance" field will follow T+1 refresh, updated daily at 00:00 UTC.
2. WebSocket Updates
2.1 Topic: adlAlert.{coin}
Documentation: https://bybit-exchange.github.io/docs/v5/websocket/public/adl-alert
Key Changes:
"b" field will follow T+1 refresh, updated daily at 00:00 UTC.
"mb" field will be deprecated and will return an empty string.
2.2 Topic: insurance
Documentation: https://bybit-exchange.github.io/docs/v5/websocket/public/insurance-pool
Key Changes:
"balance" field will follow T+1 refresh, updated daily at 00:00 UTC, replacing the 1-second push.
Effective Time:
Mainnet: December 18
If you have any questions, feel free to reach out to us.
Thank you for your continued support.
Dear OpenAPI Users,
Following our earlier announcement /channel/Bybit_API_Announcements/383 (https://announcements.bybit.com/en/article/bybit-uta-manual-borrowing-fixed-rate-option-coming-soon-bltbc3b81ddfc8563cd/) regarding the upcoming introduction of the UTA Manual Borrowing Fixed-Rate option, we would like to provide important clarifications for OpenAPI users regarding the December 8 release version.
Key Notes for OpenAPI Users:
1. Borrowing via OpenAPI endpoint (https://bybit-exchange.github.io/docs/v5/account/borrow) will support floating-rate borrowing only in this release.
2. Repayment behavior via OpenAPI endpoints (https://bybit-exchange.github.io/docs/v5/account/no-convert-repay or https://bybit-exchange.github.io/docs/v5/account/repay):
The system will repay floating-rate liabilities first, followed by fixed-rate
Thank you for your continued support.
Bybit Team
Dear Traders,
To provide a more responsive and efficient market data experience, the push frequency of OrderBook level 1000 will be adjusted from 300 ms to 200 ms.
Effective Time:
Nov 25th, 2025. around 7:00 UTC
What’s Changing:
Push Frequency of Spot & Futures OB Level 1000: 300 ms → 200 ms
Please refer to: https://bybit-exchange.github.io/docs/v5/websocket/public/orderbook
If you have any questions, please feel free to contact us.
Best regards,
Bybit Team
Title: Update to WebSocket OrderBook Push Frequency
Dear Traders,
We are pleased to announce upcoming enhancements to our OrderBook data services.
Effective Date: November 25, 2025
The WebSocket OrderBook (1,000 depth levels) push frequency for Futures and Spot markets will be adjusted from 300 milliseconds to 200 milliseconds.
For more details, please refer to the api official documentation:
https://bybit-exchange.github.io/docs/v5/websocket/public/orderbook
Please review the documentation and make the necessary adjustments to ensure a smooth transition.
Thank you for your continued support.
The Bybit Team
