Unable to get sub-account/list or accountStatus

tpittmannode40 · July 20, 2022, 12:18am

Im unable to get /sapi/v3/sub-account/list or sapi/v3/accountStatus based on binance.us docs example. I am getting Invalid Parameter (-1100) for five different sets of keys I’ve tested, across two different accounts. the same exact code/logic and keys successfully get the /api/v3/myTrades endpoint.

dino · July 20, 2022, 4:50am

can you share what’s the value of this:

echo $api_url/sapi/v3/accountStatus?timestamp=$timestamp

tpittmannode40 · July 20, 2022, 12:20pm

@dino thanks for your help, the result is https://api.binance.us/sapi/v3/accountStatus?timestamp=1658319453000

dino · July 22, 2022, 12:49am

That’s weird, the url looks fine to me.

Do you mind have a try with this python script:

github.com

binance/binance-signature-examples/blob/master/python/spot/spot.py

import hmac
import time
import hashlib
import requests
from urllib.parse import urlencode

""" This is a very simple script working on Binance API

- work with USER_DATA endpoint with no third party dependency
- work with testnet

Provide the API key and secret, and it's ready to go

Because USER_DATA endpoints require signature:
- call `send_signed_request` for USER_DATA endpoints
- call `send_public_request` for public endpoints

```python

python spot.py

This file has been truncated. show original

You will need to change the BASE_URL to .us site:


BASE_URL = "https://api.binance.us"

and test with endpoint, see if it works.

Thanks

tpittmannode40 · July 22, 2022, 12:46pm

Thanks @dino
as expected I get the same response, {'code': -1100, 'msg': 'Illegal characters found in a parameter.'}
with two different sets of keys from two different accounts.
both sets of keys successfully access the /api/v3/account and /api/v3/myTrades endpoints.
it appears there’s some issue with the sapi endpoints.

let me know if I can provide any additional info. Thanks again!