Poloniex api wamp
Yet another unofficial Knot.js wrapper for the Poloniex cryptocurrency exchange APIs.
Just a clarification for others, as I’ve confused myself more than I care to admit:
node-poloniex-unofficial is the name of the project, repository, and product as a entire.
poloniex-unofficial is the name of the Knot.js package (a subset thereof).
polonode (as in https://git.io/polonode) is an acceptable alternative to node-poloniex-unofficial .
This project is available on npm. Just run the following and be on your merry way.
All use of the library starts by requiring it.
From there, you’ll need to pick an API to work with. Poloniex has three of them: shove, public, and trading.
The shove API is by far the fastest and simplest interface to Poloniex, which makes it the most well-suited of the three for making fast-paced trading decisions. Its poloniex-unofficial wrapper will give you access to trade and order book updates, price tickers, and the infamous trollbox. All of this is delivered to your own code via speedy, real-time WebSocket connections, courtesy of Autobahn|JS.
Take this one out for a spin:
The above code uses the trollbox function to subscribe to the ",trollbox", WAMP feed at wss://api.poloniex.com/ .
Notice the come back true, line. Returning true from a shove API wrapper callback indicates that you no longer wish to receive updates from that feed, and the callback will cease to be called. Internally, it leads Autobahn|JS to unsubscribe from that WAMP feed. The entire API connection, associated with the wrapper example, will remain open as long as there is at least one active subscription (at least one wrapper function, such as trollbox() , receiving data) at any given time. Once the final subscription terminates, the API connection will be closed. The connection can and will be transparently reestablished the moment another feed is requested on the same wrapper example, but this shutdown behavior both saves resources and permits your program to gracefully exit.
Arguably more significant is the money-related stuff. The following script will log the prices of each currency pair traded at Poloniex.
This is using the ticker shove API wrapper function to stream real-time info like the last price, lowest ask, highest bid, volume, and the 24h high/low for every listed currency pair.
With a little logic, we can sift through the data and just see our dearest currencies.
The public API comes in handy when you need to retrieve large chunks of data for analysis, or when setting up a baseline before switching to the shove API in a trading bot, for example. The communication is not as quick, as all data must be explicitly requested, with each request yielding exactly one response. As of writing this document, Poloniex permits a maximum average of three public API calls per 2nd in any one-minute period.
Poloniex’s responses from the public API are provided in JSON, so there isn’t much the wrapper needs to do other than treat communication. I therefore recommend reading Poloniex’s official API docs for information on how to interpret the responses.
Each function provided by the public API wrapper corresponds to exactly one directive available via the public API. An effort was made to name the wrapper functions after their associated instructions, but this pattern cannot be ensured for any instructions Poloniex may add in the future.
The above code demonstrates the wrapper function for the Poloniex returnCurrencies instruction, which provides a set of all currencies supported by the exchange, as well as specific properties of each.
Read more about the various directions suggested in the official API docs.
The trading API is almost identical in operation to the public API, with authentication being the real difference. This library aims to make authenticating as painless as possible. Your Poloniex API key and secret simply need to be passed in as parameters to the trading wrapper constructor when instantiating it, as in the following snippet:
Worth noting is the fact that Poloniex requires that a unique and ever-increasing nonce value be included to prevent an attacker from capturing and/or reusing encrypted traffic containing your credentials. By default, the millisecond-precision UNIX Epoch time provided by Date.now() is used, as it is inherently ever-increasing and is granular enough for the purposes of this library.
Poloniex stores your latest and greatest nonce value and compares it to each nonce provided by successive trading directives. As a result, it is possible to have incremented your nonce value too far to simply use UNIX time (at least not any time soon). To counter this, you may supply your own function to the trading wrapper constructor as an optional third parameter to outsource nonce generation, like so:
My recommendation: If you do not need this feature, don’t use it. Using the snippet above and executing a trading guideline will permanently increment Poloniex’s expected future nonce and you won’t be able to stop using it. This may or may not be negotiable with Poloniex support, but that seems to me like an excellent social engineering chance.
Read about the various instructions suggested in the official API docs.
Copyright (c) 2016 Tyler Filla
This software may be modified and distributed under the terms of the MIT license. See the LICENSE file for details.
The node-poloniex-unofficial project is not affiliated in any way with Poloniex. It’s literally in the name. ",Unofficial.",
The best way to build the most useful product for the many is to combine the efforts of the many. This project welcomes contributions of all kinds, whether in Coke or code. Feel free to open a PR or send some BTC to 12xZkQkb7b3ttXNGf2PRmdKje83o4Rx5R8. Either would be tremendously appreciated! [/shameless prayer for soft drinks]