Implement upcoming V5 TPSL changes

Question

Implement upcoming V5 TPSL changes

tiagosiebler opened this issue a year ago · comments

To further optimize users' trading experience, Bybit will upgrade the Take Profit/Stop Loss (TP/SL) feature of openAPI for USDT Perpetual, Inverse and USDC Contracts. This upgrade will be implemented on May 23 2023, 3AM UTC.

For details, please refer to https://announcements.bybit.com/en-US/article/derivatives-upgrade-of-take-profit-stop-loss-feature-blt741d9e5777be1c7e/ (already effective on WEB and APP). One thing has to be attention that openAPI does not support setting the trigger price of TP/SL orders by ROI or P&L.

The feature has been already available on testnet, feel free to have a try. https://bybit-exchange.github.io/docs/pilot-feature#new-tpsl

Below are openAPI changes:

Place order: /v5/order/create, /contract/v3/private/order/create
add request params: tpslMode, tpLimitPrice, slLimitPrice, tpOrderType, slOrderType
Get open order: /v5/order/realtime, /contract/v3/private/order/unfilled-orders
add response params: tpslMode, tpLimitPrice, slLimitPrice
Get order history: /v5/order/history, /contract/v3/private/order/list
add response params: tpslMode, tpLimitPrice, slLimitPrice
Amend order: /v5/order/amend, /contract/v3/private/order/replace
add request params: tpLimitPrice, slLimitPrice
Get position info: /v5/position/list, /contract/v3/private/position/list
tpslMode depreciated, always return 'Full' for Perpetual and Futures
Set trading stop: /v5/position/trading-stop, /contract/v3/private/position/trading-stop
add request params: tpslMode, tpLimitPrice, slLimitPrice, tpOrderType, slOrderType
Websocket - Order stream (v5 / Contract v3):
add response params: tpslMode, tpLimitPrice, slLimitPrice
Websocket - Position stream (v5 / Contract v3)
tpslMode depreciated, always return 'Full' for Perpetual and Futures

Haffel · Answer 1 · Thu May 25 2023 05:17:08 GMT+0800 (China Standard Time)

Are there already plans on when this feature will be implemented in your API? Or is it already and I just missed it?

Joao Cunha · Answer 2 · Tue Jun 06 2023 02:13:33 GMT+0800 (China Standard Time)

@tiagosiebler

Can you try to add this endpoint, it gives the default trade setup for each coin.

https://api2-2-testnet.bybit.com/contract/v5/position/base-info?_sp_category=fbu&_sp_business=usdt

Tiago · Answer 3 · Wed Jun 07 2023 17:23:39 GMT+0800 (China Standard Time)

I'm checking all of this today and will add anything that's missing @Haffelchen @brlocky

Tiago · Answer 4 · Fri Jun 09 2023 22:09:28 GMT+0800 (China Standard Time)

Hey @brlocky - is that endpoint in the API docs? I don't see it anywhere

Tiago · Answer 5 · Fri Jun 09 2023 22:26:25 GMT+0800 (China Standard Time)

Are there already plans on when this feature will be implemented in your API? Or is it already and I just missed it?

@Haffelchen Hello, the next release will include these changes (via #267 - still WIP and checking things).

Haffel · Answer 6 · Sat Jun 10 2023 03:26:32 GMT+0800 (China Standard Time)

Are there already plans on when this feature will be implemented in your API? Or is it already and I just missed it?

@Haffelchen Hello, the next release will include these changes (via #267 - still WIP and checking things).

Sounds good, thanks :)
In the meantime I was able to already use the new parameters by just passing them anyways :D

Joao Cunha · Answer 7 · Mon Jun 12 2023 08:19:38 GMT+0800 (China Standard Time)

Hey @brlocky - is that endpoint in the API docs? I don't see it anywhere

Hi @tiagosiebler, Its not on the API docs, i found it when debug ByBit requests. Would be useful to avoid 1 request each time the symbol changes.

Tiago · Answer 8 · Tue Jun 13 2023 18:59:59 GMT+0800 (China Standard Time)

Hey @brlocky - is that endpoint in the API docs? I don't see it anywhere

Hi @tiagosiebler, Its not on the API docs, i found it when debug ByBit requests. Would be useful to avoid 1 request each time the symbol changes.

I see - do you have a list of params and values that it accepts? You could try using getPrivate(url, objectWithParams) on the rest client (e.g. RestClientV5) to try a raw request against it. If it's not documented, it might be that the signature auth mechanism doesn't work there.

If it does work there, I don't mind adding undocumented apis to the SDK as long as it's clearly warned that the endpoint is undocumented and may stop working at any time.

Joao Cunha · Answer 9 · Tue Jun 13 2023 21:14:40 GMT+0800 (China Standard Time)

Hey @brlocky - is that endpoint in the API docs? I don't see it anywhere

Hi @tiagosiebler, Its not on the API docs, i found it when debug ByBit requests. Would be useful to avoid 1 request each time the symbol changes.

I see - do you have a list of params and values that it accepts? You could try using getPrivate(url, objectWithParams) on the rest client (e.g. RestClientV5) to try a raw request against it. If it's not documented, it might be that the signature auth mechanism doesn't work there.

If it does work there, I don't mind adding undocumented apis to the SDK as long as it's clearly warned that the endpoint is undocumented and may stop working at any time.

Im skipping it for now once is not documented.