Changelog 2024-04-23
Websocket API
Websocket Trade Guideline [UPDATE]
- Request parameter of "Create/Amend/Cancel" is changed from headers to header
Dear trader,
With the increasing volume of transfer records, Bybit will make the change for Get Transfer Records related endpoints.
Before the change:
There is no time restriction when query transfer records.
After the change:
Without startTime and endTime, it returns the past 30 days data by default.
For example, GET /v5/asset/transfer/query-inter-transfer-list?coin=USDT
In particular, there is no time restriction when query transferId only
For example, GET /v5/asset/transfer/query-inter-transfer-list?transferId=c7e2c844-34fc
Affected APIs:
V5 - Get Internal Transfer Records
V5 - Get Universal Transfer Records
V3 - Get Internal Transfer List
V3 - Get Universal Transfer List
The implementation time will be started from 2AM UTC, 15 April
Dear trader (Classic account Spot Trading):
Regarding this announcement: /channel/Bybit_API_Announcements/230, in addition to the original changes, there is also a new change:
Before:
You get below error when the orderId or orderLinkId does not exist at all
{"retCode": 170213, "retMsg": "Order does not exist.", "result": {}, "retExtInfo": {},"time":1711386182235}
After:
You will get empty array when the orderId or orderLinkId does not exist at all
{"retCode": 0, "retMsg": "OK","result": {"nextPageCursor": "","category": "spot","list": []},"retExtInfo": {},"time": 1711386553777}
Affected APIs:
V5 Get Open Orders
V5 Get Order History
V5 Get Pre-upgrade Order History
The new implementation date will be started from 11 April, including this change and the original change mentioned in the previous notification.
Dear trader,
There is an ongoing issue for UTA account trading. The backend team is working on it.
We will keep you post when there is an update.
Dear trader,
The launch of Minimum Order Notional Value is delayed. Below is the latest timeline:
Testnet: 28 March
Mainnet:
11 April:
1. USDT perps for classic accounts uid ending with "9"
2. USDT perps, USDC perps & USDC futures for Unified account - nonPro uid ending with "9"
16 April:
1. USDT perps for classic accounts (all uids)
2. USDT perps, USDC perps & USDC futures for Unified account Pro (all uids)
Previous announcement: /channel/Bybit_API_Announcements/220
Changes to Max. Order Size for USDT Perpetual Contracts
To enhance trading experience, Bybit has adjusted the Maximum Order Size of USDT Perpetual Contracts, effective from March 22, 2024.
If necessary, please adjust your trading strategies in accordance with the new Max. Order Size.
https://docs.google.com/spreadsheets/d/1bfC4e9heHqpLV7U4zpsIOGp9anmW7S3tXjWRFuA0YoA/edit?usp=sharing
Dear trader,
As of 15:51 SGT we're pleased to announce that the previous service interruption has been resolved, and everything is back to normal! Our team has successfully addressed the issue, and you can now resume your regular activities without any disruptions.
We apologize for any inconvenience caused during the interruption and appreciate your patience and understanding throughout the resolution process.
Thank you for your cooperation and continued support.
Dear traders,
Bybit are encountering an issue for Unified Trading Account users. All related service are impacted.
The technical team is investigating.
The next communication time is 15:35 SGT
Dear trader,
Bybit will implement a change for V5 - Orderbook Rest API and V3 - Orderbook Rest API
Before the change,
Perps & Futures: support depth 200, and u is corresponding to the u in the wss 200-level orderbook
After the change,
Perps & Futures: support depth 500, and u is corresponding to the u in the wss 500-level orderbook
The implementation time will be started from 2AM UTC, 21 March
Dear trader,
Bybit will implement an urgent delisting of STRAXUSDT Perpetual, which was planned to be delisted on 21 March. The new delisting time is 6AM UTC, 20 March.
https://announcements.bybit.com/en/article/delisting-of-straxusdt-perpetual-contract-bltb8cab042a75047dd/?category=delistings
Dear trader,
Bybit will introduce Minimum Order Notional Value (USD) for perpetual & futures orders. It requires the orders to satisfy this minNotionalValue.
You can refer to field minNotionalValue, which will be added to V5-Get Instruments Info (category=linear,inverse)
and V3-Instrument Info (category=linear,inverse)
If violated, you will receive error: 3100116, Order notional Value below the lower limit {xxx}
This limit will not affect closing position orders.
Release plan:
Testnet: 25 March
Mainnet:
28 March:
1. inverse perps & futures for classic account and Unified account - nonPro & Pro (all uids)
2. USDT perps for classic accounts uid ending with "9"
3. USDT perps, USDC perps & USDC futures for Unified account - nonPro (all uids)
2 Apr:
1. USDT perps for classic accounts (all uids)
2. USDT perps, USDC perps & USDC futures for Unified account Pro (all uids)
Dear trader,
Bybit will introduce Minimum Order Notional Value (USD) for perpetual & futures orders. It requires the orders to satisfy this minNotionalValue.
You can refer to field minNotionalValue, which will be added to V5-Get Instruments Info (category=linear,inverse)
and V3-Instrument Info (category=linear,inverse)
If violated, you will receive error: 3100116, Order notional Value below the lower limit {xxx}
This limit will not affect closing position orders.
Release plan:
Testnet: 25 March
Mainnet:
28 March:
1. inverse perps & futures for classic account and Unified account - nonPro & Pro (all uids)
2. USDT perps for classic accounts uid ending with "9"
3. USDT perps, USDC perps & USDC futures for Unified account - nonPro (all uids)
2 Apr:
1. USDT perps for classic accounts (all uids)
2. USDT perps, USDC perps & USDC futures for Unified account Pro (all uids)
Dear Trader,
Bybit to Support the Ethereum Network Upgrade and Hard Fork.
Starting from 1:25 PM UTC, Mar 13, 2024, Bybit will briefly suspend deposits and withdrawals of all coins via the Ethereum (ETH), Arbitrum(ARB), Optimism (OP), Base Protocol (BASE), ZKFair(ZKF), Linea, Manta Network (MANTA), zkSync Lite, zkSync Era, Starknet (STRK), Polygon (MATIC), and Mantle networks due to Bybit's support for Ethereum's network upgrade and hard fork, expected to occur at 1:55 PM UTC on Mar 13, 2024, at epoch 269,568.
All businesses related to the above-mentioned chains will be affected, including but not limited to:
1. On-chain deposits and withdrawals.
2. Settlement of Pre-Market Trading.
3. ETH2.0 will temporarily pause the Mint and Redeem function starting from 12:00 PM UTC. Previously success orders may be delayed shortly.
4. Bybit WEB3, including but not limited to the withdrawal, swap, and staking activities of Web3.
5. NFT
6. Fiat 3rd party payment methods(Like Moonpay, Mercuryo, Banxa).
Bybit will determine the exact duration of the suspension based on the network's speed.
Deposits and withdrawals will resume once the upgraded network is deemed stable and will not be the subject of a further announcement.
To stay informed, users can set alerts in the deposit and withdrawal windows. You will receive alerts once features resume.
If you have any questions regarding the upgrade, please contact our Customer Support or your respective RM.
Dear trader,
Bybit Will Support the Ethereum (ETH) Network Upgrade & Hard Fork
Starting at approximately 2024-03-13 13:25 (UTC), Bybit will suspend the deposits and withdrawals of token(s) on the Ethereum (ETH), Arbitrum (ARB), Optimism (OP), zkSync Era, Base Protocol (BASE), Manta Network (MANTA), Starknet (STRK) and Polygon (MATIC) networks to support the Ethereum network upgrade and hard fork to ensure the best user experience.
The network upgrade and hard fork will take place at epoch 269,568, or approximately at 2024-03-13 13:55 (UTC).
Please note:
- The trading of token(s) on the aforementioned networks will not be impacted.
- Bybit will handle all technical requirements involved for all users.
- Deposits and withdrawals for token(s) on the aforementioned networks will be reopened once the upgraded network is deemed to be stable. No further announcement will be posted.
- There may be discrepancies in the translated version of this original article in English. Please reference this original version for the latest or most accurate information where any discrepancies may arise.
Changelog 2024-03-06
REST API
Batch Place Order
- Support Spot trading (Unified account)
Batch Amend Order
- Support Spot trading (Unified account)
Batch Cancel Order
- Support Spot trading (Unified account)
Dear Trader,
There is a scheduled service upgrade for "Move Position" APIs. You may encounter service unavailable around 15 - 30 seconds.
Affected APIs:
Move Position
Get Move Position History
Error sample:
{"retCode":10016,"retMsg":"Internal System Error.","result":{},"retExtInfo":{},"time":1712645180993}
The implementation time is between 2.30 - 4PM SGT, 16 Apr
Changelog 2024-04-03
Rest API
- Demo trading supports Open API
- Guideline: https://bybit-exchange.github.io/docs/v5/demo
Dear trader,
The Unified Account trading service has been recovered at 17:19 SGT.
We're keeping monitoring the status.
Dear Traders,
Changes to Tick Size for USDT Perpetual Contracts (Apr 3, 2024)
In our ongoing efforts to enhance market liquidity and optimize your trading experience, Bybit will be adjusting the tick size for select USDT Perpetual Contracts on Apr 3, 2024 at 9AM UTC.
https://announcements.bybit.com/en/article/changes-to-tick-size-for-usdt-perpetual-contracts-apr-3-2024--bltec1391049ec6fae7/
Dear trader,
Websocket trading has been released to testnet. Please find the documentation here:
https://bybit-exchange.github.io/docs/v5/websocket/trade/guideline
We'd love to hear your feedback and suggestions.
Dear trader,
Bybit will implement a change of querying Cancelled orders of Classic account Spot Trading.
Before the change:
You can query "Deactivated", fully "Cancelled" orders occurred in the past 180 days
After the change:
You can query "Deactivated", fully "Cancelled" orders occurred in the past 7 days
Affected APIs:
V5 Get Order History
V5 Get Pre-upgrade Order History
V3 Order History
The implementation time is started from 26 March
Dear traders,
Bybit are encountering an issue for Unified Trading Account users. All related service are impacted.
The technical team is investigating.
The current ETA is 30min. Keep you posted once there is new update.
Dear trader,
Bybit will implement an upgrade, which will affect query historical orders API of Classic account (USDT Perpetual).
Affected account:
UID ends in the third-to-last digit with 0, 1, 4, 5, 6, 7
Affected time:
you may get empty response less than 1 minute.
Affected APIs:
V5 - Get Order History
V3 - Get Order List
The implementation time is 6:30AM - 7:30AM UTC, 22 March.
Dear trader,
Here is corrections of this announcement /channel/Bybit_API_Announcements/220
1. inverse perps & inverse futures are not affected, i.e., there is no minimum order notional value requirement
2. error code will be 110094, Order notional Value below the lower limit {xxx}
Sorry for inconvenience.
Dear trader,
To ensure the efficiency of our trading platform, Bybit will be implementing minimum notional value requirements for orders placed on USDT Perpetual, USDC Perpetual, and USDC Futures contracts. This change is scheduled to take effect gradually, starting from Mar 28, 2024.
For more details, you can refer to https://announcements.bybit.com/en/article/introducing-minimum-notional-value-requirement-for-derivatives-trading-blt0aea715040568196/ and previous telegram notification
Dear trader,
To improve the user experience, Bybit will implement the changes for Classic account Spot trading. Please make sure you adapt below changes.
Before the change:
1. Cancelled or Filled orders
call cancel API, you get one of the below responses.
- OK
- Cancelled orders: (v5-"170142", v3-"12142") "Order has been canceled."
- Filled orders: (v5-"170139", v3-"12139") "Order does not exist."
2. Market order
e.g, you input FOK, then it returns FOK in the order detail response. Always the same as input.
3. Cancel-all response
"result": {"success": "1"}
4. orderLinkId length
there is no length limit
5. open orders limit
no upper limit for Limit order; maximum 30 orders for TP/SL order, Stop order, Oco order per symbol
After the change:
1. Cancelled or Filled orders
call cancel API, you will only get (v5-"170213", v3-"12213") "Order does not exist." no matter it is cancelled or filled
2. Market order
e.g, you input FOK, then it returns IOC in the order detail response. Always shows "IOC" for market order.
3. Cancel-all response
"list": [{"orderId": "xxx", "orderLinkId": "xxxx"}], "result": {"success": "1"}
4. orderLinkId length
the length is no more than 64
5. open orders limit
500 orders in total, including a maximum of 30 open TP/SL orders, a maximum of 30 open stop orders, a maximum of 30 open oco orders per symbol
Affected APIs:
V5-Cancel Order, V5-Create Order, V5-Cancel All Orders
V3-Place Order, V3-Cancel Order, V3-Batch Cancel Order
During the upgrade, you are expected to receive error code: v5 - "170138", v3 - "12318", the impact time should be less than 3 seconds.
The implementation time will be started from 2AM UTC, 28 March.
Bybit to Support the Optimism (OP), Arbitrum (ARB), Base Protocol (BASE) and Mantle(MNT) Upgrade and Hard Fork
Bybit will temporarily suspend deposits and withdrawals for the following networks due to Optimism (OP), Arbitrum (ARB), and Base Protocol (BASE) upgrade and hard fork:
- Bybit will suspend the deposits and withdrawals of token(s) on the Arbitrum (ARB) network starting from approximately 2024-03-14 08:00 (UTC).
- Bybit will suspend the deposits and withdrawals of token(s) on the Optimism (OP) network starting from approximately 2024-03-13 23:00 (UTC).
- Bybit will suspend the deposits and withdrawals of token(s) on the Base Protocol (BASE) network starting from approximately 2024-03-13 23:00 (UTC).
- Bybit will suspend the deposits and withdrawals of token(s) on the Mantle(MNT) network starting from approximately 2024-03-15 00:00 (UTC).
During this time, the following services will be affected:
- On-chain deposits and withdrawals.
- Bybit WEB3, including withdrawal, swap, and staking activities.
- Fiat 3rd party payment methods (like Moonpay, Mercuryo, Banxa).
Bybit will determine the exact duration of the suspension based on the network's speed.
Deposits and withdrawals will resume once the upgraded network is deemed stable and will not be the subject of further announcements.
To stay informed, users can set alerts in the deposit and withdrawal windows. You will receive alerts once these features resume.
If you have any questions regarding the upgrade, please contact our Customer Support via this form.
Dear trader,
To align the product plan, Bybit will stop the deposit to USDC Contract wallet for Classic account.
Affected API:
V5-Set Deposit Account
You will receive below error when you set destination wallet as "OPTION"
"retCode":131003,"retMsg":"Not Support Sub Account"
The above change will be implemented from 8AM UTC, 13 March
Dear trader,
Bybit will implement an upgrade, which will affect query historical orders API of Unified account (category=inverse) and Classic account.
Affected account:
uid ending with "8" and "9".
Affected time:
you will get empty response lasting at most 1 minute.
Affected APIs:
V5 - Get Order History
V3 - Get Order List
The implementation time is 3AM - 4AM UTC, 12 March.
Changelog 2024-03-05
REST API
Get Position Info
- Add new response field sessionAvgPrice for USDC contracts
- Add new response field curRealisedPnl for Perps, Futures and Option
- cumRealisedPnl is depreciated for Option, always ""
- Add new response fields delta, vega, theta, gamma for Option
Websocket API
Position
- Add new response field sessionAvgPrice for USDC contracts
- Add new response field curRealisedPnl for Perps, Futures and Option
- cumRealisedPnl is depreciated for Option, always ""
- Add new response fields delta, vega, theta, gamma for Option
