GDAX is a cryptocurrency trading platform and it is a subsidy owned by Coinbase. They offer a great platform along with a suite of API services for easy access to the trading data – rear mirror historical view or real-time data.
I have used API before but GDAX suggests to use websocket instead of API for real-time data access.
API – LEVEL1
“Only the best bid and ask”
As you can see, on the trading platform, the best selling price (ask to sell) is 10077.92 USD/BTC and at the same time, the best buying price (bid to buy) is 10077.91 USD/BTC. There are 53 different orders bidding at the best bid price and the total bids size is 35.26 BTCs. Same for the asks.
API – LEVEL2
“Top 50 bids and asks (aggregated)”
At level2, instead of the top 1 (best) bid and ask orders, the API will return the top 50 bids and the top 50 asks. The data is in the same format [price, ordersize, numberOfOrders]. Given this information, you will have enough information to plot the depth chart (investopedia explanation).
However, the price range is so small (10112.14 – 10076.77) / 10076.77 ~ 0.3% only a small small price range, which is not sufficient enough to draw a meaning depth chart.
API – LEVEL3
“Full order book (non aggregated)”
This is a BIG request, however, the information is quite rich and it a complete snapshot of the orderbook. Hence, the response format is slightly different where they do not have order size anymore because record is at order level without any aggregation, instead, they provided the order ID.
As shown in a snippet of the response, they even listed the bids out there at the price of 0.01 USD/BTC. Those bids are probably the ones either added to the orderbook years ago or those were the disbelievers. On the other size of the spectrum, you can easily see people even ask to sell BTC at the price of 9,999,999,999 USD/BTC, good luck to them 🙂
This is a plot of the histogram of how orders are distributed on different prices. As you can see, there are a few peak values out there. The biggest peak is definitely on the lowest point, maybe under a dollar. Then they have a few big peaks around $800, $5000, $8000 and $10000.
This is interesting but not necessary the depth chart that you usually see.
For example, this is the market depth from GDAX. And clearly, the X axis is still exchange rate of BTC and USD but the y axis is the number of Bitcoins at that price. I am not exactly sure of the resolution in this graph but let’s take a quick look and see if we can reproduce this graph in Matplotlib.
The code might not be the most efficient but it does but you want it to do.
If you are on GDAX website, you can realize that your computer’s fan might be spinning a bit faster, behind the scene of numbers jumping up and down, you can the browser actually subscribed to the GDAX websocket to stream NRT trading information from their server to update the information on your website. And this actually the exact websocket that the developer manual suggest users to use to receive information feed.
Of course, in this case, you will need to take the responsibility of parsing the information calculate the latest state and deal with everything yourself.
So far, you should have a rough understanding of what kind information are provided various levels of orderbook API from GDAX. We also briefly touched the GDAX websocket. In the next article, I am going to have a deep dive into the websocket data types and message format, hopefully, we can cover Mongodb in more detail regarding how to query the transaction information and gain analytics.
8 thoughts on “GDAX – orderbook data API level1,2,3”
Really interesting article about the GDAX api and use for different levels of orderbooks. When are you planning on releasing the next article on websocket data and Mongobd?
Thanks for the comment, I have already done something but never got a chance to put that into an article. Your comment made me realized people are waiting, I will do that this weekend 🙂
Great article. I’ve been playing around with your code. In your second to last graphic… where you use “lambda” the graphic is cut off. In this graphic “https://datafireball.files.wordpress.com/2017/11/screen-shot-2017-11-28-at-10-42-59-pm.png?w=690” I am wondering what the rest of those two lines say where you sum the res_ask and res_bid??? Sorry, but I’m a bit of hack. I should probably be able to figure it out.
I’d also like to know what is cut off there in that graphic please. I am learning Python as well and this is a fun little project to learn, but I don’t know enough yet to know what should be there after the =.
I am still waiting for the websocket article as well. Please post if you have time.
Hi there, tanks for the article. Quick question, is it possible to poll for JUST the trades history? I only want the trades that are filled, but price and quantity are not returned! It seems that the only way would be to keep a list of all open orders and try to match the order IDs.. but that’s like really inefficient!
Thank you !
Hello, I appreciate the callout of my GDAX Library, but would you mind editing my name to spell, “Daniel Paquin”. Feel free to delete this comment after the edit, thank you!
Hi Dan, sorry for the typo and I corrected the spelling. BTW, thanks for the awesome work.