Hey HN — long-time reader, second-time Show HN. I built Snuper[1], a small utility for inspecting and consuming live DraftKings prop data directly from their WebSocket feeds. The original itch came from building a live sports app where I wanted real-time betting lines and prop updates without relying on delayed REST endpoints or polling. DraftKings already streams this data — it’s just not documented. Snuper connects to the WebSocket, listens for message frames, and exposes structured prop updates in real time. No scraping, no headless browsers — just listening to the same stream the site uses. What it does: - Connects to DraftKings WebSocket feeds - Decodes and surfaces live prop updates - Useful for real-time dashboards, analytics, or experimentation - Minimal, transparent, and easy to inspect What it doesn’t do: - No automation, no betting, no bypassing auth - No attempts to modify or interfere with traffic - Read-only observation of publicly delivered data It’s intentionally small and focused — meant as a building block, not a product. Open to any feedback :) |