Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Free and AvailableToWithdraw fields comming as null when retrieving Asset Balances #250

Open
andresdrb opened this issue Jan 16, 2025 · 3 comments

Comments

@andresdrb
Copy link

Those fields used to come properly populated before, but recently noticed they come as null (when I know for the retrieved asset I have all its equity free).

For the following call I get, and free and AvailableToWithdraw should have teh same value as walletBalance and equity.

.V5Api.Account.GetBalancesAsync(Bybit.Net.Enums.AccountType.Unified, "LTC")

Image

For the time being I had to workaround by doing walletBalance-Locked to et the actual free asset available, as I don0t know why this started happening

@JKorf
Copy link
Owner

JKorf commented Jan 17, 2025

This is an update on the Bybit side; the availableToWithdraw field is deprecated. Free is only available for Spot balances according to the docs.
A new endpoint was introduced to retrieve the availableToWithdraw value; it's available via V5Api.Account.GetTransferableAsync.

@andresdrb
Copy link
Author

andresdrb commented Jan 17, 2025 via email

@JKorf
Copy link
Owner

JKorf commented Jan 18, 2025

Hm not sure why that would be. This is the only recent change listed for the endpoint:
For accountType=UNIFIED, the response field availableToWithdraw is deprecated, it always returns ""

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants