Deprecation of V1-V3 REST APIs

[tiagosiebler]

No description provided.

[tiagosiebler]

V5 is the new standard and has been the current version for a while now. Do the old v3 etc endpoints even work anymore? If not, it's time to remove tests + rest clients for any old versions. Also websockets, if those versions don't work anymore. Trim out dead code.

[baoanhng]

I also have the same question.

[tiagosiebler]

@baoanhng Once the old endpoints are fully phased out, we will start removing the old functionality. Bybit's API docs have already phased out all the v3 endpoints, except for the Tax API (we will review whether to have this as a separate feature in the SDK).

For anyone using the SDK with the older endpoints, it's important to transition to V5 as soon as you can. V3 has been deprecated for a while now and an increasing number of endpoints are no longer functional.

[JJ-Cro]

What should we do with this, did we check it?

[tiagosiebler]

@JJ-Cro bybit is gradually turning off all the old (pre-v5) APIs. We need to see if the remaining APIs still work. If not, we can look at removing old endpoints from the SDK that aren't usable anymore. Requires some testing... easy to start with the public ones.

[tiagosiebler]

Deprecation notices added to old REST clients in #387 - old pre-v5 APIs are expected to stop working around the end of this year. Anyone still using the old REST APIs should look to transition to V5 APIs as soon as possible. Some time early 2025 we will remove those old REST clients completely.

[tiagosiebler]

I've received confirmation from bybit that almost all of these are now offline. The one endpoint that still exists, I'll keep in place, but it may stop working at any moment.

All remaining v1-v3 REST API & WebSocket integration for bybit will be removed in the next major release, as part of the upgrades in #398