# Fotmob Scraper (`normdata/fotmob-scraper`) Actor

Every shot's exact location and xG, minute-by-minute momentum, head-to-head history, and attack-zone breakdown - for any FotMob match, league, or day of fixtures worldwide. Full standings, season fixtures, and transfers per competition, plus a complete leagues directory.

- **URL**: https://apify.com/normdata/fotmob-scraper.md
- **Developed by:** [Norm Data](https://apify.com/normdata) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 match results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

![Norm Data](https://i.ibb.co/rGbhM5Y8/Chat-GPT-Image-Sep-8-2026-02-20-50-PM.png)

## ⚽ FotMob Scraper

Every shot's exact location and expected goals, minute-by-minute match momentum, head-to-head history, and attack-zone breakdown, for any football match, league, or day of fixtures worldwide. One Actor covers matches, leagues, and the full competitions directory. No login.

Point it at a match ID, a date, or a league ID, and get export-ready data for analytics, fantasy tools, media, and league dashboards.

### 🎯 Who uses it?

#### 📊 Analysts & modelers

Shot-level xG, team-stat comparisons, and momentum data for match prediction, player evaluation, or content.

#### 🎮 Fantasy & scouting tools

Per-player ratings and stats across matches for player tracking and squad building.

#### 📰 Media & content teams

Lineups, timelines, head-to-head history, and highlights links for match summaries and reporting.

#### 🏆 League & competition dashboards

Full standings with home/away/form/xG splits, season fixtures, and transfer activity.

### ✨ What it does

- **Match:** one deep record per match, with final score, lineups and formations, per-player stats and ratings, the goal/card/substitution timeline, a full team-stat comparison, venue, referee, weather, player of the match, a shot-by-shot map with expected goals (xG), head-to-head history, a minute-by-minute momentum graph, and an attack-zone breakdown.
- **Matches:** every match on a given date, across every competition worldwide, in one call.
- **League:** a competition's full standings table (plus separate home/away/form/xG breakdowns), the complete season's fixtures and results, season top players, and recent transfers.
- **Leagues:** the complete real directory of competitions worldwide, for discovering league IDs.

Missing source values are returned as `null`, never invented.

### Why this scraper

- **Far more per match than a bare score.** Shot-by-shot xG, head-to-head history, live momentum, and attack-zone data all come on every match record, at no extra request.
- **One Actor instead of four.** Matches, leagues, and the leagues directory are all built in, not separate purchases.
- **Real transfer data and deeper standings on every league.** Recent transfers, plus home/away/form/xG standings breakdowns, come with every league pull, not just the plain table.
- **Fast and reliable at real scale.** Tested at 1,000 full match records in well under a minute, zero duplicates, zero crashes under load.
- **No login, no API key.**

### How it compares

Checked directly against the closest real competitor set on Apify (their own declared input/output):

| Capability | This actor | Closest competitors |
|---|:--:|:--:|
| Shot-by-shot map with per-shot xG | **yes** | not documented |
| Head-to-head history | **yes** | not documented |
| Match momentum graph | **yes** | not documented |
| Attack-zone breakdown | **yes** | not documented |
| Recent transfers per league | **yes** | not documented |
| Matches + Leagues + Directory in one Actor | **yes** | 4 separate Actors |
| Reported reliability | tested clean at 1,000-record scale | one competitor sits at 87 to 93% success |

### 📦 What data you get

| Entity | Useful fields |
| --- | --- |
| Match | ID, URL, teams, score, stadium, capacity, referee, weather, player of the match, highlights link, lineups, formations, per-player stats and ratings, the goal/card/substitution timeline, and a full team-stat comparison. |
| Shot & momentum data | A shot-by-shot map with pitch coordinates and xG, a minute-by-minute momentum graph, and a left/center/right attack-zone split per team per half. |
| Head-to-head | Summary record and the real match history between the two teams. |
| League | Standings (plus home/away/form/xG breakdowns), season fixtures and results, top players, and recent transfers. |
| Directory | Every real competition worldwide, for discovering league IDs. |

Every record includes `scraped_at` (UTC). Download your dataset from Apify as CSV, JSON, Excel, or XML.

### 💡 Use cases

#### 📊 Full breakdown of one match

```json
{ "mode": "match", "matchIds": ["5795363"] }
```

#### 📅 Every match on a given date

```json
{ "mode": "matches", "dates": ["20260920"] }
```

#### 🏆 A league's standings, fixtures, and transfers

```json
{ "mode": "league", "leagueIds": ["47"] }
```

#### 🔎 Discover league IDs

```json
{ "mode": "leagues" }
```

### ⚙️ How the input is organised

Pick a **mode** and a **maximum results** cap first, then fill in only the section that matches your mode:

| Section | What it's for |
| --- | --- |
| **Match mode** | Real FotMob match IDs, for a full per-match breakdown. |
| **Matches mode** | Dates in `YYYYMMDD` format, each getting its own fair share of the results cap. |
| **League mode** | Real FotMob league IDs, for standings, fixtures, and transfers. |

Leagues mode needs nothing else, it returns the full competitions directory. Use it to discover the league or match IDs the other modes need.

> **Apify Free plan:** every run is limited to a fixed 10-row sample. Upgrade your Apify plan to run your own settings.

### 🛡️ Limits & responsible use

This Actor reads only FotMob's own public match, league, and directory data. It never signs in and never accesses anything gated behind an account.

`weather` or `highlights_url` are sometimes null because FotMob itself doesn't set them for every match (indoor, older, or lower-profile fixtures), a real source-side gap, not a parsing failure. A match that hasn't started yet has no result status text in Matches mode; it fills in once the match kicks off.

If a match, league, or date can't be loaded, that row is skipped with a warning in the run log. The rest of the run continues.

### 📧 Contact

Need a scraper for a different site, or found something wrong with this one? norm.data.scrapers@gmail.com

### Local development

```bash
bun install
bun test                       # offline: normalization (real fixtures)
bun run src/main.ts             # reads storage/key_value_stores/default/INPUT.json
```

# Changelog

This Actor's version history is a separate document: https://apify.com/normdata/fotmob-scraper/changelog.md

# Actor input Schema

## `mode` (type: `string`):

Match: one deep record per match ID. Matches: every match on a given date, across every competition. League: a competition's full standings, season fixtures, and transfers. Leagues: the full directory of competitions. Only the fields for the mode you pick are used.

## `maxItems` (type: `integer`):

Caps how many rows this run writes. Starts at 10 for a quick sample; raise it for a full run.

## `matchIds` (type: `array`):

One or more real FotMob match IDs (the number after "#" in a match URL).

## `dates` (type: `array`):

One or more dates in YYYYMMDD format (e.g. "20260920"), each getting its own fair share of maxItems.

## `leagueIds` (type: `array`):

One or more real FotMob league/competition IDs (e.g. "47" for the Premier League - use Leagues mode to discover IDs).

## Actor input object example

```json
{
  "mode": "match",
  "maxItems": 10,
  "matchIds": [
    "5795363"
  ],
  "leagueIds": [
    "47"
  ]
}
```

# Actor output Schema

## `listings` (type: `string`):

Complete dataset with all scraped rows.

## `overview` (type: `string`):

Overview view with key fields displayed in a table.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "match",
    "maxItems": 10,
    "matchIds": [
        "5795363"
    ],
    "leagueIds": [
        "47"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("normdata/fotmob-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "match",
    "maxItems": 10,
    "matchIds": ["5795363"],
    "leagueIds": ["47"],
}

# Run the Actor and wait for it to finish
run = client.actor("normdata/fotmob-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "match",
  "maxItems": 10,
  "matchIds": [
    "5795363"
  ],
  "leagueIds": [
    "47"
  ]
}' |
apify call normdata/fotmob-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,normdata/fotmob-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8aDMj1sTTjRn0GC88/builds/KjTb47esIPujG93HQ/openapi.json