Jun 26, · This repository provides documentation for BTC Markets' API. For more information please refer to the wiki area. Introduction. Authentication. Trading updated 03/15/ Market data updated 7/24/ Account management updated 3/14/ Fund Transfer updated 08/06/ FAQ. WebSocket feed. WebSocket v2. WebSocket v1 - deprecated. Sample Codes. Description. bitmoneylab.de API wrapper to BTCC (formally BTC China) bitcoin exchange. Publisher. btcmarkets. Lightweight node script to watch BTCMarkets prices in your terminal. Accommodates any currency/conversion pairing of your choosing from BTCMarkets, showing BID/ASK prices and an estimated wallet value based on your holdings (optional).
Node js btc-marketsGitHub - BTCMarkets/btcmarkets-node-sdk: bitmoneylab.de SDK for BTC Markets - bitmoneylab.de
Pagination parameters can't be combined with timestamp parameters and default behavior is pagination when no query param is specified. When using timestamp parameters as query string, the maximum number of items that can be retrieved is , and depending on the specified timeWindow this can be different time windows.
The default behavior, when no query parameter is specified, is to return your most recent trades for all orders and markets. When a valid order id is provided then all trades for the order is returned. Mixing orderId and marketId parameters is not supported. Returns an array of historical orders or open orders only.
All query string parametesr are optional so by default and when no query parameter is provided, this API retrieves open orders only for all markets. Cancels a single order.
Use this API to place multiple new orders or cancel existing ones via a single request. Batch operations are only containers for multiple requests, so each individual request is handled separately from the rest of the requests in the batch.
Once all items in the batch are processed then a single response containing orders added and orders cancalled is returned along with an attribute called unprocessedRequests that is an array of any item in the batch thet can't be processed.
Note that you must provide clientOrderId when placing orders in batch. This allows items inside a batch request to be tracked and processed accurately. When cancelling orders, you can either use orderId or clientOrderId within the request. On average report generation takes about 20 seconds so please allow at least 10 seconds and recommended 30 seconds before attempting to get detail of the report after requesting it via the previous API.
Trying too quickly to get detail a newly created report will result in http response. A successful response of this API contains a link that you can use to download the report content. The attribute contentUrl inside the response is a link to download the report content in either json or csv format. Please note that report content files are only available for download for up to 30 minutes after creation time. Sending subscribe message allows you to start receiving events for the specified channels and marketIds.
This event is published when there is any change in the order status, including placement, matching, cancellation, and triggering. Those events are published when deposit or withdraws of funds are requested by a user or approved by the system and result in balance updates. Channel name used is fundChange. Below is an example of error handling using try catch when placing orders. The error codes along with the message can be used to handle specific situations programmatically.
Your project will be rebuilt upon changes. TSDX has a special logger for you convenience. Error messages are pretty printed and formatted for compatibility VS Code's Problems tab. Bundles the package to the dist folder.
Runs the test watcher Jest in an interactive mode. By default, runs tests related to files changed since the last commit. BTC Markets welcomes contributions from anyone and everyone.
Please see our guidelines for contributing. Following is a wallet app that demonstrates the way to use it. ExchangeSharp uses 'symbol' to refer to markets, or pairs of currencies. Please send pull requests if you have made a change that you feel is worthwhile, want a bug fixed or want a new feature. You can also donate to get new features. This free web service exists to provide information on "coins".
Supports all crypto—currencies. StockSharp shortly S — are free set of programs for trading at any markets of the world American, European, Asian, Russian, stocks, futures, options, Bitcoins, forex, etc. You will be able to trade manually or automated trading algorithmic trading robots, conventional or HFT.
Any broker or partner broker benefits. All currency symbols are based on the base type symbols. A TensorForce-based Bitcoin trading bot algo-trader.
Those episodes are tutorial for this project; including an intro to Deep RL, hyperparameter decisions, etc. PolyCash is the ultimate open source betting solution. PolyCash is a colored coins implementation built using blockchain technology and can be used to create betting currencies on top of bitcoin, litecoin or any other blockchain based on the Bitcoin source code. A cryptocurrency is a digital asset designed to work as a medium of exchange using cryptography to secure the transactions and to control the creation of additional units of the currency.
There are many algorithms used in many different crypto—currencies. This document serves to provide a simple map to reference which are for what, as well as provide a nice list of helpful services and utilities for managing coins. Copay is a secure bitcoin wallet platform for both desktop and mobile devices. The Copay app securely stores multiple, distinct bitcoin wallets, allowing both business and privacy-conscious users to keep funds carefully separated.
It makes sharing a wallet simple and secure. Thanks to tehsenaus and petermrg for pointing this out. Basically, load your data into a Pandas dataframe object and be sure to convert the dates to datetime format and include the following lowercase column titles. If you don't have your own data, we've included a useful function for grabbing historical charting data from the Poloniex exchange. To demonstrate the versatility of our data grabber, we will ignore the last 30 days of data in our backtest and look at the 60 days before then.