Bybit API Announcements
3.12K subscribers
1 photo
2 files
329 links
Download Telegram
Bybit API Rate Limit Policy (Institutional Version).pdf
118.3 KB
Dear Traders,

Announcement: Upcoming Institutional API Rate Limit Policy
Bybit will introduce a unified rate limit cap of 60,000 transactions per second (TPS) per product line (Futures, Options, Spot). This cap applies independently by business line, allowing institutions to allocate limits flexibly across all UIDs under their structure.

Features:
• Supports tier upgrades and downgrades, with proportional scaling to ensure compliance when limits are exceeded
Backend-assisted configuration during rollout
Custodial structures supported: institutional cap applies across all accounts (parent and sub accounts)


The new policy is expected to launch next quarter. If you have any questions or concerns, please contact your Bybit RM within two weeks.
Dear Traders,
We would like to inform you of an upcoming change to the SPOT order price logic.

Current Behavior (Before the Change):
If a user places a limit order with a price that crosses the opposite side of the order book:
• Buy order price > system calculated maximum limit price for buy orders
The system rejects the order with: "retCode": 170193, "retMsg": "Buy order price cannot be higher than XXXX USDT."
• Sell order price < system calculated minimum limit price for sell orders
The system rejects the order with: "retCode": 170194, "retMsg": "Sell order price cannot be lower than XXXX USDT."

New Behavior (After the Change):
If such orders are submitted:
• Buy order price > system calculated maximum limit price for buy orders, The system will automatically adjust the order price to that maximum limit price
• Sell order price < system calculated minimum limit price for sell orders. The system will automatically adjust the order price to that minimum limit price.
No error will be returned. The order will proceed with the adjusted price.

Deployment Schedule:
• 2025.06.02 — Rollout to Mainnet-Grayscale
• 2025.06.16 — Rollout to Mainnet-Full
Dear users,

To better measure market risks and enhance your trading experience, we're updating the third batch assets of collateral value ratio rules for Unified Trading Account (UTA) Borrowing, effective May 28, 2025, 6AM UTC. This transition, from a single collateral value ratio to a tiered collateral value ratio, will impact the Maintenance Margin Rate (MMR) in your UTA account. Stay informed and monitor your positions accordingly to manage any potential risks.

Please check the details below:
https://announcements.bybit.com/article/update-to-uta-borrowing-collateral-value-ratio-rules-third-batch-implementation-bltec147ec6cb8c554b/
Dear Traders,

Following the previous announcement: https://t.me/Bybit_API_Announcements/317, we have decided to postpone this change after receiving feedback from users. A new rollout schedule will be announced once it is confirmed.

Thank you for your understanding and continued support.
Dear Traders,

Bybit has improved the update frequency for insurance pool balance data.
REST API: The Get Insurance endpoint now provides isolated insurance pool balance updates every 1 minute.
WebSocket API: A new topic has been added. Please refer to the Insurance Pool documentation for details.

We hope these enhancements provide more timely and accurate data for your trading needs.
Dear Traders,

We would like to inform you that a fix will be applied to the Open API – Get Long/Short Ratio endpoint.

Currently, the output data may slightly deviate from the actual values due to an issue in the internal calculation service. After the fix, both real-time and historical data will reflect accurate values.

Effective Date: May 29, 2025

Thank you for your continued support and understanding.
Dear Traders,

📢 Bybit Announcement: Tick Size Updates for Spot Pairs

Bybit will be implementing adjustments to the tick sizes of selected Spot trading pairs effective 10AM UTC on May 29, 2025.

🔍 Key Details:
• Effective Date: May 29, 2025, at 10AM UTC
• Scope: B3TRUSDT, B3TRUSDC, DMAILUSDT, GSTSUSDT, PAWSUSDT, SONUSDT, ZKUSDC, ZKUSDT, NXPCUSDT
• Impact: Existing Spot orders placed before the update will remain unaffected and will be matched using the original tick sizes. API queries for tick sizes will reflect the updated values post-implementation.
https://announcements.bybit.com/article/updates-on-tick-size-for-spot-pairs-ticksizeupdatedate--blt9f3d7c7e953186cb/
📢 Bybit Update: Removal of Minimum Order Quantity Limit for Spot and Margin Pairs

Effective June 17, 2025, Bybit will remove the minimum order quantity requirement for all Spot and Margin trading pairs. Moving forward, only the minimum order value will be enforced at the time of order placement.

🔍 Key Details:
• Effective Date: June 17, 2025
• Scope: All Spot and Margin trading pairs
• Impact: Orders will now be validated solely based on their total value, not quantity.

For more information and recommended actions, please visit: Bybit Announcements
Important Notice: TRBUSDT Contract Migration

Bybit will migrate the TRBUSDT Perpetual Contract to an independent insurance fund pool to enhance risk management and market stability.

Effective Date: June 5, 2025
Key Change:
TRBUSDT will be removed from the shared insurance fund pool.
It will have a dedicated insurance fund going forward.

No changes to trading operations or other pairs. Read full details here
📢 Notice of Error Code Update


Please be informed of an upcoming change on June 17, 2025 (Greyscale testing) and June 24, 2025 (Live) in our spot trading system logic:

We will adjust the order verification logic for spot trading as follows:
The system will only verify the minimum order value, and will no longer verify the minimum order quantity.
As a result, the error code 170136 ("Order quantity lower than the minimum") will be replaced with error code 170140 ("Order value exceeded lower limit").


This means that for all trading scenarios, regardless of change in market price or limit buys and sells, the error code 170136 will be replaced with error code 170140. Please note on this change to avoid any technical issues, thank you for your understanding.
Dear Traders,

We would like to inform you that Bybit will soon be delisting the BTC and ETH Leveraged Tokens. As part of this process, spot trading, subscription, and redemption of these tokens will be gradually discontinued according to the schedule outlined below.

For full details, please refer to the official announcement: https://announcements.bybit.com/en/article/delisting-of-leveraged-token-pairs-blt587f324dcfa69839/?category=delistings

Impact on Open API Services
Following the delisting, the corresponding Open API services will also be terminated on 4 July, 2025. The affected endpoints include:
* Get Leverage Token Info
* Get Leveraged Token Market
* Purchase
* Redeem
* Get Purchase/Redemption Records
* LT Kline
* LT Ticker
* LT Nav
Reminder: UTA Borrowing Limit Adjustments

To meet the consistently high demand for asset borrowing, Bybit has adjusted the borrowing limits for Unified Trading Account (UTA) users. The borrowing limits of select assets under the UTA margin trading framework has been updated.

🔗 Full details can be found here:
https://announcements.bybit.com/en/article/uta-borrowing-adjustments-to-borrowing-limits--blt0ef813f157f2afdd

To ensure a seamless borrowing experience, we recommend users surpassing the new limits to repay in advance by Jun 20, 2025, 6AM UTC. This is to ensure that your risk level stays within acceptable parameters
Dear Traders,

To ensure full hedging for spread trading, we will implement changes to the Spread Trading Spot leg fee currency logic. Please review the details below and prepare accordingly.

REST API Changes
1. Get Spread Trading History
New Field: feeCurrency (applies to Spot leg only)
• New Field:
execFeeV2 – Spot leg trading fee
Deprecation: execFee for Spot leg – will return "0"

2. Get Trade History
New Field: execFeeV2 – applies to transactions with:
createType = "CreateByFutureSpread"
category = "spot"
Note: For such transactions, execFee will return "0"

Websocket API
Spread Execution Stream
New Field: feeCurrency (applies to Spot leg only)
• New Field:
execFeeV2 – Spot leg trading fee
Deprecation: execFee for Spot leg – will return "0"

Production Deployment Timeline
26 June, UID ending in "0"
27 June, UID ending in "1" ~ "3"
30 June, UID ending in "4" ~ "9"

If you have any questions or concerns regarding this change, feel free to reach out to us.
Bybit will be supporting the Zilliqa (ZIL) Network Upgrade & Hard Fork, which is expected to take place on Jun 23, 2025, 00:00AM UTC approximately, or at the block height of 4,770,087.


To ensure a smooth transition,

All borrowing and lending services for ZIL will be suspended, including Borrowing (UTA), Crypto Loans, and Bybit Savings on Jun 21, 2025, 04:00AM UTC.

All deposits and withdrawals via Zilliqa (ZIL) will be temporarily suspended starting from Jun 22, 2025, 11:00PM UTC.

The suspension may take up to 8 days.

https://announcements.bybit.com/article/bybit-to-support-zilliqa-zil-network-upgrade-hard-fork-june-22-2025--blt5b97d2afbc2b81f7/
📣 Delisting of LEVERUSDT Perpetual Contract

Effective Time: Find more details in the announcement center post below
Bybit will be delisting the LEVERUSDT Perpetual Contract at Jul 1, 2025, 9:00AM UTC.

https://announcements.bybit.com/en/article/delisting-of-leverusdt-perpetual-contract-bltb7ebf82b68ebcee1/
📢 Institutional Notice: Major Updates to Margin Calculation (Perps & Futures)

Bybit is updating the margin algorithm for Perpetual & Futures Contracts. Key changes include:
1. Cross Margin
• Position Initial Margin & Maintenance Margin will now use Mark Price instead of Entry Price

2. Isolated Margin
• Maintenance Margin & Liquidation Price is now based on the Mark Price instead of the Entry Price
• Initial Margin remains unchanged
• Algorithm for position liquidation price will be updated but remain at a fixed value. This is consistent with the current experience

3. Portfolio Margin
• No changes

Do note that Risk Limits will dynamically adjust based on real-time Mark Price – clients are encouraged to review exposure accordingly.

Dual Calculation Display
Compare old & new calculations side-by-side before switchover:
• Web rollout: July 8, 2025
• Mobile app submission: July 16, 2025

API endpoints available:
• /v5/position/list, /v5/account/wallet-balance, and push topics (position, wallet) — July 3: Grayscale release. July 8: Full release

Details:
• /v5/account/wallet-balance: Add new response fields: `totalMaintenanceMarginByMp`,`accountMMRateByMp`,`accountIMRateByMp`,`totalInitialMarginByMp`
• /v5/position/list: Add new response fields: `positionIMByMp`,`positionMMByMp`
• "wallet" topic: Add new fields: `accountIMRateByMp`,`accountMMRateByMp`,`totalInitialMarginByMp`,`totalMaintenanceMarginByMp`
• "position" topic: Add new fields: `positionIMByMp`,`positionMMByMp`

New Algorithm Rollout Starts: August 26, 2025
• Complete migration in 2 weeks
• Liquidation may trigger immediately under new logic — clients should prepare & reallocate as needed.
• When the new algorithm takes effect, the risk limit tier may be adjusted immediately based on the real-time mark price, and the margin requirements may be increased accordingly.

More details to come on 8th July.
📣 Update to UTA Borrowing collateral value ratio rules – 3rd batch implementation

Effective Time: Find more details in the announcement center post below

To better measure market risks and enhance your trading experience, we're updating the 3rd batch of collateral value ratio rules for Unified Trading Account (UTA) Borrowing. Effective Jul 11, 2025, 6AM UTC, we'll shift from a single to a tiered collateral value ratio, affecting the Maintenance Margin Rate (MMR) in your UTA account. Stay informed and monitor your positions to manage potential risks.

Learn More!