Multi-League Season Results & Team Lookup: MCP config, n8n workflow and API

{
  "mode": "results",
  "sport": "epl",
  "season": "2024-2025",
  "teamQuery": "Arsenal",
  "includeOdds": true,
  "includeUpcoming": true,
  "enrichTeams": false,
  "regionalFallback": true,
  "maxItems": 20
}

---
name: multi-league-season-results-and-team-lookup
description: "Season match results with scores and 1X2 odds, league team rosters with standings, or team profiles. Runs the Apify Actor dataspryva/multi-league-season-results-and-team-lookup. Use when the user needs Multi-League Season Results data with fields such as homeTeam, awayTeam, homeScore, awayScore, matchDate, status and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/multi-league-season-results-and-team-lookup"
  store-url: "https://apify.com/dataspryva/multi-league-season-results-and-team-lookup"
---

# Multi-League Season Results & Team Lookup

Use this skill to fetch Multi-League Season Results data with the Apify Actor `dataspryva/multi-league-season-results-and-team-lookup` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `results`, `teams`, `teamSearch`, required | Season results with odds, a league's team roster, or a team lookup by name. |
| `sport` | string | Which competition to fetch. Ignored when leagueUrls is set. |
| `season` | string | Season to fetch. Soccer-style seasons use YYYY-YYYY (a plain YYYY expands to YYYY-YYYY); calendar-year leagues (MLB, MLS, NPB, J1, K League) use YYYY; 'current' is the live season. Used in results and teams modes. |
| `leagueUrls` | array | Optional: one or more OddsPortal league or season-results URLs (any sport or league, e.g. https://www.oddsportal.com/football/england/premier-league-2024-2025/results/). Overrides League and Season. |
| `teamQuery` | string | Team to look up by name (teamSearch mode), e.g. Arsenal or Real Madrid. |
| `includeOdds` | boolean | Add 1X2 average and maximum odds, bookmaker count and per-bookmaker prices to each result. |
| `includeUpcoming` | boolean | Keep scheduled and in-progress matches; turn off to get only finished results. |
| `enrichTeams` | boolean | In teams and teamSearch modes, open each team's page for its full name, venue, city, country and coach. Adds one request per team. |
| `regionalFallback` | boolean | When a league-season is empty on the main domain, retry it on the same site's regional edition (a few competitions, e.g. ACB, only publish older seasons there). Only fires on empty results, so it does not change normal runs. |
| `maxItems` | integer | Maximum records to return (1-10000). The run also stops when the source runs out of pages. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "results",
  "sport": "epl",
  "season": "2024-2025",
  "teamQuery": "Arsenal",
  "includeOdds": true,
  "includeUpcoming": true,
  "enrichTeams": false,
  "regionalFallback": true,
  "maxItems": 20
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~multi-league-season-results-and-team-lookup/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~multi-league-season-results-and-team-lookup/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `homeTeam`, `awayTeam`, `homeScore`, `awayScore`, `matchDate`, `status`, `oddsHome`, `oddsDraw`, `oddsAway`, `bookmakerCount`, `teamName`, `league`, `country`, `rank`, `points`, `matchesPlayed`, `wins`, `draws`, `losses`, `teamUrl`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.