You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
That’s odd, the balance of that asset is Spot but still returning always null on the Free field…Enviado desde mi iPhoneEl 17 ene 2025, a las 7:39, Jan Korf ***@***.***> escribió:
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.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
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 ""
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")
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
The text was updated successfully, but these errors were encountered: