How to Scrape ESPN Sports Data in 2026 (API & Python)

The fastest way to get ESPN sports data in 2026 is a structured API that returns scores, standings, rosters, and player stats as normalized JSON. ESPN itself runs on an internal JSON API that plenty of open-source projects reverse-engineer directly — it works, but it's undocumented, unofficial, and can change without warning. This guide covers the DIY route, no-code tools, and a structured API, plus the legal reality of scraping ESPN.

Why scrape ESPN?

ESPN's data — scores, standings, rosters, stats, news — feeds a recognizable set of products:

• Fantasy sports tools — rosters, player stats, and injury reports for lineup and waiver-wire decisions.
• Betting and odds comparison — game schedules, scores, and matchup context alongside odds data.
• Sports-news aggregation — pulling headlines and scores into a single feed.
• Fan and analytics apps — score trackers, standings widgets, historical stat lookups.

Is it legal to scrape ESPN?

ESPN is a Disney property, and its Terms of Use point to Disney's Terms of Use, which explicitly ban using "a robot, spider, script, or other automated means" to "access, monitor, copy or extract" its products — including, by name, web scraping and data mining. The only carve-out is public search-engine indexing that respects robots.txt. ESPN's own robots.txt blocks known AI-crawler user agents outright and disallows admin, login, and several parameterized/archive paths for everyone else.

That's the legal backdrop for scraping espn.com pages directly. A large share of real-world "ESPN API" usage instead targets ESPN's internal JSON endpoints (site.api.espn.com), which power ESPN's own apps and are widely documented by third parties — but every credible source is explicit that this is a reverse-engineered, unofficial integration, not a sanctioned API, with no published terms of its own. Treat it accordingly: fine for personal projects and prototyping, but not something to build a commercial product on without your own legal review. See Is web scraping legal in 2026? for the general framework.

Option 1: DIY in Python (and why it breaks)

Most DIY ESPN scrapers skip HTML entirely and call the undocumented JSON endpoints ESPN's own site uses:

import requests

def get_scoreboard(sport="football", league="nfl"):
    url = f"https://site.api.espn.com/apis/site/v2/sports/{sport}/{league}/scoreboard"
    resp = requests.get(url, headers={"User-Agent": "Mozilla/5.0"})
    resp.raise_for_status()
    return resp.json()

This works — until it doesn't. The recurring failure modes:

• No documentation, no stability guarantee. These endpoints are reverse-engineered from ESPN's own web/mobile traffic. Fields get renamed, restructured, or dropped between deploys with zero changelog.
• Schema varies by sport and league. A soccer scoreboard response doesn't shape identically to an NFL one — code that works for nfl can silently break for eng.1.
• User-Agent and rate-limit blocking. Default requests-style clients get blocked or throttled without warning; there's no documented rate limit to design around.
• Live data needs polling discipline. Scores update in real time with no push mechanism, so you're responsible for polling cadence and de-duplication.
• HTML scraping is worse. Falling back to scraping espn.com pages directly runs straight into the Terms-of-Use ban above, plus JS-rendered live scoreboards that need a headless browser.

Option 2: No-code tools

Generic web scrapers can pull a single scoreboard or standings table for a one-off report. They don't hold up for anything ongoing — no scheduling across sports/leagues, and they inherit the same undocumented-schema fragility as the DIY approach underneath.

Option 3: A structured ESPN API

A managed API normalizes the sport/league differences and absorbs the schema drift, so the same code works across the NFL, NBA, Premier League, and more:

curl -G "https://api.crawlora.net/api/v1/espn/scoreboard" \
  -H "x-api-key: $CRAWLORA_API_KEY" \
  --data-urlencode "sport=football" \
  --data-urlencode "league=nfl"

import requests

resp = requests.get(
    "https://api.crawlora.net/api/v1/espn/scoreboard",
    headers={"x-api-key": "YOUR_API_KEY"},
    params={"sport": "football", "league": "nfl"},
)
for game in resp.json()["data"]["games"]:
    home, away = game["competitors"]
    print(game["short_name"], game["status"]["detail"])

Example response (fields are illustrative — check the docs for the full schema):

{
  "data": {
    "sport": "football",
    "league": "nfl",
    "season": { "year": 2026, "type": 2, "name": "Regular Season" },
    "count": 14,
    "games": [
      {
        "id": "401547439",
        "date": "2026-09-08T17:00Z",
        "short_name": "KC @ BAL",
        "status": { "state": "pre", "detail": "Sun 1:00 PM", "completed": false },
        "venue": "M&T Bank Stadium",
        "competitors": [
          { "team": { "id": "33", "abbreviation": "BAL", "display_name": "Baltimore Ravens" }, "home_away": "home", "score": null },
          { "team": { "id": "12", "abbreviation": "KC", "display_name": "Kansas City Chiefs" }, "home_away": "away", "score": null }
        ]
      }
    ]
  }
}

Rosters, individual athletes, and standings follow the same sport/league pattern:

curl -G "https://api.crawlora.net/api/v1/espn/team-roster" \
  -H "x-api-key: $CRAWLORA_API_KEY" \
  --data-urlencode "sport=basketball" \
  --data-urlencode "league=nba" \
  --data-urlencode "team=lal"

resp = requests.get(
    "https://api.crawlora.net/api/v1/espn/standings",
    headers={"x-api-key": "YOUR_API_KEY"},
    params={"sport": "baseball", "league": "mlb", "season": 2026},
)
for group in resp.json()["data"]["groups"]:
    print(group["name"], [e["team"]["abbreviation"] for e in group["entries"]])

Which approach should you use?

What you can collect

• Scores and schedules — live and upcoming games across football, basketball, baseball, hockey, and soccer
• Standings — division/conference tables by season
• Rosters and athletes — player details, position, jersey number, experience
• Game detail — box scores and, where available, odds
• News — headlines and article links per sport/league

Limitations and common challenges

• Undocumented is undocumented. Every source covering ESPN's internal API says the same thing: no SLA, no changelog, no guarantee it looks the same next month.
• Coverage varies by league. Rankings and some detail endpoints only cover specific sports/leagues (e.g., college football/basketball polls).
• No official commercial terms. There's no published rate limit or license for the reverse-engineered endpoints — build accordingly.
• Live-score freshness is polling-based, not push — plan your refresh interval around how time-sensitive your use case is.

Where this fits

Pair ESPN's structured stats with SofaScore for broader international soccer coverage, or Google Trends to line up game-day search interest against real outcomes. See the full ESPN API reference for every available endpoint.

Sources

Start collecting

Test the ESPN endpoints in the Playground, read the full schema in the API docs, and check credit costs on the pricing page. For related guides, see how to scrape SofaScore for the same live scores and standings with deeper global-football coverage, how to scrape MLB for one league's schedules and box scores in full depth, how to scrape Google Trends and Is web scraping legal in 2026?.

Part of our how-to-scrape guide series — every platform we cover, in one index.