Kalshi KXETHD: Ether price above/below (daily) — order book & trade data
55.0K book and trade events for Kalshi's ether price above/below (daily) markets, recorded live since 2026-10-01 — about 2,200 events a day.
Coverage
KXETHD ETH Daily data coverage
What is recorded, how often it updates and how much there is.
Recording since
2026-10-01
25 days so far · no backfill
Events recorded
55,000
≈ 55.0K as of 2026-10-25
Avg events / day
2,200
book snapshot · book delta · trade
Update frequency
Order-book snapshots, deltas and trades streamed in real time
Daily activity · last 25 days
Indicative daily event volume, last 25 days to 2026-10-25. Shape modeled from collector stats; mean matches the average events/day above.
About this market
What is KXETHD ETH Daily?
KXETHD is the ether twin of the bitcoin ladder: daily 'ETH above $X?' contracts whose strikes cover the plausible range for the day, with wider percentage spacing because ETH moves more. AymarData has been recording the KXETHD series since 2026-10-01 and holds 55.0K events so far — about 2,200 a day. History is forward-only; we record live and do not backfill Kalshi.
The contract is a binary on ETH's reference price at the daily cut-off. Compared with KXBTCD it trades less volume, so spreads are wider and the book is thinner, but ETH-specific catalysts — upgrades, ETF headlines, DeFi stress — move it independently of BTC.
Use KXETHD to test whether Kalshi prices ETH moves with a lag relative to BTC: the YES price on the ETH ladder often reprices a beat after the BTC ladder when a macro release hits.
What moves KXETHD
- The ETH/BTC ratio, since ETH often follows BTC with a larger amplitude
- ETF flow data and staking headlines that land during US hours
- DeFi liquidation events that push ether through several strikes in minutes
Schema
KXETHD ETH Daily fields and sample rows
The same columns are returned by the API and in Parquet and CSV files.
| Field | Type | Description |
|---|---|---|
| ts_ms | int64 | Exchange event time, Unix milliseconds |
| ticker | string | Full Kalshi market ticker |
| event_type | string | book_snapshot | book_delta | trade |
| side | string | buy / sell on trades; bid / ask on book events |
| yes_bid | number | Best YES bid, 0–1 dollars |
| yes_ask | number | Best YES ask, 0–1 dollars |
| volume | int64 | Contracts traded or resting at the level |
Sample rows
| ts_ms | ticker | event_type | side | yes_bid | yes_ask | volume |
|---|---|---|---|---|---|---|
| 1792940718410 | KXETHD-26OCT2617-T2600 | book_snapshot | bid | 0.7 | 0.73 | 3164 |
| 1792940719455 | KXETHD-26OCT2617-T2650 | trade | buy | 0.52 | 0.55 | 1025 |
| 1792940720206 | KXETHD-26OCT2617-T2700 | book_delta | ask | 0.33 | 0.36 | 928 |
Illustrative rows for the KXETHD series; tickers follow Kalshi's naming and prices are YES quotes in dollars (0–1).
Code
Pull KXETHD ETH Daily in Python, cURL or MCP
Market id: KXETHD-26OCT2617-T2600. Export AYMARDATA_API_KEY from your dashboard, then run the Python requests example.
import os
import requests
API = "https://api.aymardata.com/v1"
KEY = os.environ["AYMARDATA_API_KEY"] # export AYMARDATA_API_KEY=ad_live_…
H = {"Authorization": f"Bearer {KEY}", "User-Agent": "aymardata-docs/1.0"}
# KXETHD: ten minutes of trades and book updates for one contract
trades = requests.get(
f"{API}/trades",
headers=H,
params={
"source": "kalshi",
"market": "KXETHD-26OCT2617-T2600",
"start": "2026-10-25T15:00:00Z",
"end": "2026-10-25T15:10:00Z",
"limit": 500,
},
timeout=30,
).json()["data"]
last = trades[-1]
print(last["ticker"], last["yes_bid"], last["yes_ask"])
book = requests.get(
f"{API}/book",
headers=H,
params={
"source": "kalshi",
"market": "KXETHD-26OCT2617-T2600",
"at": "2026-10-25T15:05:00Z",
"depth": 10,
},
timeout=30,
).json()
print(book.get("spread"), len(trades))FAQ
KXETHD ETH Daily: common questions
How is KXETHD different from KXBTCD in the data?
Same schema, different instrument: strikes are in ETH dollar terms, volumes are smaller, and quoted spreads are wider. Joined on timestamp, the two ladders show how an ETH move leads or lags BTC.
Do I need Binance data to analyse KXETHD?
It helps. Binance ETHUSDT spot gives the reference price at each tick, so you can compute distance-to-strike and see whether Kalshi prices were stale at any moment.
What moves KXETHD prices?
The ETH/BTC ratio, since ETH often follows BTC with a larger amplitude; ETF flow data and staking headlines that land during US hours; and DeFi liquidation events that push ether through several strikes in minutes.
How much KXETHD history is available?
Recording began 2026-10-01 and is forward-only. At the time of this page that is 25 days, 55.0K events and about 2,200 events a day.
How do I query KXETHD data with the API?
Use market=<full ticker> such as KXETHD-26OCT2617-T2600 with source=kalshi on /v1/trades or /v1/book, or ask the MCP server for the series by name. The snippets on this page are ready to run with your API key.
Related
Related markets and next steps
KXBTCD · BTC Daily
Bitcoin price above/below (daily)
KXETHMAX · ETH Max Price
Ether maximum price in a window
INXD · S&P 500 Daily
S&P 500 above/below (daily close)
Polymarket: ETH Up/Down 15m
Prediction-market view of the same asset
Binance USDⓈ-M perps: ETHUSDT perp
Binance perpetual: funding and mark price
Binance spot: ETHUSDT spot
Binance spot order book
Hyperliquid: ETH perp
On-chain perpetual
← All kalshi data
Parent hub for Kalshi
Pricing →
Builder, Pro and Enterprise plans
Backtest KXETHD ETH Daily with real tick data
Get an API key, pull your first window and join it with the other sources in the catalog.