# FIFA World Cup 2026 Schedule & Results Scraper (`scrapers_lat/fifa-worldcup-scraper`) Actor

Scrape the official FIFA World Cup 2026 schedule, live results, group standings and teams: match date, status, score, home and away team with flag, stage, group, stadium and city. Export to JSON, CSV or Excel.

- **URL**: https://apify.com/scrapers_lat/fifa-worldcup-scraper.md
- **Developed by:** [Scrapers Lat](https://apify.com/scrapers_lat) (community)
- **Categories:** News, Automation, Developer tools
- **Stats:** 2 total users, 0 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $6.15 / 1,000 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

[![FIFA World Cup 2026 Schedule & Results Scraper](https://scrapers.lat/banners/fifa-worldcup-scraper.png)](https://console.apify.com/actors/ff6Gu30gMNjp19vk6/input)

## FIFA World Cup 2026 Schedule & Results Scraper

Here is one real result, with every field the actor returns for a match:

```json
{
  "recordType": "match",
  "matchNumber": 1,
  "matchId": "400021443",
  "date": "2026-06-11T19:00:00Z",
  "localDate": "2026-06-11T13:00:00Z",
  "matchTime": "98'",
  "status": "Played",
  "stage": "First Stage",
  "group": "Group A",
  "homeTeam": "Mexico",
  "homeTeamCode": "MEX",
  "homeFlag": "https://api.fifa.com/api/v3/picture/flags-sq-4/MEX",
  "homeScore": 2,
  "homeFormation": "4-1-2-3",
  "awayTeam": "South Africa",
  "awayTeamCode": "RSA",
  "awayFlag": "https://api.fifa.com/api/v3/picture/flags-sq-4/RSA",
  "awayScore": 0,
  "awayFormation": "5-3-2",
  "homePenalty": null,
  "awayPenalty": null,
  "winner": "Mexico",
  "referee": "Wilton SAMPAIO",
  "officials": [
    { "name": "Wilton SAMPAIO", "role": "Referee", "country": "BRA" },
    { "name": "Bruno PIRES", "role": "Assistant Referee 1", "country": "BRA" },
    { "name": "Nicolás Gallo Barragán", "role": "Video Assistant Referee (VAR)", "country": "COL" }
  ],
  "stadium": "Mexico City Stadium",
  "stadiumId": "400222084",
  "city": "Mexico City",
  "country": "MEX",
  "attendance": 80824,
  "competition": "FIFA World Cup™",
  "season": "FIFA World Cup 2026™",
  "observedAt": "2026-08-10T14:16:42.820Z"
}
```

(The `officials` array is trimmed above to three of eight entries for length; every value is real.)

The most complete FIFA World Cup 2026 scraper available. It returns every field the official FIFA source exposes for each match, standings row, and team, including formations, referees, the full officials crew, stadium, and attendance, and gives you three modes plus stage and group filters to target exactly the records you need.

**📥 [Input](https://apify.com/scrapers_lat/fifa-worldcup-scraper/input-schema) · 📤 [Output](https://apify.com/scrapers_lat/fifa-worldcup-scraper/output-schema) · 💰 [Pricing](https://apify.com/scrapers_lat/fifa-worldcup-scraper/pricing) · ▶️ [Examples](https://apify.com/scrapers_lat/fifa-worldcup-scraper/examples)**

![Apify](https://img.shields.io/badge/Platform-Apify-1CE1CE?logo=apify\&logoColor=white)
![Coverage](https://img.shields.io/badge/Coverage-World%20Cup%202026-blue)
![Output](https://img.shields.io/badge/Output-JSON%20%7C%20CSV%20%7C%20Excel-orange)
![Billing](https://img.shields.io/badge/Billing-Pay%20per%20result-brightgreen)

### Table of contents

- [What it does](#what-it-does)
- [Quickstart](#quickstart)
- [Input reference](#input-reference)
- [Output reference](#output-reference)
- [Example output record](#example-output-record)
- [Run via API and CLI](#run-via-api-and-cli)
- [Fetch results](#fetch-results)
- [Billing and limits](#billing-and-limits)
- [FAQ and troubleshooting](#faq-and-troubleshooting)

### What it does

The actor collects FIFA World Cup 2026 data in one of three modes and writes one normalized record per row to the run's dataset:

- **matches**: the full schedule and results, with scores, formations, referee, the complete officials crew, stadium, city, and attendance.
- **standings**: the group standings table, with position, played, won, drawn, lost, goals for and against, goal difference, points, and qualification status.
- **teams**: the participating teams, with code, confederation, country, foundation year, and crest.

Dates are ISO 8601, missing source values are returned as `null`, and you can narrow matches or standings to a single `stage` or `group`.

### Quickstart

Open the actor, paste this into the input, and press Run. It returns the first 10 matches of the schedule.

```json
{
  "mode": "matches",
  "maxRecords": 10
}
```

Every input field is optional. Leave `maxRecords` empty to return the entire dataset for the chosen `mode`. Set `mode` to `standings` or `teams` to collect those instead.

### Input reference

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `maxRecords` | integer | no | (all) | Maximum number of records to collect. Range 1 to 100000. Empty returns everything for the chosen mode. |
| `mode` | enum | no | `matches` | Which dataset to collect: `matches` (schedule and results), `standings` (group table), or `teams`. |
| `stage` | string | no | (empty) | Only return matches or standings from a stage whose name contains this text, for example `First Stage`, `Round of 16`, `Quarter-final`, `Final`. Empty means all stages. |
| `group` | string | no | (empty) | Only return matches or standings from a group whose name contains this text, for example `Group A`, `Group L`. Empty means all groups. |
| `competition` | string | no | (FIFA World Cup) | Advanced. Override the competition id. Leave empty unless you know the id. |
| `season` | string | no | (World Cup 2026) | Advanced. Override the edition id. Leave empty unless you know the id. |

All filters are optional. Leave everything at its default to get the complete World Cup 2026 match schedule.

### Output reference

One dataset item per record. The `recordType` field tells you which shape a record has. Types: `string`, `integer`, `object`, `object[]`, or `null` when the source value is absent.

Common field:

| Field | Type | Description |
|---|---|---|
| `recordType` | string | `match`, `standing`, or `team`. |
| `observedAt` | string | ISO 8601 timestamp of when the record was collected. |

Match records (`mode: matches`):

| Field | Type | Description |
|---|---|---|
| `matchNumber` | integer | Sequential match number in the tournament. |
| `matchId` | string | FIFA match id. |
| `date` | string | Kickoff time in UTC (ISO 8601). |
| `localDate` | string | Kickoff time in venue local time (ISO 8601). |
| `matchTime` | string | Clock at last update, for example `98'`, or `null` before kickoff. |
| `status` | string | Match status, for example `Played`, `Live`, `Scheduled`. |
| `stage` | string | Tournament stage, for example `First Stage`. |
| `group` | string | Group name for group-stage matches, or `null`. |
| `homeTeam` / `awayTeam` | string | Team names. |
| `homeTeamCode` / `awayTeamCode` | string | Three-letter team codes. |
| `homeFlag` / `awayFlag` | string | Crest image URLs. |
| `homeScore` / `awayScore` | integer | Goals scored, or `null` before the match. |
| `homeFormation` / `awayFormation` | string | Line-up formation, for example `4-1-2-3`, or `null`. |
| `homePenalty` / `awayPenalty` | integer | Penalty shootout score, or `null`. |
| `winner` | string | Winning team name, or `null` for a draw or unplayed match. |
| `referee` | string | Main referee name. |
| `officials` | object\[] | Full match officials crew, each with `name`, `role`, `country`. |
| `stadium` | string | Stadium name. |
| `stadiumId` | string | FIFA stadium id. |
| `city` | string | Host city. |
| `country` | string | Host country code. |
| `attendance` | integer | Reported attendance, or `null`. |
| `competition` | string | Competition name. |
| `season` | string | Edition name. |

Standings records (`mode: standings`):

| Field | Type | Description |
|---|---|---|
| `stage` | string | Stage the table belongs to. |
| `group` | string | Group name. |
| `position` | integer | Rank within the group. |
| `team` | string | Team name. |
| `teamCode` | string | Three-letter team code. |
| `flag` | string | Crest image URL. |
| `confederation` | string | Team confederation, for example `CONCACAF`. |
| `played` | integer | Matches played. |
| `won` / `drawn` / `lost` | integer | Match outcomes. |
| `goalsFor` / `goalsAgainst` | integer | Goals scored and conceded. |
| `goalDifference` | integer | Goal difference. |
| `points` | integer | Points. |
| `qualificationStatus` | string | Qualification status, for example `ConfirmedQualified`, or `null`. |

Team records (`mode: teams`):

| Field | Type | Description |
|---|---|---|
| `teamId` | string | FIFA team id. |
| `name` | string | Team name. |
| `shortName` | string | Short team name. |
| `code` | string | Three-letter team code. |
| `confederation` | string | Team confederation. |
| `country` | string | Country code. |
| `city` | string | Association base city, or `null`. |
| `foundationYear` | integer | Year the association was founded, or `null`. |
| `officialSite` | string | Official website, or `null`. |
| `flag` | string | Crest image URL. |

### Example output record

Real standings record from a live run (input `{"mode":"standings","maxRecords":3}`):

```json
{
  "recordType": "standing",
  "stage": "First Stage",
  "group": "Group A",
  "position": 1,
  "team": "Mexico",
  "teamCode": "MEX",
  "flag": "https://api.fifa.com/api/v3/picture/flags-sq-4/MEX",
  "confederation": "CONCACAF",
  "played": 3,
  "won": 3,
  "drawn": 0,
  "lost": 0,
  "goalsFor": 6,
  "goalsAgainst": 0,
  "goalDifference": 6,
  "points": 9,
  "qualificationStatus": "ConfirmedQualified",
  "observedAt": "2026-08-15T04:26:59.671Z"
}
```

Real team record from a live run (input `{"mode":"teams","maxRecords":3}`):

```json
{
  "recordType": "team",
  "teamId": "43911",
  "name": "Mexico",
  "shortName": "Mexico",
  "code": "MEX",
  "confederation": "CONCACAF",
  "country": "MEX",
  "city": "DISTRITO FEDERAL",
  "foundationYear": 1927,
  "officialSite": null,
  "flag": "https://api.fifa.com/api/v3/picture/flags-sq-4/MEX",
  "observedAt": "2026-08-15T04:27:04.572Z"
}
```

### Run via API and CLI

Start a run and wait for it to finish, then read the dataset. Replace `<TOKEN>` with your Apify API token.

Run synchronously and get dataset items in one call:

```bash
curl -X POST "https://api.apify.com/v2/acts/scrapers_lat~fifa-worldcup-scraper/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"mode":"matches","stage":"Round of 16"}'
```

Start a run asynchronously:

```bash
curl -X POST "https://api.apify.com/v2/acts/scrapers_lat~fifa-worldcup-scraper/runs?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"mode":"standings","group":"Group A"}'
```

Apify CLI:

```bash
apify call scrapers_lat/fifa-worldcup-scraper \
  --input '{"mode":"teams"}'
```

### Fetch results

Every run writes to a dataset. Fetch items as JSON, CSV, or Excel by changing `format`:

```bash
## JSON
curl "https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&clean=true&format=json"

## CSV
curl "https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&clean=true&format=csv"

## Paginate large datasets
curl "https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&offset=1000&limit=1000"
```

`<DATASET_ID>` is returned as `defaultDatasetId` in the run object. Use `offset` and `limit` to page through large result sets. `clean=true` drops empty and internal fields.

### Billing and limits

- **Pay per result.** You are charged per record returned (`result` event). See the [pricing tab](https://apify.com/scrapers_lat/fifa-worldcup-scraper/pricing) for the current per-result price.
- **No charge on failure.** If a run errors, the actor writes a single item with a populated `error` field and does not charge for it. Empty runs cost nothing.
- **Spend cap respected.** Set `maxTotalChargeUsd` on the run; once reached, the actor stops emitting and charging further billable results.
- **Free Apify plans** are capped at 10 records per run. Upgrade for higher `maxRecords`.

### FAQ and troubleshooting

**A run returned 0 records. Why?**
The `stage` or `group` filter matched nothing, or the chosen `mode` has no data yet. Loosen the filters or confirm the stage and group names. Zero-result runs are not charged.

**How do I get only knockout matches?**
Set `stage` to a knockout name such as `Round of 16`, `Quarter-final`, `Semi-final`, or `Final`. The filter matches any stage name that contains your text.

**Why are `homeScore` and `winner` null for some matches?**
The match has not been played yet. Missing source values are returned as `null`, never invented.

**Can I get the standings for a single group?**
Yes. Set `mode` to `standings` and `group` to `Group A` (or any group name).

**What is in the `officials` array?**
The full match officials crew: main referee, assistant referees, fourth official, VAR, assistant VAR, and reserve officials, each with name, role, and country.

**Is this an official FIFA tool?**
No. This actor is independent and has no affiliation with FIFA. It reads only data that is publicly available on FIFA's public match center.

### Related scrapers

- [ESPN Soccer Scraper](https://apify.com/scrapers_lat/espn-soccer-scraper): soccer standings, scores, and teams from ESPN.
- [Sofascore Scraper](https://apify.com/scrapers_lat/sofascore-scraper): live scores and match stats across sports.
- [MLB Stats Scraper](https://apify.com/scrapers_lat/mlb-stats-scraper): Major League Baseball schedules and stats.
- [SeatGeek Events Scraper](https://apify.com/scrapers_lat/seatgeek-events-scraper): event tickets and listings.
- [Eventbrite Scraper](https://apify.com/scrapers_lat/eventbrite-scraper): public events and organizers.

### More scrapers at scrapers.lat

Built and maintained by [scrapers.lat](https://scrapers.lat), where we publish scrapers for US and Latin American public platforms: company registries, government data, finance, e-commerce and more. Browse the catalog or request a custom scraper at [scrapers.lat](https://scrapers.lat).

***

> Independent tool, not affiliated with FIFA. Accesses only publicly available FIFA match center data.
>
> </content>

# Actor input Schema

## `maxRecords` (type: `integer`):

Maximum number of records (matches, standings rows or teams) to collect. Leave empty to return everything.

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

Choose the dataset to collect: the full match schedule and results, the group standings table, or the participating teams.

## `stage` (type: `string`):

Optional. Only return matches or standings from a stage whose name contains this text (for example: First Stage, Round of 16, Quarter-final, Semi-final, Final). Leave empty for all stages.

## `group` (type: `string`):

Optional. Only return matches or standings from a group whose name contains this text (for example: Group A, Group L). Leave empty for all groups.

## `competition` (type: `string`):

Advanced. Override the competition to scrape. Defaults to the FIFA World Cup. Leave empty unless you know the id.

## `season` (type: `string`):

Advanced. Override the edition to scrape. Defaults to World Cup 2026. Leave empty unless you know the id.

## Actor input object example

```json
{
  "mode": "matches"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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": "matches"
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapers_lat/fifa-worldcup-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": "matches" }

# Run the Actor and wait for it to finish
run = client.actor("scrapers_lat/fifa-worldcup-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": "matches"
}' |
apify call scrapers_lat/fifa-worldcup-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapers_lat/fifa-worldcup-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/ff6Gu30gMNjp19vk6/builds/8XAnYhoRMAgamB7yp/openapi.json