biscoint / biscoint-api-node Goto Github PK

The documentation page shows a base parameter on the trades endpoint, but ITradesParams doesn't have it.

The IMetaResult interface doesn't have an offer/confirm attribute as the actual returned object does.

How can one test the api without live real money on the line?

Estou rodando o robô de arbitragem e está dando falha na consulta da API balances:

balances = await bc.balance();
const { BRL, BTC } = balances;
handleMessage(Balances: BRL: ${BRL} - BTC: ${BTC} - ${JSON.stringify(balances)});

Ele acaba imprimindo esse valor zerado para reais, independentemente do valor de BTC

2021-07-20T09:22:43.864Z [Biscoint BOT] [info] - Balances: BRL: 0.00 - BTC: 0.00276863 - {"BRL":"0.00","BTC":"0.00276863"}

Parece que há algum problema no response da API do lado do servidor que não retorna o valor em reais, só em bitcoins.

While playing around with Biscoint's node client, I constantly get this response in the authenticated endpoints:

{ 
  code: 4003,
  error: 'Forbidden',
  details: 'Invalid authorization headers' 
}

I suspect the issue is related to the nonce or the actual request signing.

It's more a question to resolve a question, looking at the documentation I realized that there is no endpoint where I can get a value of a currency passing a date and time as a parameter.

This is not available in the biscoint API, but might this be possible in some other API?

I believe I've looked at more than 10 other services and I don't find this type of query.

Right now it's not possible to config Axios with credentials to a http proxy. That would definitely extend the options one have to deploy trade bots.

Do yous guys have any plans to allow ETH or USDT on the trading methods?

The majority of automatic trade bots use technical indicators like moving averages, oscillators and so on. Without historical price data from Biscoint there's no way to precisely initialize indicators. The only option is to let the program run dry for the number of periods required for the indicator, only to get prices and build the right value. Example: a 20 period EMA watching a 1 day time frame would take 20 days to get properly initialized.

A good historical price endpoint would receive the base coin, the op, the time frame and the number of registries to return. This idea is common place in the MetaTrader world, where the broker provides sets of past data.

I'm constantly getting divergence on the ETH amount after buy operations. The amount returned by confirmOffer doesn't match the value shown by the app. This behaviour has not been seen on BTC operations yet, suggesting that the new ETH features might be flawed.