<p>I haven't yet used Bitstamp's streaming API but I think it's fairly safe to assume that you will only get real-time changes via those pusher channels. That means you need to make at least one initial call to their official REST API to get the full orderbook, and then keep it updated by applying the changes that you receive from the streaming API.</p>

<p>If you are really stuck with websockets only (care to explain why?), you may need to build your own proxy middleware that can make that initial REST call and feed your client with the full orderbook via websockets.</p>

<p>Either way, be extra careful about relying on an unofficial and unsupported API which Bitstamp can change at any moment without prior warning.</p>

CC BY-SA 3.0
2014-01-15T02:22:03.910Z
2014-01-15T02:22:03.910Z
ktorn
<p>I've been trying to work with Bitstamp streamline API, which uses Pusher.</p>

<p>So I managed to connect to some channels, specifically to 'orderbook' and it even returned me 6 items. However it looks like some kind of limit. Does anybody know how do I get the full contents of the orderbook (that is, all orders) throught this streamline API? (I know you can do it via regular REST api, but due to some limitation, I really have to use Websockets and Pusher in this case).</p>

<api><bitstamp>
Bitstamp streamline API: how to get all contents of the ordebooks?
orion3
# Bitstamp streamline API: how to get all contents of the ordebooks?

(Asked by: username_0 on 2014-01-14)

I've been trying to work with Bitstamp streamline API, which uses Pusher.

So I managed to connect to some channels, specifically to 'orderbook' and it even returned me 6 items. However it looks like some kind of limit. Does anybody know how do I get the full contents of the orderbook (that is, all orders) throught this streamline API? (I know you can do it via regular REST api, but due to some limitation, I really have to use Websockets and Pusher in this case).

**Tags:** api, bitstamp


---

## 1 answers

### Answer by username_1 on 2014-01-15. Score: 1

I haven't yet used Bitstamp's streaming API but I think it's fairly safe to assume that you will only get real-time changes via those pusher channels. That means you need to make at least one initial call to their official REST API to get the full orderbook, and then keep it updated by applying the changes that you receive from the streaming API.

If you are really stuck with websockets only (care to explain why?), you may need to build your own proxy middleware that can make that initial REST call and feed your client with the full orderbook via websockets.

Either way, be extra careful about relying on an unofficial and unsupported API which Bitstamp can change at any moment without prior warning.


---

