News for hackers. Stuff that matters.

A comment on Coinbase – Exchange API. Parent comment

Re:Coinbase – Exchange API by artursapek on Monday January 26, 2015 @12:45AM (#8945676)
Really? I've found Kraken's pretty hard to work with. They're inconsistent in some ways, like their currency pair names (sometimes "XXBTXZEUR", sometimes "XBTEUR"). Also, they are the only ones I've come across who don't just use plain old integers for ids - they have some weird scheme that has string ids formatted like O6W5EU-VY7YF-CS3XNP.

That said, they're better than say BTC-e and OKCoin :)

[ Parent | on HN ]
Re:Coinbase – Exchange API by clarkmoody on Monday January 26, 2015 @02:48AM (#8945935)
The way Coinbase is doing the streaming WebSocket data looks very good. My frame of reference is Bitstamp and Mt. Gox before that...

Keeping a proper copy of the order book on the client side should be fairly straightforward.

Bitstamp's API makes it impossible to keep the full order book synced. They broadcast the top 20 rows over the socket, but for many situations that's not good enough.

[ Parent | on HN ]
Re:Coinbase – Exchange API by functionCall on Monday January 26, 2015 @08:29AM (#8946866)
Bitstamp has a new websocket channel https://www.bitstamp.net/websocket/ where you can get full order book updates.
[ Parent | on HN ]
Re:Coinbase – Exchange API by clarkmoody on Monday January 26, 2015 @10:15AM (#8947363)
Excellent!

Maybe one day and exchange will create a developer email list where they let people know when the API changes (Bitstamp has had an awful history of breaking the API without warning).

[ Parent | on HN ]
Re:Coinbase – Exchange API by drpancake on Monday January 26, 2015 @06:59AM (#8946553)
Kraken's API is pretty good when compared to the industry average. It's just a little bit whacky.
[ Parent | on HN ]