# Match Stats, Lineups & H2H API | Ratings, xG, Events (`reminiscent_folder/match-stats-lineups-api`) Actor

Full match data: team stats (possession, xG, shots), both lineups with ratings and per-player stats, goals, cards, subs, H2H, venue and referee. Ids or a team's latest match. Charged per match.

- **URL**: https://apify.com/reminiscent\_folder/match-stats-lineups-api.md
- **Developed by:** [Paul Bernabeu](https://apify.com/reminiscent_folder) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 match details

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

Everything the source holds on a match in one dataset: the match row with venue and referee, head-to-head record and recent form, every team statistic (possession, xG, shots, passes, actual play time) side by side, both lineups with formation, per-player rating, minutes and full stat lines, and the timeline of goals, cards and substitutions. Pass match ids, or a team name for its latest match. A Sofascore and Flashscore alternative that runs on Apify without proxies. Charged per match.

**$0.02 per match detail, plus $0.005 once per run.** Anything that fails, is not
found, or returns nothing is skipped and not charged.

### What data does this actor return?

One `MatchRow + StatRow + LineupPlayerRow + EventRow` per result, exported as JSON, CSV or Excel, or read from the Apify API:

`record_type`, `event_id`, `home_team`, `away_team`, `stat`, `home`, `away`, `side`, `player`, `position`, `rating`, `minutes`, `type`, `minute`

Timestamps are ISO 8601 in the timezone you choose, and field names are identical across all
nine actors in the suite. Every row carries the source's own ids, so results chain straight
into the other actors without a second lookup.

### How to use it

1. Open the input tab and pick a mode.
2. Type names, not ids. "Premier League" and "Carlos Alcaraz" are resolved through the
   source's own search, so you never have to look a number up.
3. Set **Max matches** to bound the run. Results are ordered by importance first, so a small
   cap returns the biggest matches rather than an arbitrary slice.
4. Press **Start**. A typical run finishes in two to five seconds.
5. Export as JSON, CSV or Excel, or call the dataset from the Apify API.

### Example output

```json
{
  "record_type": "stat",
  "event_id": 4512900,
  "home_team": "Napoli",
  "away_team": "Arsenal",
  "stat": "Expected Goals",
  "home": "0.84",
  "away": "1.72"
}
{
  "record_type": "lineup",
  "side": "away",
  "player": "Bukayo Saka",
  "position": "RW",
  "rating": 7.9,
  "minutes": 90
}
```

### How much does it cost to get match stats and lineups?

| Run | Cost |
|---|---|
| 1 match detail | $0.025 |
| 100 match details | $2.005 |
| 1,000 match details | $20.005 |

You are charged per match detail delivered, plus one run fee. There is no subscription and no
minimum. The run fee exists so a run that returns a single row still covers its own compute.

### Uses

- Post-match analysis with per-player ratings and xG
- Lineup and formation datasets
- Previews with H2H, form and referee in one call

### Honest billing

This actor charges only for what it delivers. A match that is not found, a name that does
not resolve, a market that is not published, or a request the source refuses is logged and
skipped at no cost. Every run writes a `RUN_SUMMARY` record to its key-value store stating
exactly how many rows were charged and how many were skipped, so you can audit any bill.

### The rest of the suite

All of these share one client and one set of field names, so ids and rows chain between them:

| Actor | What it does |
|---|---|
| [live-scores-api](https://apify.com/reminiscent_folder/live-scores-api) | Every match live right now across football, tennis, basketball and six more sports, one row per match with score, minute, period scores and main-line odds. No proxy, no key. Charged per live match. |
| [tennis-scores-api](https://apify.com/reminiscent_folder/tennis-scores-api) | Tennis matches today, live, by date, or per player and tournament: set scores with tiebreaks, live point, ATP/WTA ranking, tour and match-winner odds on every row. No proxy needed. Charged per match. |
| [football-scores-api](https://apify.com/reminiscent_folder/football-scores-api) | Football matches today, live, by date, or per club and competition: half-time and full-time scores, minute, round, venue and the 1X2 line on every row. No proxy needed. Charged per match. |
| [basketball-scores-api](https://apify.com/reminiscent_folder/basketball-scores-api) | Basketball games today, live, by date, or per team and league (NBA, EuroLeague, national leagues): quarter scores, records and moneyline on every row. No proxy needed. Charged per game. |
| [sports-odds-api](https://apify.com/reminiscent_folder/sports-odds-api) | Bookmaker odds per match: main market plus promoted markets and player props, decimal/fractional/American, opening price and movement. Price ids or a whole day of a sport. Charged per match. |
| [league-standings-api](https://apify.com/reminiscent_folder/league-standings-api) | League tables for any competition in nine sports: position, played, W/D/L, goals, points, form, streak, zones, plus pct and games behind for NBA-style tables. Charged per table. |
| [sports-search-api](https://apify.com/reminiscent_folder/sports-search-api) | Resolve team, player and competition names to ids across nine sports, with sport, country, club and URL. The glue for the other actors in this suite. Charged per query with results. |

### FAQ

#### Do I need an API key or a proxy?

No. The source serves Apify's own IP ranges directly, so this actor runs on the free plan
with no proxy and nothing added to your bill for proxy traffic. There is no login, no API
key and no rate-limit token to manage. Leave the proxy input empty unless you hit limits at
high volume.

#### Where does the data come from?

From 365Scores' public JSON API, the same endpoint their own website reads. It is not an
official partner API, so it can change without notice. Every route is tested against
captured payloads on each build, and the first response per route is logged so an upstream
change shows up immediately in the run log.

#### How often can I run it?

As often as you like. Use Apify's scheduler for a recurring pull, for example every minute
for live scores or once a night for results. Each run is billed independently at the prices
above, so a schedule costs the per-run fee each time it fires plus whatever it delivers.

#### What happens if a name cannot be resolved?

It is logged as a warning, skipped, and not charged. The run continues with the names that
did resolve, so one bad spelling in a list of fifty does not fail the run. Use the search
actor first if you want to confirm ids before a large run.

#### Can I use the ids in the other actors?

Yes, that is the point of the suite. Every row carries `event_id`, and team, player and
competition ids where they apply. Paste them straight into the odds, match stats or player
stats actors. No id translation is needed because all nine read the same source.

### Source and reliability

Data comes from 365Scores' public JSON API, the same one their website reads. No key, no
login, and unlike Sofascore or ESPN it serves Apify's own IP ranges directly, so no proxy is
needed. Every route was verified against live responses, the parsers are tested against
captured payloads on every build, and the first response per route is logged in a `[shape]`
line on each run so an upstream change is visible immediately. If a route ever fails, the
raw response is saved to the run's key-value store as `DIAG_<route>` for diagnosis.

# Actor input Schema

## `eventIds` (type: `array`):

365Scores match ids. Get them from any of the scores actors or the search actor.

## `teams` (type: `array`):

Team names or ids. For each, the most recent finished match is fetched in full.

## `sport` (type: `string`):

Used only to disambiguate team names.

## `includeStatistics` (type: `boolean`):

Possession, shots, xG, passes, corners, actual play time and more, home and away side by side.

## `includeLineups` (type: `boolean`):

Both lineups with formation, position, rating, minutes and every per-player stat.

## `includeEvents` (type: `boolean`):

Goals, cards and substitutions with minute and player.

## `includeH2H` (type: `boolean`):

Past meetings and both teams' recent form, attached to the match row.

## `includeOdds` (type: `boolean`):

Also add the published odds markets as 'odds' records.

## `timezone` (type: `string`):

IANA timezone for start times and the 'today' window, e.g. Europe/Paris or America/New\_York.

## `proxyConfiguration` (type: `object`):

Optional. The source serves Apify's own IPs directly, so no proxy is needed. Add one only if your account is rate-limited at volume.

## `requestDelayMs` (type: `integer`):

Politeness gap between requests. Raise it if you see 429s in the log.

## Actor input object example

```json
{
  "eventIds": [],
  "teams": [
    "Arsenal"
  ],
  "sport": "football",
  "includeStatistics": true,
  "includeLineups": true,
  "includeEvents": true,
  "includeH2H": true,
  "includeOdds": false,
  "timezone": "Europe/London",
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "requestDelayMs": 200
}
```

# 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 = {
    "teams": [
        "Arsenal"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("reminiscent_folder/match-stats-lineups-api").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 = { "teams": ["Arsenal"] }

# Run the Actor and wait for it to finish
run = client.actor("reminiscent_folder/match-stats-lineups-api").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 '{
  "teams": [
    "Arsenal"
  ]
}' |
apify call reminiscent_folder/match-stats-lineups-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,reminiscent_folder/match-stats-lineups-api"
        }
    }
}

```

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/IUM2qnZ6vLodUDieF/builds/94d797BauWLcANn4y/openapi.json