Polymarket Up/Down market slug — PRO generator for 1h / 4h / 1d (Eastern-Time, DST-safe)
Build the correct Polymarket event slug for the crypto Up or Down markets — across all five timeframes (5m / 15m / 1h / 4h / 1d) — and turn it into the CLOB token IDs you actually need. The hourly, 4-hour, and daily slugs are where naive code silently 404s; this is the build that gets them right, year-round. If you've been stuck on this, you're not alone Polymarket's Gamma API happily looks up an event once you already have the slug (/events?slug=...). But it never documents how to construct that slug for the recurring crypto Up/Down markets. So you reverse-engineer 5m and 15m (easy — they're just UTC timestamps) and then hit a wall on 1h / 4h / 1d: Eastern-Time boundaries, am/pm formatting, daylight saving, a noon-ET day that isn't midnight, a format Polymarket quietly changed, and last year's "zombie" markets answering to this year's date. Is this what you've been searching for? "polymarket event slug" / "polymarket slug api" / "polymarket get event by slug" "polymarket get market by slug" / "polymarket api get market by slug" "polymarket hourly markets" / "polymarket daily markets" "polymarket bitcoin up or down 1 hour" / "polymarket 4h market" "how to get polymarket market id" / "polymarket clob token id" / "polymarket condition id" "polymarket gamma api python" You came up empty because there is no documented slug format for these markets — that gap is exactly why this exists. What it does Give it an asset (btc / eth / sol / xrp), a timeframe, and optionally a time. It returns the canonical event slug and the polymarket.com/event/... URL, t_start / t_end in both UTC and Eastern Time, and with --resolve it validates against Gamma and hands you the CLOB token IDs and the real tickSize. python polymarket_slug_pro.py btc 1h --resolve matched : bitcoin-up-or-down-june-1-2026-9am-et [year-fallback] tokens : ['10806304314332875011...', '11523534956597908212...'] tick : 0.01 python polymarket_slug_pro.py btc 1d --resolve slug : bitcoin-up-or-down-on-june-1-2026 title : Bitcoin Up or Down on June 1? tick : 0.001 What's inside polymarket_slug_pro.py — the full generator + Gamma resolver (5m/15m/1h/4h/1d). test_polymarket_slug_pro.py — 13 offline unit tests (DST, noon-ET, am/pm, year-fallback). README.md + README.zh.md (English + 中文) and requirements.txt. Commercial license. What PRO handles that a quick script gets wrong Daylight saving — 4h/1h/1d boundaries are Eastern Time; a hard-coded UTC-5 offset 404s every slug all summer. PRO uses zoneinfo, correct year-round. The noon-ET day — the 1d market runs noon-ET → noon-ET (not UTC/ET midnight); the slug date is the settlement day. Format drift — Polymarket has shipped the 1h slug both with and without the year. PRO tries both and tells you which one is live. Cross-year zombies — the same date can resolve to last year's CLOSED market (depth 0); PRO filters closed/inactive. Dynamic tickSize — 1d uses 0.001, others 0.01; PRO reads the real value so your downstream order isn't rejected for an invalid tick. Free vs PRO There's a free, MIT-licensed generator for the two easy timeframes (5m / 15m) on GitHub — grab it, it's genuinely useful. The moment you need 1h, 4h, or 1d, you're in Eastern-Time + daylight-saving + noon-ET + format-drift territory, and that's this PRO build. Free earns your trust; PRO saves you the days of reverse-engineering and the live money you'd lose getting the boundary wrong. What it is, and what it isn't This tool builds and validates a data primitive — the slug (and the token IDs behind it). It does not place orders, predict prices, read the price-to-beat, or guarantee any profit. Slug formats are defined by Polymarket and can change; as of this build the live 1h format is the year-embedded variant (verified against Gamma), and the tool tries both so it survives a switch. --resolve uses the public read-only Gamma endpoint — no API key, no wallet. FAQ Does this work for "polymarket bitcoin up or down 1 hour" and the daily market? Yes — 1h and 1d are exactly the timeframes PRO adds, with correct Eastern-Time and noon-ET handling. Can I get the CLOB token id / condition id from it? Yes — --resolve returns the clobTokenIds; the slug is also how you reach the market id / condition id via Gamma. Why did my own slug 404 in summer but work in winter? Daylight saving. Your boundary used a fixed UTC offset; PRO uses zoneinfo so EST/EDT are both handled. What Python do I need? 3.9+. On Windows run pip install -r requirements.txt (it pulls tzdata, which zoneinfo needs on Windows). Refund — 14-day fix-or-refund Because this is downloadable source, it can't be "returned." If within 14 days it doesn't work as described in the README, email with a reproduction (the command + the output) and we'll fix it; if it still can't be made to work, you get a full refund. No refunds for "changed my mind" or buyer-side environment/network issues. If Polymarket changes the slug format, a corrective update is in scope — just tell us. Open-source companion (free 5m/15m): https://github.com/BlueWhale-Quant-Lab/polymarket-updown-event-slug-generator
Get it → bluewhalequantlab.gumroad.com