Discussions
Cannot get orderbook depth for some symbols
Hello,
I am trying to get the depth of the orderbook for some trading pairs using the GET request:
https://api.huobi.com/market/depth?symbol=ethbtc&type=step0'
This works well for some pairs, such as ETH-BTC, or LTC-BTC, but I get an error when I try other pairs such as OMG-BTC:
https://api.huobi.com/market/depth?symbol=omgbtc&type=step0'
{'ts': 1557692702065, 'status': 'error', 'err-code': 'invalid-parameter', 'err-msg': 'invalid symbol'}
Could you please help?
Thanks a lot!
Julia
Posted by Julia Scivi almost 5 years ago
how much do you charge for rating
Posted by Bill Lu almost 5 years ago
Get Latest Trades not working
Hi,
I am trying to access your api, specifically GET /market/history/trade Latest Trade Detail, but I am not getting the information I expect. What I expect are the 1000 most recent trades for the pair specified. Instead it does not seem like I can get more than 316 and they do not seem to be the most recent, as I have some that date back 4 days for the pair btcusdt. Please advise.
Best,
Lucas
Posted by Lucas Berry about 5 years ago
Trades stream sends messages very rare
Hello! My server receives data using websockets API. All streams work good, except trades steam (trade.detail). After sending subscribe message Huobi answeres with subscribed ok message and sends some trade messages (usually less than 5). After that my server receives only ping messages. I don't understand what's going on.
Posted by Alexander Subota about 5 years ago
Bad-Argument placing an order
I am able to correctly sign a request and get my account-ids and balances. Using the same signing code, when I try to place an order, I get "err-code":"bad-argument", "err-msg":"Argument is invalid" but I cannot see what argument might be invalid.
Below is my request. Note that account-id, AccessKeyId, and Signature have been obfuscated.
POST https://api.hbus.com/v1/order/orders/place?account-id=xxxxxx&amount=0.1&price=0.010405&source=api&symbol=ltcbtc&type=buy-limit&AccessKeyId=xxxx-xxx-xxxx&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2018-07-26T22%3A03%3A37&Signature=xxxxxxxx
Posted by Mark McCracken almost 6 years ago