[Announcement] Full Release of Manual Coin Borrowing API Endpoints

Dear Traders,

We are pleased to announce that the Manual Coin Borrowing API endpoints will be fully released on October 23, 2025.

For more details, please refer to the API changelog:
👉 https://bybit-exchange.github.io/docs/changelog/v5#2025-10-23

Thank you for your continued support,
The Bybit Team

Important Notice: Discontinuation of the Bybit Classic Account

Since the Bybit Unified Trading Account (UTA) launched in July 2022, it has been continuously improved for better reliability and efficiency, even during times of market volatility. With over 99.9% of our users now on the UTA, the Classic Account will be officially discontinued on Oct 31, 2025. Users with a Classic Account must upgrade to the UTA 2.0 by this date.

Account definitions (https://bybit-exchange.github.io/docs/v5/acct-mode)
1. Classic Account: Settles Spot via the Spot Account and all Derivatives via the Derivatives Account. Upgrade to the UTA 2.0 is required.
2. UTA 1.0: Settles Spot and some Derivatives via the UTA, but uses the Inverse Derivatives Account for Inverse Derivatives. Upgrade to the UTA 2.0 is required.
3. UTA 2.0: Settles Spot and all Derivatives via the UTA. No upgrade required.

Key Points — Effective Nov 3, 2025
• Classic Account: Any open Derivatives positions/orders will be closed or canceled. Accounts will be upgraded to the latest UTA, and all assets in Spot and Derivatives Accounts will be transferred. Bybit Classic Accounts will no longer be available.
• UTA 1.0: Any open Inverse Derivatives positions/orders will be closed or canceled. Accounts will be upgraded to UTA 2.0, with assets transferred.

We encourage all users to upgrade to UTA 2.0 as soon as possible to ensure a smooth transition.

Please reach out if you need any assistance with the upgrade.

[Announcement] Release of the API endpoint for querying withdrawal addresses in the address book

Dear Traders,

We are pleased to announce that we have launched a new endpoint to query the withdrawal addresses in the address book. this function will be released on October 21, 2025.

For more details, please refer to the API changelog:
👉 https://bybit-exchange.github.io/docs/v5/asset/withdraw/withdraw-address

Thank you for your continued support,
The Bybit Team

Optimization to /v5/order/cancel-all Endpoint (https://bybit-exchange.github.io/docs/v5/order/cancel-all)

Dear Traders,

To address high latency issues, we will be optimizing the /v5/order/cancel-all endpoint.

Previously, if multiple open orders existed, the cancel-all endpoint would send individual cancel requests for each order to the matching engine. With this update, cancellations will be processed in batches, with up to 200 orders per batch, improving overall efficiency and performance.

For WebSocket order topic: (https://bybit-exchange.github.io/docs/v5/websocket/private/order)
Before:
WebSocket order messages were pushed one by one per order.

After:
A single WebSocket order message may now contain multiple order updates.

Release Schedule:
Testnet: October 28, 2025
Mainnet: November 4, 2025

Thank you for your continued support and understanding.
The Bybit Team

Update to V5 WebSocket Public Connection ID Format

Dear Traders,

To ensure consistency across all connection types, Bybit will update the V5 Public WebSocket connection ID (connId) format to align with the Private channel.

Details of the Change:
• New Format: "machine_name_encoded"-"base36_encoded_incremental_connection_sequence_number"
Example: cejreassvfrsfvb9v1a0-2m

• Previous Format: UUID

Rollout Plan

Product Type              Nov 6           Nov 11          Nov 13          Nov 18
---------------------------------------------------------------------------------
Options & Futures Spread  Grey Release 1  Grey Release 2  Full Rollout    —
Spot                      Grey Release 1  Grey Release 2  Full Rollout    —
Futures                   —               Grey Release 1  Grey Release 2  Full Rollout

• Both old UUID and new encoded connId formats will be supported during this period until full migration is complete.

Thank you for your continued support and understanding.
The Bybit Team

Title: Update to Spot Market Tickers Data Push Frequency

Dear Traders,

To further enhance system stability during periods of high market volatility, Bybit will be optimizing the Spot market tickers data push frequency.
To improve overall system reliability, the Spot WebSocket tickers data push frequency will be adjusted from Real-time to 50 milliseconds.
Please refer to : https://bybit-exchange.github.io/docs/v5/websocket/public/ticker

Testnet Release: October 31, 2025
Mainnet Release: November 4, 2025

Thank you for your continued support and understanding
Bybit Team

New Endpoint: /v5/account/no-convert-repay

Dear Traders,

1. Bybit will introduce a new endpoint – POST /v5/account/no-convert-repay – which allows users to repay only positive assets (ie, where walletBalance > 0).

This new endpoint is similar to the existing POST /v5/account/repay (https://bybit-exchange.github.io/docs/v5/account/repay) endpoint, but only repays assets in the same currency, avoiding asset conversion or repaying using assets which already have a negative balance.

Request Parameters

Parameter  Required  Type    Description
coin       false     string  Coin name (uppercase only)
amount     false     string  Repay amount. If the coin is not specified, the amount must also be omitted.

Release Schedule
Testnet: October 30, 2025
Mainnet: November 3, 2025

2. These two APIs are changing from being asynchronous to returning synchronously.
POST /v5/account/repay
POST /v5/account/no-convert-repay

We will add "SU" and "FA" enums to the response parameters to reflect this.
Parameter Type Comments
result array Object
> resultStatus string
P: Processing
SU: Success
FA: Failed

Thank you for your continued support
Bybit team

Dear Traders,

We are pleased to announce that Option order will suppot "slippageToleranceType" on November 4th, 2025

For more details, please refer to the API changelog:
👉 https://bybit-exchange.github.io/docs/changelog/v5#2025-11-04

Thank you for your continued support,
The Bybit Team

Dear Traders,

To enhance system performance and stability, we are planning the following update to the OpenAPI endpoint /v5/market/instruments-info (category = option):

🛠 Update Details:
This endpoint will no longer return data for deprecated option symbols with status = Closed.

Only option instruments with the following statuses will be included in the response:
PreLaunch (about to go live)
Trading (currently trading)
Delivering (in the delivery phase)

📈 Background:
We have observed a recent increase in transactions per second (TPS) on this endpoint. As it currently accesses the database in some scenarios, this adjustment is intended to improve performance and stability under high-load conditions going forward.

🗓 Planned Effective Date:
November 7, 2025

Thank you for your continued support.

Best regards,
The Bybit Team

Title: Introduction of "PostOnlyMaxLimitOrderSize" for Spot Trading Rules

Dear Traders,

To enhance trading flexibility and improve transparency for Post-only and Retail Price Improvement (RPI) orders, Bybit is updating Spot Trading Rules with the introduction of a new configuration field: "PostOnlyMaxLimitOrderSize".

Key Updates:
Each trading pair will now have its own defined "PostOnlyMaxLimitOrderSize", replacing the previous a fixed 5x multiplier rule.

Effective Date: November 11, 2025
For more details, please refer to the official announcement : https://announcements.bybit.com/article/introduction-of-postonlymaxlimitordersize-for-spot-trading-rules-bltd5c53bae78fe2a6e/

Thank you for your continued support.

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

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 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

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 OpenAPI Users,

Following our earlier announcement https://t.me/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 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 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 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,

Based on feedbacks from institutional clients, we have made several requirement adjustments to the previously announced changes (Ref: https://t.me/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.

📢 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.

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