DEV Community

Cover image for Stop Scraping Betting Sites: How to Build a Real-Time Sports Tracker in Python
E. Mitev
E. Mitev

Posted on

Stop Scraping Betting Sites: How to Build a Real-Time Sports Tracker in Python

#api #python #tutorial #webscraping

If you have ever tried to build a sports dashboard, an arbitrage scanner, or an automated trading bot, you already know the painful truth: scraping bookmaker data is a nightmare.

Sites like Bet365, FanDuel, and DraftKings have aggressive anti-bot protection (hello, Cloudflare). Even if you bypass it, they constantly change their HTML structure, breaking your scrapers every few weeks. Plus, managing custom WebSocket connections for live in-play odds is an infrastructure money pit.

In this quick guide, we’ll build a real-time sports odds tracker in Python without writing a single line of scraper code.

To do this, we’ll use PulseScore, a real-time sports odds API that aggregates multiple bookmakers into a single, unified JSON shape. They have a completely free tier (no credit card required), which is perfect for this project.

🛠️ The Tech Stack

  • Python 3.x
  • Requests library (for polling pre-match data)
  • WebSockets library (for ultra-low latency live updates)

First, make sure you have the required packages installed:

pip install requests websockets

1️⃣ Fetching Pre-Match Odds (REST API)

One of the biggest headaches of multi-bookie apps is normalizing data. Every bookmaker names their markets and sports differently. PulseScore solves this by serving the same JSON structure whether you fetch from Bet365, DraftKings, or Bwin.

Here is how to fetch upcoming tennis or soccer matches using their clean REST endpoints:

import requests

# Get your free API key from [https://pulsescore.net](https://pulsescore.net)
API_KEY = "YOUR_FREE_SECRET_HEADER_KEY"
URL = "[https://api.pulsescore.net/v1/odds/bet365](https://api.pulsescore.net/v1/odds/bet365)" # You can easily swap /bet365 for /fanduel or /bwin

headers = {
    "X-Secret": API_KEY,
    "Accept": "application/json"
}

response = requests.get(URL, headers=headers)

if response.status_code == 200:
    data = response.json()
    # Let's print out the first few upcoming events
    for event in data.get("events", [])[:5]:
        print(f"Match: {event['home_team']} vs {event['away_team']}")
        print(f"Start Time: {event['start_time']}")
        print(f"1X2 Odds: {event['markets'].get('1x2')}\n")
else:
    print(f"Error: {response.status_code}, {response.text}")
Enter fullscreen mode Exit fullscreen mode

2️⃣ Streaming Live In-Play Odds (WebSockets)

For live betting or real-time trading, a 10-second delay is unacceptable. WebSockets allow you to stream low-latency data straight into your application.

Here is how you can listen to live match updates with a 1-2 second refresh rate:

import asyncio
import websockets
import json

API_KEY = "YOUR_FREE_SECRET_HEADER_KEY"
WS_URL = f"wss://ws.pulsescore.net/live?secret={API_KEY}"

async def stream_live_sports():
    async with websockets.connect(WS_URL) as websocket:
        print("Successfully connected to PulseScore live stream...")

        while True:
            try:
                message = await websocket.recv()
                event_data = json.loads(message)

                # Print real-time shifts in lines/odds
                print(f"Live Update: {event_data['home_team']} vs {event_data['away_team']}")
                print(f"Current Score: {event_data['score']}")
                print(f"Live In-Play Odds: {event_data['live_markets']}\n")

            except websockets.ConnectionClosed:
                print("Connection closed, reconnecting...")
                break

asyncio.run(stream_live_sports())
Enter fullscreen mode Exit fullscreen mode

💡 Why This Beats Custom Scrapers

  1. Unified JSON Shape: You can swap /bet365 for /fanduel, /bwin, or /ps3838 in your code, and the payload format remains identical. No need to map data structures manually.

  2. No IP Bans: You don't have to manage proxy rotation or deal with headless browsers.

  3. Low Latency: Live events update every 1 second, keeping your data ahead of the curve.

Conclusion
Building sports tools should be about creating smart algorithms and beautiful dashboards, not fighting website layouts and Cloudflare blocks.eo

If you want to try this out yourself, head over to pulsescore.net, spin up a free plan (gives you 500 requests/mo right away), and test the payloads with the scripts above.

What are you currently building with sports data? Let me know in the comments below! ⚽🏀🎾

Top comments (0)