Crypto exchange feed (Binance, Bybit)
A crypto exchange feed is the public market-data stream a centralised exchange such as Binance or Bybit publishes for its own pairs: trades, order-book updates and candles, usually without an account or API key. It covers that exchange only, and its trade side and quantity conventions differ from venue to venue.
Senzoukria · Glossary · Updated September 2026
What the public streams contain
Centralised crypto exchanges publish market data openly: a trade stream with price, quantity, timestamp and a maker or taker flag, an order-book stream with depth updates, and candle streams. Because the exchange matches every trade in its pair, the stream is a full record for that venue, which makes footprints and delta readable at face value. It is not a market-wide record: BTC on Binance and BTC on Bybit are two different books.
The conventions are exchange-specific. Binance's trade messages flag whether the buyer was the maker, so the seller is the aggressor when that flag is set; Bybit publishes a side field on its public trade stream. Quantities can be base asset, quote-currency notional or contract counts depending on the market type. Aligning these before comparing charts is part of reading the feed.
- Trades: aggregated or raw, with an aggressor convention to verify.
- Order book: snapshots plus incremental updates, to a stated number of levels per side.
- Candles: OHLCV per interval, useful for history but carrying no bid and ask split.
Limits to keep in view
- Exchange access terms, rate limits and regional availability apply to the public endpoints.
- Historical trades are downloadable from archives; historical depth is a separate recording and cannot be rebuilt from trades.
- A market-data stream implies nothing about order routing; trading requires keys and permissions that analysis does not.
- Missing intervals are unknown observations, never zero volume.
In Senzoukria
The Chart data source offers Binance Spot and Binance USD-M Perp as public feeds with no account, no credentials and no data subscription, and the tour describes crypto as a reading source: trading stays off. On first load the chart imports recent trades, then goes live from the exchange stream; bid × ask is rebuilt from real trades rather than from candles. Bybit contributes order-book history for the heatmap, described on the crypto page as 24 hours to 7 days of the book at 200 levels per side in one-second samples.
The Crypto history and profiles setting extends Binance Spot and Perp history progressively on disk, from one week to six months, with candles and real volume at price; larger chart grains are required to display the longest windows. The same drawings, indicators, scripts and AI copilot as the futures chart apply. The redistribution status of any collected data is not an offer of free data.
Common mistakes
- Merging Binance trades with a Bybit book as if they were one exchange's matched history.
- Comparing delta across exchanges without checking which side each one flags.
- Reading base-asset quantity on one chart against notional on another.
- Expecting a crypto order ticket because the feed is live.
Related
This page in other languages
Frequently asked questions
- Do I need a Binance or Bybit account to see the feed?
- No. Public market data on both exchanges is available without credentials, and Senzoukria connects to it that way. Accounts and API keys are only involved in trading, which the software does not do on crypto.
- Why does Bybit only appear for order-book history?
- The Bybit path in the software is the recorded book, used by the heatmap over a window of one to seven days, while executed trades and the live footprint come from Binance Spot and Perp. Each source is shown for what it covers, and the two exchanges are not merged.