carlosmiei/node-binance-api issues and pull requests

#100 - [#33] ensure depth cache message queue exists

Pull Request - State: closed - Opened by bkrypt about 7 years ago

#99 - Bug fix: Pass reconnect parameter to socket handlers

Pull Request - State: closed - Opened by bkrypt about 7 years ago - 1 comment

#98 - Add use of combined WebSocket streams

Pull Request - State: closed - Opened by bkrypt about 7 years ago - 2 comments

#97 - 404 trying to load balances

Issue - State: closed - Opened by LorinWeb about 7 years ago - 4 comments
Labels: responded

#96 - #prices() can retrieve single price ticker

Pull Request - State: closed - Opened by MadDeveloper about 7 years ago - 1 comment

#95 - Unable to specify fromID

Issue - State: closed - Opened by programmrz about 7 years ago - 2 comments
Labels: resolved

#94 - Multiple Instances of Binance?

Issue - State: closed - Opened by springjben about 7 years ago - 2 comments

#93 - Redirect logs from node-binance-api

Pull Request - State: closed - Opened by vaielab about 7 years ago - 4 comments

#92 - Error: connect ETIMEDOUT 54.238.203.159:443

Issue - State: closed - Opened by droidmanspace about 7 years ago - 1 comment

#91 - markeyBuy returning empty response

Issue - State: closed - Opened by samilkorkmaz about 7 years ago - 4 comments

#90 - Redirect logs from node-binance-api

Issue - State: closed - Opened by vaielab about 7 years ago - 1 comment

#89 - Stop loss orders are not supported

Issue - State: closed - Opened by qjflores about 7 years ago - 4 comments

#88 - Cancel all orders on a specific market without orders causes a timeout

Issue - State: closed - Opened by marcovega about 7 years ago - 2 comments

#87 - Sandbox Environment

Issue - State: closed - Opened by shayaanahmed about 7 years ago - 4 comments

#86 - Websocket disconnects (Binance issue, but maybe we can defend against)

Issue - State: closed - Opened by kevflynn about 7 years ago - 8 comments
Labels: bug, resolved

#85 - Recent trades returns Too many parameters

Issue - State: closed - Opened by davidstoneham about 7 years ago - 4 comments

#84 - Multiple Instances?

Issue - State: closed - Opened by springjben about 7 years ago - 1 comment
Labels: in-progress, feature-request

#83 - recentTrades: Too many parameters; expected '2' and received '5'.

Issue - State: closed - Opened by keyle about 7 years ago - 4 comments

#82 - Websockets timing out

Issue - State: closed - Opened by ryanvanbelkum about 7 years ago - 2 comments

#81 - Singleton VS new Object

Issue - State: closed - Opened by usama33 about 7 years ago - 18 comments
Labels: in-progress, feature-request, resolved

#80 - Trades call failing with code -1104

Issue - State: closed - Opened by misterdeveloper about 7 years ago - 5 comments

#79 - Compressed/Aggregate trades list

Issue - State: closed - Opened by freimanas about 7 years ago - 1 comment

#78 - Get coins balances in BTC

Issue - State: closed - Opened by GeorgeMurAlkh about 7 years ago - 3 comments
Labels: feature-request, needs-solution

#77 - Error: unexpected server response (504)

Issue - State: closed - Opened by vaielab about 7 years ago - 22 comments
Labels: feature-request

#76 - WebSocket connection closed!

Issue - State: closed - Opened by vaielab about 7 years ago - 7 comments
Labels: bug, resolved

#75 - Universal websocket client?

Issue - State: closed - Opened by rafaelklaessen about 7 years ago - 8 comments

#74 - Parse Error - RS2 and RS3 must be clear

Issue - State: closed - Opened by maintwitter7 about 7 years ago - 3 comments

#73 - Fixes issue with argument list in advanced parameters

Pull Request - State: closed - Opened by bitoiu about 7 years ago

#72 - "Filter failure: PRICE_FILTER"

Issue - State: closed - Opened by azharuniverse about 7 years ago

#71 - "Filter failure: LOT_SIZE"

Issue - State: closed - Opened by azharuniverse about 7 years ago - 5 comments
Labels: feature-request

#70 - Incorrect Api Error case Not Handled

Issue - State: closed - Opened by azharuniverse about 7 years ago - 2 comments

#69 - Timestamp Problem - Server out of sync

Issue - State: closed - Opened by usama33 about 7 years ago - 12 comments

#68 - Time stamp issues with binance API

Issue - State: closed - Opened by blinkcloud about 7 years ago - 7 comments
Labels: resolved

#67 - adding empty {} to error processed API requested

Pull Request - State: closed - Opened by CollinEstes about 7 years ago - 1 comment

#66 - OSX - 400 on signed requests due to time sync

Issue - State: closed - Opened by CollinEstes about 7 years ago

#65 - Error: Unexpected server response: 504

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 1 comment

#64 - binance.exchangeInfo((data) not working anymore

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 1 comment

#63 - Using promises vs callbacks?

Issue - State: closed - Opened by grofit about 7 years ago - 8 comments
Labels: feature-request

#62 - 0.4.0: TypeError: Cannot read property 'msg' of null

Issue - State: closed - Opened by keyle about 7 years ago - 6 comments

#61 - improved error handling

Pull Request - State: closed - Opened by robaleman about 7 years ago - 4 comments

#60 - RSV2 and RSV3 must be clear

Issue - State: closed - Opened by maintwitter7 about 7 years ago - 2 comments

#59 - Version on NPM is outdated

Issue - State: closed - Opened by adrianmcli about 7 years ago - 6 comments

#58 - TypeError: Cannot read property 'Symbol(Symbol.iterator)' of undefined

Issue - State: closed - Opened by robertbodley about 7 years ago - 4 comments

#57 - throwing whenever the statusCode != 200 causes issues

Issue - State: closed - Opened by keyle about 7 years ago - 4 comments

#56 - depthCache limit question

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 5 comments

#55 - Added optional params to get candlestick data

Pull Request - State: closed - Opened by sethyx about 7 years ago - 1 comment

#54 - Issue with marketBuy method

Issue - State: closed - Opened by matty8444 about 7 years ago - 5 comments
Labels: bug, resolved

#53 - hopefully fixing error handling and updating it to work the "standard…

Pull Request - State: closed - Opened by hems about 7 years ago - 3 comments

#52 - CORS issue

Issue - State: closed - Opened by bishwash-devops about 7 years ago - 2 comments

#51 - Syntax Error in NPM version of the API

Issue - State: closed - Opened by big-diesel about 7 years ago - 1 comment

#50 - failed market buy errors out instead of throwing actual response

Issue - State: closed - Opened by programmrz about 7 years ago - 12 comments
Labels: bug, resolved

#49 - quick syntax error

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 1 comment
Labels: bug, resolved

#48 - Error: ETIMEDOUT

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 9 comments

#47 - Error when attempting a Stop Loss Limit order

Issue - State: closed - Opened by programmrz about 7 years ago - 2 comments

#46 - Support Flags for Market Orders

Pull Request - State: closed - Opened by matthewwoop about 7 years ago - 1 comment

#45 - Propagate errors objects instead of strings

Pull Request - State: closed - Opened by hems about 7 years ago - 2 comments

#44 - messageQueue[symbol] undefined

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 3 comments

#43 - Allow additional parameters to be passed to trades calls

Pull Request - State: closed - Opened by mstijak about 7 years ago - 2 comments

#42 - Additional options for fetching trades

Issue - State: closed - Opened by mstijak about 7 years ago - 6 comments
Labels: feature-request

#41 - disconnect websockets

Issue - State: closed - Opened by thaison316 about 7 years ago - 1 comment

#40 - info on candles

Issue - State: closed - Opened by thaison316 about 7 years ago - 1 comment

#39 - depthData error for new listed pair

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 3 comments

#38 - Use this library directly in the browser?

Issue - State: closed - Opened by webqap about 7 years ago - 15 comments
Labels: feature-request

#37 - Depth cache out of sync

Issue - State: closed - Opened by mstijak about 7 years ago - 5 comments

#36 - calling balance generates this error

Issue - State: closed - Opened by fjafferi about 7 years ago - 4 comments
Labels: question

#35 - unable to run any method

Issue - State: closed - Opened by thaison316 about 7 years ago - 16 comments

#34 - data.balances is not iterable

Issue - State: closed - Opened by matty8444 about 7 years ago - 2 comments

#33 - Problems with Depth Cache

Issue - State: closed - Opened by andrius-t about 7 years ago - 24 comments
Labels: bug, in-progress, feature-request, resolved

#32 - Binance is down

Issue - State: closed - Opened by ghost about 7 years ago - 1 comment

#31 - Detect a server side disconnect and handle it

Issue - State: closed - Opened by amlwwalker about 7 years ago - 28 comments
Labels: feature-request, resolved

#30 - Catch errors during JSON.parse

Pull Request - State: closed - Opened by sethyx about 7 years ago - 2 comments

#29 - Stop Loss Order Not Working

Issue - State: closed - Opened by yongyi520 about 7 years ago - 9 comments
Labels: resolved

#28 - Depth cache doesn't update increases in price properly

Issue - State: closed - Opened by tsujp about 7 years ago - 2 comments

#27 - CORS issue on request

Issue - State: closed - Opened by Mithgroth about 7 years ago - 1 comment

#26 - Document the entire websocket data objects

Issue - State: closed - Opened by tonytamps about 7 years ago - 2 comments

#25 - How to reconnect for listening websocket

Issue - State: closed - Opened by denisenkoaj about 7 years ago - 2 comments

#24 - weird issue with depth

Issue - State: closed - Opened by bitcoinvsalts about 7 years ago - 11 comments

#23 - LOT_SIZE error

Issue - State: closed - Opened by 0awful about 7 years ago - 3 comments
Labels: responded

#22 - Converting depth object to array gives garbled orders

Issue - State: closed - Opened by tsujp about 7 years ago - 4 comments
Labels: responded

#21 - There hasn't a network error handler

Issue - State: closed - Opened by Xaber20110202 about 7 years ago - 4 comments
Labels: in-progress, feature-request

#20 - How do I check response codes?

Issue - State: closed - Opened by mishterk about 7 years ago - 1 comment
Labels: in-progress, feature-request, responded

#19 - Issue when getting restful depth (order book)

Issue - State: closed - Opened by amlwwalker about 7 years ago - 2 comments
Labels: resolved

#18 - Parameter on depth call should be limit and not depth

Issue - State: closed - Opened by hunterbmartin about 7 years ago - 1 comment

#17 - enabled tracking of all open orders instead of requiring symbol parameter

Pull Request - State: closed - Opened by pouriaa about 7 years ago - 1 comment

#16 - callback not callbac

Issue - State: closed - Opened by fmacko about 7 years ago - 1 comment

#15 - Documentation cleanup

Issue - State: closed - Opened by demipixel about 7 years ago - 1 comment

#14 - Better way to get the current price / volume for each coin?

Issue - State: closed - Opened by napindc about 7 years ago - 4 comments
Labels: in-progress, feature-request, responded

#13 - how to close websocket instance

Issue - State: closed - Opened by includeleec about 7 years ago - 1 comment
Labels: feature-request, responded

#12 - publicRequest error: Error: connect ETIMEDOUT 54.238.203.159:443

Issue - State: closed - Opened by includeleec about 7 years ago - 3 comments
Labels: in-progress, responded

#11 - Update from original

Pull Request - State: closed - Opened by jaggedsoft over 7 years ago

#10 - Update from original

Pull Request - State: closed - Opened by jaggedsoft over 7 years ago

#9 - Websocket Reconnection/Heartbeat

Issue - State: closed - Opened by tsujp over 7 years ago - 4 comments
Labels: in-progress, feature-request, responded

#8 - binance.depth error

Issue - State: closed - Opened by malas over 7 years ago - 3 comments
Labels: responded

#7 - Use Array instead of Object for DepthCache

Issue - State: closed - Opened by tsujp over 7 years ago - 2 comments
Labels: responded

#6 - Easier market orders, better documentation

Pull Request - State: closed - Opened by jaggedsoft over 7 years ago

#5 - Easier market orders, better documentation

Pull Request - State: closed - Opened by jaggedsoft over 7 years ago

#4 - Need a callback function for the buy API

Issue - State: closed - Opened by rj-fc over 7 years ago - 2 comments
Labels: responded

#3 - Timestamp for this request is not valid for openOrders

Issue - State: closed - Opened by rj-fc over 7 years ago - 11 comments
Labels: responded

#2 - market orders aren't working

Issue - State: closed - Opened by tapesclub over 7 years ago - 5 comments
Labels: responded

#1 - missing npm packages - ws and request for your examples

Issue - State: closed - Opened by developerwok over 7 years ago - 2 comments
Labels: responded

GitHub / carlosmiei/node-binance-api issues and pull requests