Premier League Fixtures & Results Scraper (PulseLive)

Scrapes Premier League fixture schedules, match results, half-time scores, attendance, and referee data from the official PulseLive API — the same JSON backend that powers premierleague.com.

What you get

One dataset row per fixture:

Field	Description
fixture_id	Unique PulseLive fixture ID
season_label	Season label, e.g. 2024/25
matchweek	Gameweek number (1–38)
kickoff_utc	Kick-off datetime in UTC (ISO-8601)
home_team / away_team	Full club name
home_team_short / away_team_short	Short club name (e.g. Man Utd)
home_score / away_score	Full-time score (null for upcoming fixtures)
ht_home_score / ht_away_score	Half-time score (null for upcoming fixtures)
venue_name	Stadium name
venue_city	City
referee	Match referee (e.g. Robert Jones)
attendance	Crowd attendance (null for upcoming fixtures)
status	C = completed, U = unplayed, L = live
source	Source API endpoint URL

A full Premier League season is 380 fixtures (20 teams x 38 matchdays).

Why this actor

• Direct from the source — PulseLive powers premierleague.com. Data is official, structured, and free.
• Referee + HT score + attendance — fields that multi-league aggregators typically strip.
• Datacenter-friendly — the API is open with a CORS Origin header; no residential proxy needed.
• Season-aware — pass any seasonId to pull historical seasons or the upcoming 2026/27 season (starts Aug 15 2026).

Input

{
  "maxItems": 380,
  "seasonId": 719
}

Field	Default	Description
maxItems	500	Maximum fixtures to return. Set to 380 for a complete PL season.
seasonId	719	PulseLive season ID. 719 = 2024/25. See notes below for other seasons.

Finding season IDs

PulseLive season IDs change each year. To discover the current/upcoming season ID, query:

https://footballapi.pulselive.com/football/competitions/1/compseasons

(Add Origin: https://www.premierleague.com header.)

Known IDs:

• 578 — 2022/23
• 596 — 2023/24
• 719 — 2024/25
• The 2026/27 ID will be available once the official site publishes it ahead of the Aug 15 2026 season start.

How it works

The actor calls the PulseLive fixtures list endpoint paginating 40 records at a time, then fetches the individual fixture detail for each match to add half-time scores and referee information. Both calls use the Origin: https://www.premierleague.com header required by the CORS guard on the API server.

A full 380-fixture season pull (list pages + 380 detail calls) takes roughly 10-15 minutes.

Example output

{
  "fixture_id": "115827",
  "season_label": "2024/25",
  "matchweek": 1,
  "kickoff_utc": "2024-08-16T19:00:00.000Z",
  "home_team": "Manchester United",
  "home_team_short": "Man Utd",
  "away_team": "Fulham",
  "away_team_short": "Fulham",
  "home_score": 1,
  "away_score": 0,
  "ht_home_score": 0,
  "ht_away_score": 0,
  "venue_name": "Old Trafford",
  "venue_city": "Manchester",
  "referee": "Robert Jones",
  "attendance": 73297,
  "status": "C",
  "source": "https://footballapi.pulselive.com/football/fixtures?comps=1&compSeasons=719&pageSize=40"
}

Use cases

• Fantasy football / FPL data feeds (fixtures, kickoff times, venue)
• Sports betting models (HT/FT scores, referee tendencies, attendance)
• Journalism and statistics (historical season archives)
• Building Premier League dashboards and APIs

Notes

• Upcoming fixtures have home_score, away_score, ht_home_score, ht_away_score, attendance, and referee set to null.
• The actor covers the English Premier League (competition ID 1). Other competitions (Championship, FA Cup) have different competition IDs and are not included.
• Rate limited to one request per 200ms. The actor is polite to the upstream API.