LogoLogo
  • Kaiko Knowledge Hub
  • General
    • 👋Introduction
    • 🏎️Getting Started
      • API input
      • API output
        • "taker_side_sell" Explained
        • Market open and close
        • Timestamp
      • Authentication
      • Data versioning
      • Envelope
      • Error codes
      • Pagination
      • Rate limiting
  • Data Feeds
    • Introduction
    • Level 1 & Level 2 Data
      • Level 1 Aggregations
        • Trade Count, OHLCV, & VWAP
          • OHLCV only
          • VWAP only
      • Level 1 Tick-Level
        • All trades
        • Derivative liquidation events
        • Borrows, repayments, liquidations, and withdrawals
      • Level 2 Aggregations
        • Market depth (snapshot)
        • Market depth (aggregation)
        • Price slippage (snapshot)
        • Price slippage (aggregation)
        • Bid-ask spread (aggregation)
        • Tokens in a liquidity pool
          • Tokens in a liquidity pool (Uniswap v3)
        • Interest rates, borrowed and deposited amounts
        • Raw order book snapshot
          • Raw order book snapshot + market depth, bid/ask spread & price slippage
      • Level 2 Tick-Level
        • Mints and burns
    • Reference Data
      • Free tier
        • Asset codes
        • Exchange codes
        • Exchange trading pair codes (instruments)
        • Lending protocol codes
        • Blockchain codes
      • Advanced tier
        • Derivatives contract details
        • Derivatives price details
      • Premium tier
        • Market capitalization and circulating supply (BETA)
  • ANALYTICS Solutions
    • Introduction
    • Kaiko Fair Market Value
      • Kaiko Fair Market Value (Direct prices for high liquidity pairs)
      • Kaiko Fair Market Value (Synthetic prices for low liquidity pairs)
        • Convert with Oanda FX Rates
    • Kaiko Derivatives Risk Indicators
      • Exchange-provided metrics
      • Token-level liquidation volumes
      • Implied volatility calculation - smile
      • Implied volatility calculation - surface
    • Kaiko Portfolio Risk & Performance
      • Value at risk calculation
      • Custom valuation
  • Monitoring Solutions
    • Kaiko Market Explorer
      • Assets
      • Exchanges
    • Kaiko Blockchain Monitoring
      • Ethereum Wallets
        • Balances and transactions
      • Bitcoin Wallets
        • Balances
        • Transaction
      • Solana Wallets
        • Balances and transactions
      • Provenance Wallets
        • Balances and transactions
  • Misc & Legacy endpoints
    • CME
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. General
  2. Getting Started
  3. API output

"taker_side_sell" Explained

For Centralized Exchange(CEX) taker_side_sell takes the value of true when a taker's sell order fills a maker's buy order and false when a taker's buy order fills a maker's sell order.

For Decentralized Exchanges (DEX) using Automatic Market Maker (AMM) protocols, the liquidity pool contract is considered the maker. The entity executing a transaction against the liquidity pool is the taker.

If an exchange does not appear below, it can be assumed that all data we provide is normalized correctly.

For exchanges where we were unable to confirm as reporting data from either a taker or a maker's perspective, we have included the notation mapping from the exchange's trade direction field to our taker_side_sell field. This is necessary so that researchers who want to further study trade direction can make their own conclusions. For exchanges that classify trade direction differently or exclude the field entirely, we also include the notation mapping and a short explanation for how their variable differs.

Furthermore, there are some trades of the Australian Exchange Independent Reserve, where we cannot decide if it is the taker buy or taker sell. As such, it is the only exchange that has 3 values, which are true, false and unknown, in the field taker_side_sell.

Finally, we have made a couple of errors in classifying exchanges as "maker" or "taker", typically early on in the process of developing taker_side_sell. Rather than switch our trade reporting after years of data collection, we have simply marked exchanges where the inverse of the notation stated should be applied. For these exchanges, researchers should be aware that when taker_side_sell: false, the inverse should be assumed.

Unconfirmed, Misclassified or Absent Trade Direction Field

Exchange

Exchange Notation

Kaiko taker_side_sell: true equivalent to:

Comment

BTCBox

"type": "buy" or "sell"

inverse notation: "type": "sell"

Inverse, but confirmed perspective from exchange.

Liquid (Quoine)

taker_side: "buy" or "sell"

inverse notation: taker_side: "buy"

Inverse, but confirmed perspective from exchange.

Bithumb

"type": "bid" or "ask"

inverse notation: "type": "bid"

Inverse, but confirmed perspective from exchange.

Coinone

"is_ask": "0"(if seller is taker)/"1"(if seller is maker)

inverse notation: "is_ask": "1"

Inverse, confirmed from exchange but slightly different notation format

Bitstamp

type: 0 (buy) or 1 (sell)

type: 1

Unconfirmed perspective from exchange

Bit-Z

"s": "buy" or "sell"

"s": "sell"

Unconfirmed perspective from exchange

EXX

type": "buy" or "sell"

type: "sell"

Unconfirmed perspective from exchange

CEX.io

type: "buy" or "sell"

type: "sell"

Unconfirmed perspective from exchange

Yobit

"type": "bid" or "ask"

"type": "bid"

Unconfirmed perspective from exchange

itBit

None

Always returns true

No buy/sell field

Korbit

None

Always returns null

No buy/sell field

Coinflex

None

Always returns null

No buy/sell field

Independent Reserve

"Side": "Buy" or "Sell"

"Side": "Sell"

Some trades have "Unknown"

AsiaNext

None

Always returns false

No buy/sell field provided

PreviousAPI outputNextMarket open and close

Last updated 5 months ago

Was this helpful?

🏎️