New realtime endpoint: Ohio (AWS us-east-2, next to Kalshi) — Binance from Tokyo at ~65.0 ms one-way to your clientNew endpoint: Ohio · ~65.0 ms one-way

Configure
Low-Latency Trading Solutions
CART
Kalshi · Culture · event · KXTAYLORSWIFTWEDDING

Kalshi TAYLOR SWIFT WEDDING Historical Data

Every Kalshi “TAYLOR SWIFT WEDDING” contract of the day — every trade print and the complete Level-2 book, captured co-located with nanosecond venue and receive timestamps. 124 trading days as day bundles, €1 per day, bought as a guest with instant download.

Trading days
124
Coverage
March 2026 – July 2026
Archive size
209 MB
Price per day
€1
Activity & identifier

TAYLOR SWIFT WEDDING on Kalshi — activity

Per-day trade and turnover statistics exist from July 2026 onward — a limit of the statistics, not of the capture: older days are archived in full (every contract, every message) without a statistics row.

Series ticker
KXTAYLORSWIFTWEDDING
Files on latest day
17
Typical files / day
17
What's in a bundle

One purchase, the whole series for a day

A series-day bundle contains every TAYLOR SWIFT WEDDING contract that was listed on Kalshi on that UTC day — traded or not — 17 contract files on the latest covered day. Each file carries the full raw feed: every trade print with price, size and side, plus Level-2 order-book updates, in the same zstd-compressed schema as our crypto venues. Event contracts quote 0..1; turnover is USD-normalized.

Coverage runs March 2026 – July 2026 — 124 trading days, 209 MB compressed in total. A day typically holds 17 contract files (up to 17 on the busiest day, 17.0 MB). Pick individual days in the shop calendar for €1 each; delivery is an instant per-file download or one archive for the whole day.

Daily statistics

TAYLOR SWIFT WEDDING — last 30 days in the archive

Files, size, contracts traded, trades, USD turnover, buy share, quoted spread, top-of-book depth and order-book updates per UTC day, from the recorded tick data.

UTC dayFilesSizeNotes
2026-07-0517700 KBBuy day →
2026-07-04171.11 MBBuy day →
2026-07-031717.0 MBBuy day →
2026-07-021716.1 MBBuy day →
2026-07-011710.5 MBBuy day →
2026-06-301713.7 MBBuy day →
2026-06-29175.93 MBBuy day →
2026-06-28174.14 MBBuy day →
2026-06-2717856 KBBuy day →
2026-06-26175.78 MBBuy day →
2026-06-2517387 KBBuy day →
2026-06-2417264 KBBuy day →
2026-06-2317260 KBBuy day →
2026-06-22172.47 MBBuy day →
2026-06-21176.02 MBBuy day →
2026-06-20174.63 MBBuy day →
2026-06-1917709 KBBuy day →
2026-06-18171.41 MBBuy day →
2026-06-17173.95 MBBuy day →
2026-06-1617877 KBBuy day →
2026-06-15179.26 MBBuy day →
2026-06-14171.58 MBBuy day →
2026-06-1317987 KBBuy day →
2026-06-12171.70 MBBuy day →
2026-06-1117679 KBBuy day →
2026-06-1017338 KBBuy day →
2026-06-0917269 KBBuy day →
2026-06-0817343 KBBuy day →
2026-06-0717467 KBBuy day →
2026-06-0617337 KBBuy day →

Trades and turnover per day appear here once our daily statistics have captured this series — normally the morning UTC after a day closes.

Why CryptoStruct

Why buy Kalshi TAYLOR SWIFT WEDDING data here

Four things every page on this site is built on — and the reason the numbers above exist at all.

We record everything

The complete public feed of each venue as it was published: every Level-2 snapshot and update at the venue's full book depth, every trade with its aggressor side, every quote, funding, mark-price and liquidation event — for every instrument the venue lists, every UTC day since we added the venue. Nothing sampled, no top-N cut, no on-demand capture.

Institutional grade

Captured co-located at the venue with the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain that makes any gap visible, and one normalized schema across 35+ venues — the same capture our own high-frequency trading engine and enterprise feeds run on.

€1 per instrument-day

Any instrument-day is €1, series-day bundles start at €1 — no subscription, no minimum order, no tiers to unlock. Credit packs lower the effective price and never expire, and every venue has free full-day samples to test against first.

Self-service for everyone

Pick the days in the Data Shop, pay by card as a guest and download immediately — no sales call, no enterprise contract, no KYC. Coding agents buy the same files through the MCP server, and the free Agent Skill teaches them the format.

FAQ

Kalshi TAYLOR SWIFT WEDDING data — FAQ

What Kalshi TAYLOR SWIFT WEDDING data can I download?

Tick-by-tick trades and Level-2 order-book depth for every contract of the TAYLOR SWIFT WEDDING series on Kalshi (17 contract files on the latest day). One bundle = one UTC day of the whole series.

What is the Kalshi series ticker for TAYLOR SWIFT WEDDING?

KXTAYLORSWIFTWEDDING — every contract of the series carries this prefix in its ticker (followed by the event date and strike). Files in a day bundle are named by the full contract ticker, so a bundle holds every KXTAYLORSWIFTWEDDING-* contract listed that UTC day.

How far back does the TAYLOR SWIFT WEDDING data go?

Coverage runs March 2026 – July 2026 — 124 trading days in total.

What format are the Kalshi files in?

One zstd-compressed text file per contract per UTC day, in the same normalized schema as our crypto venues — see the market-data specification; free samples on the downloads page.

Can I get Kalshi TAYLOR SWIFT WEDDING data as CSV or Parquet?

Yes — trades export as gzipped CSV or Parquet at no extra cost, with integer microsecond UTC timestamps that load straight into pandas, polars or DuckDB. Kalshi records full order-book depth without a separate BBO stream, so book data ships in the native tick file — the free reader script converts it locally. See the formats overview.

How much does Kalshi TAYLOR SWIFT WEDDING historical data cost?

€1 per series-day bundle — every contract of the series for that day — no subscription, no minimum order; buy as a guest in the Data Shop and download immediately. Credit packs lower the effective price and never expire.

Do I need an account or a sales call?

No. Pick the TAYLOR SWIFT WEDDING series-days in the Data Shop, pay by card as a guest and download immediately — no subscription, no minimum order, no KYC, no enterprise contract, no sales call. Coding agents buy the same bundles through the MCP server.

How is the Kalshi TAYLOR SWIFT WEDDING data captured?

Co-located at the venue, message by message: every Level-2 update and every trade print carries the exchange timestamp and our receive timestamp in integer nanoseconds, an event-id chain makes any gap visible, and one normalized schema across 35+ venues means a parser written for Binance reads these files unchanged. It is the same capture our own high-frequency trading engine runs on — nothing sampled, no top-N cut.

Topics

Topic hubs featuring this series