# Football Odds Movement Tracker (`sleeze22/football-odds-movement-tracker`) Actor

Track pre-match football odds, compare snapshots, and detect synchronized steam moves across bookmakers. No external odds API key required.

- **URL**: https://apify.com/sleeze22/football-odds-movement-tracker.md
- **Developed by:** [zSleezeh](https://apify.com/sleeze22) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

Monitor pre-match football odds, identify synchronized market moves, and build timestamped line-movement datasets without bringing an external odds API key.

Football Odds Movement & Steam Tracker compares every successful run with the previous snapshot and returns clean, analysis-ready records. Schedule it on Apify to turn changing prices into a useful historical feed for dashboards, alerts, research, and models.

### Why use this Actor?

- **See what changed:** compare current and previous decimal odds for every normalized selection.
- **Detect coordinated moves:** flag steam when no-vig probability shifts in the same direction at two or more bookmakers.
- **Reduce noise:** return only new or meaningful movements by default.
- **Build history automatically:** schedule recurring runs and export results as JSON, CSV, or Excel.
- **Start without an odds API key:** requests use your Apify proxy configuration.
- **Protect valid state:** failed or empty source responses never overwrite the last complete snapshot.

### Popular use cases

- Line-movement and market-monitoring dashboards
- Telegram, Discord, Slack, or email alert workflows
- Pre-match odds research and closing-line analysis
- Historical datasets for football models and backtests
- Data pipelines through the Apify API, webhooks, Make, or Zapier

### Supported coverage

The initial release monitors pre-match events from:

- Serie A
- Premier League
- La Liga
- Bundesliga
- Ligue 1
- UEFA Champions League

It normalizes these markets when available from the source:

- Match result (`1X2`)
- Goals totals (`Over/Under`)
- Both teams to score (`BTTS`)

Coverage varies by event and bookmaker. Unsupported or malformed markets are skipped rather than returned as unreliable data.

### Movement labels

| Label | Meaning |
| --- | --- |
| `new` | The selection was not present in the previous successful snapshot. |
| `rising` | Decimal odds increased beyond your configured threshold. |
| `falling` | Decimal odds decreased beyond your configured threshold. |
| `steam` | No-vig probability moved in the same direction at two or more bookmakers. |
| `stable` | Movement remained below the threshold; returned only when requested. |

Steam is an observable pricing signal. It is not proof of betting volume, informed money, or future results.

### Input example

```json
{
  "competitions": ["serie_a", "premier_league", "champions_league"],
  "daysAhead": 7,
  "movementThresholdPct": 2,
  "steamThresholdPct": 3,
  "includeStable": false,
  "maxEvents": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

#### Input options

| Field | Default | Description |
| --- | --- | --- |
| `competitions` | All supported | Competitions to monitor. |
| `daysAhead` | `7` | Event window from 1 to 14 days. |
| `movementThresholdPct` | `2` | Minimum decimal-odds percentage change to emit. |
| `steamThresholdPct` | `3` | Minimum no-vig probability-point move for a steam candidate. |
| `includeStable` | `false` | Include records below the movement threshold. |
| `maxEvents` | `100` | Maximum events processed in one run. |
| `proxyConfiguration` | Residential | Apify proxy used to access the public source. |

### Output example

```json
{
  "eventKey": "sofascore:12345678",
  "competition": "Serie A",
  "homeTeam": "Inter",
  "awayTeam": "Milan",
  "kickoffAt": "2026-09-20T18:45:00.000Z",
  "bookmaker": "Example Bookmaker",
  "market": "1x2",
  "line": null,
  "selection": "home",
  "odds": 1.91,
  "previousOdds": 2.02,
  "oddsChangePct": -5.45,
  "noVigChangePct": 3.18,
  "classification": "steam",
  "scrapedAt": "2026-09-20T10:15:00.000Z"
}
```

Every run writes matching records to the default Apify dataset, ready for API access and standard exports.

### Recommended setup

1. Select the competitions you need.
2. Keep the residential Apify proxy enabled.
3. Run once to create the initial snapshot; these records are labeled `new`.
4. Schedule the Actor every 15 minutes for useful pre-match history.
5. Connect a webhook or integration if you need alerts.

### Reliability and costs

- Residential proxy traffic is billed by Apify and can be the main run cost.
- Public source structures and availability can change.
- A run fails clearly when the source is blocked, empty, or structurally invalid.
- The previous valid snapshot is saved only after a complete successful fetch.
- Start with a small `maxEvents` value to measure your real proxy and compute costs.

### Responsible use

This Actor provides informational market data only. It does not place bets, guarantee profit, or provide betting advice. Users are responsible for applicable laws, gambling-age requirements, source terms, and data-redistribution rights.

This is an unofficial independent tool and is not affiliated with, sponsored by, or endorsed by SofaScore, any bookmaker, football competition, or data provider.

### Support

If a competition stops returning data or a market format changes, open an issue from the Actor page and include the run ID and affected competition. Do not include API tokens or private credentials.

# Actor input Schema

## `competitions` (type: `array`):

Football competitions to monitor.

## `daysAhead` (type: `integer`):

Collect events starting within this many days.

## `movementThresholdPct` (type: `number`):

Minimum decimal-odds percentage change to emit.

## `steamThresholdPct` (type: `number`):

Minimum no-vig probability-point movement for a steam candidate.

## `includeStable` (type: `boolean`):

Include records whose movement is below the configured threshold.

## `maxEvents` (type: `integer`):

Maximum number of football events processed per run.

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

Apify residential proxy is recommended.

## Actor input object example

```json
{
  "competitions": [
    "serie_a",
    "premier_league",
    "la_liga",
    "bundesliga",
    "ligue_1",
    "champions_league"
  ],
  "daysAhead": 7,
  "movementThresholdPct": 2,
  "steamThresholdPct": 3,
  "includeStable": false,
  "maxEvents": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("sleeze22/football-odds-movement-tracker").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("sleeze22/football-odds-movement-tracker").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 '{}' |
apify call sleeze22/football-odds-movement-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sleeze22/football-odds-movement-tracker"
        }
    }
}
```

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/NAhhe1u5N8QzYDpoq/builds/cDRjfzmnh1EYNcXq9/openapi.json