AymarData
PolymarketHistory from 2025-06-01sol-updown-15m

Polymarket SOL Up/Down 15m historical order book & trade data

6.49M order-book and trade events for SOL 15-minute Up/Down markets since 2025-06-01 — about 12,684 events a day across 96 windows.

Coverage

SOL Up/Down 15m 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

6,494,004

≈ 6.49M as of 2026-10-25

Avg events / day

12,684

book snapshot · book delta · trade · resolution

Update frequency

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

Daily activity · last 30 days

SOL Up/Down 15m events/day: 30-day series, average 12,684 events/day, low 9,142, high 31,011.
low 9,142avg 12,684high 31,011

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 SOL Up/Down 15m?

SOL 15m pairs a fast-moving underlying with moderate liquidity, so the Up price often overshoots and then mean-reverts within the same window — a pattern that only tick-level data can show. Each 15-minute window opens on a quarter-hour boundary as a new Up/Down market, so there are 96 distinct markets per day, and each one resolves against the spot price at the window's start.

Solana is the volatile one of the family. SOL's price follows on-chain activity — memecoin launches, launchpad volume, validator-client news — and it frequently moves in bursts rather than smoothly. Over a 15-minute horizon that means more windows that look decided early and then reverse, and a book whose resting liquidity retreats quickly when volatility rises.

Fifteen minutes is long enough for a model to act on a signal and short enough that a day gives you ninety-six independent samples. It is the interval most research notebooks start with: enough windows for statistical power in a week of data, and enough time inside each window to study how the Up price drifts when spot trends.

What moves SOL 15m Up/Down

  • Network incidents and validator-client upgrades
  • ETF filings and treasury-company buying that arrive as scheduled headlines
  • Window structure: quarter-hour boundaries, where fresh liquidity is posted and the opening Up price re-anchors near 0.50

Schema

SOL Up/Down 15m 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:11.443Z2026-10-22T14:40:11.482Zsol-updown-15m-1792679400uplast_trade_pricebuy0.43110
2026-10-22T14:40:12.174Z2026-10-22T14:40:12.204Zsol-updown-15m-1792679400downprice_changeask0.581343
2026-10-22T14:40:12.322Z2026-10-22T14:40:12.360Zsol-updown-15m-1792679400uplast_trade_pricesell0.4257

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

Code

Pull SOL Up/Down 15m in Python, cURL or MCP

Market id: sol-updown-15m. 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"}

# SOL Up/Down 15m: every trade in one 15-minute window
trades = requests.get(
    f"{API}/trades",
    headers=H,
    params={
        "source": "polymarket",
        "market": "sol-updown-15m",
        "outcome": "up",
        "start": "2026-10-22T14:30:00Z",
        "end": "2026-10-22T14:45: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": "sol-updown-15m",
        "outcome": "up",
        "at": "2026-10-22T14:40:00Z",
        "depth": 10,
    },
    timeout=30,
).json()
print(book.get("spread"), len(trades))

FAQ

SOL Up/Down 15m: common questions

What is the market id for SOL 15m windows?

The family is sol-updown-15m; each window adds the window-start Unix time, a multiple of 900 seconds, for example sol-updown-15m-1792681200. Query the family with search_markets or /v1/markets to list windows, then pass a window slug to /v1/book or /v1/trades.

How many SOL 15m windows resolve each day?

96. That gives roughly 49,152 resolved windows since 2025-06-01 — enough to run proper out-of-sample tests on Up/Down pricing models.

What moves the SOL 15m Up/Down price most?

Two things dominate. First, network incidents and validator-client upgrades. Second, ETF filings and treasury-company buying that arrive as scheduled headlines. On top of that sits the structural driver of every 15-minute window: quarter-hour boundaries, where fresh liquidity is posted and the opening Up price re-anchors near 0.50. Liquidity here is thinner than BTC and ETH, with visible gaps between price levels in quiet periods.

How does SOL 15m Up/Down compare with the SOLUSDT order book on Binance?

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

How big is the sol-updown-15m dataset?

About 6.49M events recorded since 2025-06-01, or roughly 12,684 events a day across about 49,152 windows. Every event carries both exchange and receive timestamps.

Backtest SOL Up/Down 15m with real tick data

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