Skip to main content
The common.perpetuals.kalshi_trades table provides individual trade data from Kalshi perpetual markets. Each row represents a single trade with its market ticker, contract count, price, and taker side. Use this table to analyze trading volume, price discovery, and order flow across Kalshi perps.

​
Table Columns

Data Notes:
  • price is per-contract in US dollars. A contract represents contract_size units of the underlying asset.
  • underlying_price is the per-underlying-asset price (price / contract_size), e.g. a BTC perp price of 6.45 with contract_size 0.0001 is an underlying_price of $64,500.
  • partition_date is the event date of the trade (date of created_time).
Unique Key: trade_id
Column NameData TypeDescription
projectVARCHARProject identifier, always ‘kalshi’.
protocolVARCHARProtocol identifier, always ‘kalshi’.
unique_keyVARCHARUnique identifier for the trade (equal to trade_id).
trade_idVARCHARUnique identifier for the trade.
tickerVARCHARPerp market ticker for this trade.
created_timeTIMESTAMP_NTZ(9)Timestamp when the trade occurred.
num_contractsNUMBER(38,2)Number of contracts traded.
priceFLOATTrade price in US dollars, per contract.
contract_sizeFLOATUnits of the underlying asset represented by one contract.
underlying_priceFLOATPrice of the underlying asset in US dollars (price / contract_size).
taker_sideVARCHARSide taken by the taker.
partition_dateDATEEvent date of the trade (used for partitioning).
ingested_atTIMESTAMP_NTZ(9)Timestamp the record was ingested into Allium’s database.

​
Sample Query

select
  trade_id,
  ticker,
  created_time,
  num_contracts,
  price,
  contract_size,
  underlying_price,
  taker_side
from common.perpetuals.kalshi_trades
where partition_date >= current_date - interval '7 days'
order by created_time desc
limit 100