Bitstamp
Bitstamp historical market data details - currency pairs, data coverage and data collection specifics
Exchange status: not available for individual order
Bitstamp historical data for all it's currency pairs is available since 2019-03-30.
https://api.tardis.dev/v1/exchanges/bitstamp
api.tardis.dev
See Bitstamp historical data coverage: available symbols, channels, date ranges and incidents

Downloadable CSV files

Historical CSV datasets for the first day of each month are available to download without API key. See downloadable CSV files documentation.
data type
symbol
date
trades
BTCUSD
2019-07-01
incremental_book_L2
BTCUSD
2019-07-01
quotes
BTCUSD
2019-07-01
trades
ETHUSD
2020-03-01
incremental_book_L2
ETHUSD
2020-03-01

API Access and data format

Historical data format is the same as provided by real-time Bitstamp WebSocket v2 with addition of local timestamps. If you'd like to work with normalized data format instead (same format for each exchange) see downloadable CSV files or official client libs that can perform data normalization client-side.
Python
Node.js
cURL & HTTP API
cURL & tardis-machine
1
# pip install tardis-client
2
import asyncio
3
from tardis_client import TardisClient, Channel
4
tardis_client = TardisClient(api_key="YOUR_API_KEY")
5
6
async def replay():
7
# replay method returns Async Generator
8
messages = tardis_client.replay(
9
exchange="bitstamp",
10
from_date="2019-07-01",
11
to_date="2019-07-02",
12
filters=[Channel(name="diff_order_book", symbols=["btcusd"])]
13
)
14
15
# messages as provided by Bitstamp real-time stream
16
async for local_timestamp, message in messages:
17
print(message)
18
19
20
asyncio.run(replay())
Copied!
1
// npm install tardis-dev
2
const { replay } = require('tardis-dev');
3
4
async function run() {
5
try {
6
const messages = replay({
7
exchange: 'bitstamp',
8
from: '2019-07-01',
9
to: '2019-07-02',
10
filters: [{ channel: 'diff_order_book', symbols: ['btcusd'] }],
11
apiKey: 'YOUR_API_KEY'
12
});
13
14
// messages as provided by Bitstamp real-time stream
15
for await (const { localTimestamp, message } of messages) {
16
console.log(localTimestamp, message);
17
}
18
} catch (e) {
19
console.error(e);
20
}
21
}
22
23
run();
Copied!
1
curl -g 'https://api.tardis.dev/v1/data-feeds/bitstamp?from=2019-07-01&filters=[{"channel":"diff_order_book","symbols":["btcusd"]}]&offset=0'
Copied!
https://api.tardis.dev/v1/data-feeds/bitstamp?from=2019-07-01&filters=[{%22channel%22:%22diff_order_book%22,%22symbols%22:[%22btcusd%22]}]&offset=0
api.tardis.dev
Example API response for Bitstamp historical market data request
1
curl -g 'localhost:8000/replay?options={"exchange":"bitstamp","filters":[{"channel":"diff_order_book","symbols":["btcusd"]}],"from":"2019-07-01","to":"2019-07-02"}'
Copied!
Tardis-machine is a locally runnable server that exposes API allowing efficiently requesting historical market data for whole time periods in contrast to HTTP API that provides data only in minute by minute slices.
See tardis-machine docs.

Captured real-time channels

https://www.bitstamp.net/websocket/v2/
www.bitstamp.net
See Bitstamp WebSocket API docs providing documentation for each captured channel's format
Click any channel below to see HTTP API response with historical data recorded for it.
Bitstamp real-time WebSocket API does not provide initial full order book snapshots for live_orders and diff_order_book channels subscriptions. To overcome this issue we fetch initial order book snapshots from REST API and store them together with the rest of the WebSocket messages. Such snapshot messages are marked with "event": "snapshot" and "generated": true fields for respective channels.

Market data collection details

Market data collection infrastructure for Bitstamp is located in GCP europe-west2 region (London, UK). Real-time market data is captured via multiple WebSocket connections.
Bitstamp servers are located in AWS eu-central-1 region (Frankfurt, Germany).
Last modified 10mo ago