-
Notifications
You must be signed in to change notification settings - Fork 156
api.getAccountBalances AccountNotFoundError (400) #507
Comments
Further inspection of the code shows the axios call as: Trying this directly with Postman and adding in the What is this number meant to be? It defaults to zero if not provided, but even zero just returns a "AccountNotFoundError" / 400. |
Hello, I also encountered the same problem, have you solved it? How was it resolved? |
@wzzYtu I got around it by not using the solo SDK and calling the API directly: |
Is it convenient to show the relevant code? |
This method is available on the mainnet. How should I obtain the mainnet of the fork? |
Here's the approximate code I used to get the account without going through the solo SDK:
|
ok, thanks |
Solo api.getAccountBalances facade to the API does not work, always returns 400.
Using the example account from the documentation, the following works and returns an empty account:
Using solo, for example:
Always fails with
I have tried using
accountNumber: new BigNumber("0")
which also fails, have also tried using my own account which does have some balances, and also returns a full JSON response simply hitting the API directly.The text was updated successfully, but these errors were encountered: