AymarData
PolymarketHistory from 2025-06-01eth-updown-1h

Polymarket ETH Up/Down 1h historical order book & trade data

9.05M order-book and trade events for ETH hourly Up/Down markets since 2025-06-01 — about 17,668 events a day across 24 windows.

Coverage

ETH Up/Down 1h data coverage

What is recorded, how often it updates and how much there is.

History start

2025-06-01

512 days of history

Events recorded

9,045,900

≈ 9.05M as of 2026-10-25

Avg events / day

17,668

book snapshot · book delta · trade · resolution

Update frequency

Book deltas and trades streamed as they occur; 24 new windows every UTC day

Daily activity · last 30 days

ETH Up/Down 1h events/day: 30-day series, average 17,668 events/day, low 14,605, high 20,143.
low 14,605avg 17,668high 20,143

Indicative daily event volume, last 30 days to 2026-10-25. Shape modeled from collector stats; mean matches the average events/day above.

About this market

What is ETH Up/Down 1h?

ETH hourly windows frequently catch on-chain events — large unstaking queues, DeFi liquidations, ETF-flow prints — that push ether independently of bitcoin for a stretch. Hourly windows open on the hour and resolve an hour later, so there are 24 markets a day. They overlap with scheduled releases and session opens that 5m and 15m windows only sample in part.

Ether usually moves with Bitcoin but with a larger amplitude, so the Up/Down outcome is a bet on beta as much as direction. Over a hourly horizon, ETH also reacts to things BTC ignores: ETH/BTC rotations, staking and ETF-flow headlines, and DeFi liquidations that dump collateral into the market. When BTC is quiet, those ETH-specific catalysts are what flip an Up/Down window.

An hour is long enough to hold a macro print, a cash-equity open or an options expiry inside a single market. That makes hourly windows the cleanest place to measure how a known catalyst is priced before it happens and how fast the book reprices after — you can line up the order book with timestamps of scheduled events.

What moves ETH 1h Up/Down

  • DeFi stress, because ETH collateral gets liquidated when lending markets de-risk
  • The ETH/BTC ratio, which rotates capital between the two majors on risk-on and risk-off days
  • Window structure: scheduled catalysts inside the hour — 8:30 ET economic releases, the US cash open and the 4pm equity close

Schema

ETH Up/Down 1h fields and sample rows

The same columns are returned by the API and in Parquet and CSV files.

FieldTypeDescription
ts_exchangestringExchange timestamp (ISO-8601, ms)
ts_recvstringAymarData receive timestamp
marketstringWindow slug: <family>-<window start unix>
outcomestring"up" or "down" token
event_typestringlast_trade_price | price_change | book
sidestring"buy" | "sell" for trades, "bid" | "ask" for book events
pricenumberProbability price, 0–1
sizenumberShares traded or resting size at the level

Sample rows

ts_exchangets_recvmarketoutcomeevent_typesidepricesize
2026-10-22T14:40:17.991Z2026-10-22T14:40:18.045Zeth-updown-1h-1792677600uplast_trade_pricebuy0.4832
2026-10-22T14:40:18.156Z2026-10-22T14:40:18.207Zeth-updown-1h-1792677600downprice_changeask0.537105
2026-10-22T14:40:18.244Z2026-10-22T14:40:18.277Zeth-updown-1h-1792677600uplast_trade_pricesell0.47180

Illustrative rows for eth-updown-1h. Market is the window slug (eth-updown-1h-<start unix>); prices are probabilities between 0 and 1.

Code

Pull ETH Up/Down 1h in Python, cURL or MCP

Market id: eth-updown-1h. 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"}

# ETH Up/Down 1h: every trade in one hourly window
trades = requests.get(
    f"{API}/trades",
    headers=H,
    params={
        "source": "polymarket",
        "market": "eth-updown-1h",
        "outcome": "up",
        "start": "2026-10-22T14:00:00Z",
        "end": "2026-10-22T15:00:00Z",
        "limit": 500,
    },
    timeout=30,
).json()["data"]
print(len(trades), trades[0]["price"], trades[-1]["price"])

book = requests.get(
    f"{API}/book",
    headers=H,
    params={
        "source": "polymarket",
        "market": "eth-updown-1h",
        "outcome": "up",
        "at": "2026-10-22T14:30:00Z",
        "depth": 10,
    },
    timeout=30,
).json()
print(book.get("spread"), len(trades))

FAQ

ETH Up/Down 1h: common questions

How do ETH 1h markets behave around the 8:30 ET data releases?

The window that contains the print — 12:00–13:00 UTC in summer time, an hour later in winter — shows the biggest book changes. Pull eth-updown-1h deltas with start and end set to ±2 minutes around 12:30 UTC (13:30 UTC once US clocks go back) to see quotes pulled before the release and re-posted afterwards.

How many ETH 1h windows are in the dataset?

24 per day, so about 12,288 since 2025-06-01. Each hourly window is its own market and resolves independently of the 5m, 15m and 4h markets that overlap with it.

What moves the ETH 1h Up/Down price most?

Two things dominate. First, DeFi stress, because ETH collateral gets liquidated when lending markets de-risk. Second, the ETH/BTC ratio, which rotates capital between the two majors on risk-on and risk-off days. On top of that sits the structural driver of every hourly window: scheduled catalysts inside the hour — 8:30 ET economic releases, the US cash open and the 4pm equity close. Liquidity here is second only to BTC, with spreads a tick or two wider and more variance in resting size.

How does ETH 1h Up/Down compare with the ETHUSDT order book on Binance?

Binance is where price discovery happens; Polymarket prices a probability on top of it. Joining eth-updown-1h with Binance ETHUSDT spot and perp ticks on timestamp lets you measure how many milliseconds the Up price lags a spot move. See the Binance ETH spot and perp pages for the matching feeds.

How big is the eth-updown-1h dataset?

About 9.05M events recorded since 2025-06-01, or roughly 17,668 events a day across about 12,288 windows. Every event carries both exchange and receive timestamps.

Backtest ETH Up/Down 1h with real tick data

Get an API key, pull your first window and join it with the other sources in the catalog.