binance-api-node
binance-api-node copied to clipboard
:chart: A complete and heavily tested wrapper with typings for the Binance API.
I have been trying (unsuccessfully) to create a function that would follow this rough format ```js function limitOrderWithSlAndTp(quantity, price, sl, tp) { // Unsure what to put here... } ```...
After putting Api key and secret from https://testnet.binancefuture.com/ I am constantly getting this error "Error: Invalid API-key, IP, or permissions for action.". Anyone can help me with this?
Hi, I'm having the same issue as all the closed reconnecting-websocket problems, and in https://github.com/ViewBlock/binance-api-node/issues/621 it was mentioned to pass options. I investigated and could not find any possible way...
im trying to closed the connection when running some code and activate the connection again but its give me the error "Websocket was closed before the connection was estabilshed" const...
Add endpoints 'Open Interest' and' and 'Open Interest Statistics'
The PR https://github.com/ViewBlock/binance-api-node/pull/586 introduced type definitions for `futuresCancelBatchOrders`. 🚀 Unfortunately, the function is missing a return-type definition which becomes a problem when trying to use it with strictly typed code:...
node_modules/binance-api-node/index.d.ts:666:5 - error TS7010: 'futuresCancelBatchOrders', which lacks return-type annotation, implicitly has an 'any' return type. 666 futuresCancelBatchOrders(options: { ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 667 symbol: string ~~~~~~~~~~~~~~~~~~~~ ... 671 timestamp?: number ~~~~~~~~~~~~~~~~~~~~~~~~ 672 })...
I am working in a TypeScript project using ES Modules (ESM) and noticed that it doesn't work out-of-the-box with the types provided from [binance-api-node/index.d.ts](https://github.com/ViewBlock/binance-api-node/blob/master/index.d.ts). Using the following code: ```ts import...
While i was using this awesome package, I realized that futures streaming listen key typing is missing. I have added them to index.d.ts
Exchange info for Futures API uses different structure then the API for Spot. PR contains new types for ExchangeInfo that reflect the actual state of the API. Source of truth...