# FootballTransfers Scraper — Transfers, Rumours & ETV (`noahadler/footballtransfers`) Actor

Scrape footballtransfers.com EN tables: confirmed/latest transfers (player, clubs, date, fee label), transfer rumours, and most-valuable player ETV with age and team. Public HTML only — no Transfermarkt data. RESIDENTIAL GB recommended. Pay per row.

- **URL**: https://apify.com/noahadler/footballtransfers.md
- **Developed by:** [Noah Adler](https://apify.com/noahadler) (community)
- **Categories:** Other, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 transfer / etv rows

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

## FootballTransfers Scraper — Transfers, Rumours & ETV

**FootballTransfers scraper** for [footballtransfers.com](https://www.footballtransfers.com/en) (English public pages): latest/confirmed transfers, transfer rumours, and most-valuable player ETV.

Not Transfermarkt. ETV is FootballTransfers’ own estimated transfer value label — not a Transfermarkt market value.

> **Proxy:** RESIDENTIAL **GB** (or NL/US) recommended if the site challenges datacenter IPs.

**Keywords:** footballtransfers scraper · football transfers api · transfer rumours scraper · player etv · footballtransfers.com

***

### What it does

| Mode | Source (public EN HTML) | Fields |
|------|-------------------------|--------|
| `transfers` / `confirmed` | Latest transfers tables | player, from/to clubs, date, **fee label** (€ / Free / Loan) |
| `rumours` | Rumours table on the transfers page | player, from/to, date; fee when shown |
| `values` | Most valuable players | player, age, team, **ETV**, skill/potential |
| `all` | Combination of the above | Mixed `recordType` |

`feeEur` / `etvEur` are filled only when the label is a numeric € amount. Many transfers are Free/Loan — the billed field is **`feeLabel`**, not a guaranteed euro number.

Does **not** call `/api/*` or `/actions/` endpoints. Does not scrape footballtransfers.co.uk.

***

### Input

| Field | Required | Description |
|-------|----------|-------------|
| `mode` | No | `all` (default), `transfers`, `confirmed`, `rumours`, `values` |
| `maxItems` | No | 1–100 (default 30) |
| `proxyConfiguration` | Recommended | RESIDENTIAL GB |

#### Try it example

```json
{
  "mode": "all",
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "GB"
  }
}
```

***

### Output example (transfer)

```json
{
  "recordType": "transfer",
  "playerName": "Charlie Cresswell",
  "playerUrl": "https://www.footballtransfers.com/en/players/charlie-cresswell-1",
  "position": "D (C)",
  "fromClub": "Toulouse",
  "toClub": "Rennes",
  "date": "01-07-2027",
  "feeLabel": "€22.5M",
  "feeEur": 22500000.0,
  "mode": "all",
  "sourceUrl": "https://www.footballtransfers.com/en/transfers/latest-transfers",
  "market": "footballtransfers.com",
  "error": false
}
```

### Output example (value)

```json
{
  "recordType": "value",
  "playerName": "Lamine Yamal",
  "team": "Barcelona",
  "age": 19,
  "etvLabel": "€225.9M",
  "etvEur": 225900000.0,
  "skill": 92.8,
  "potential": 100.0,
  "rank": 1
}
```

***

### Pricing

Pay per event: actor start + one charge per dataset row.

# Actor input Schema

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

What to scrape from FootballTransfers EN pages: all (default), transfers (latest/confirmed fees), rumours, or values (most-valuable ETV).

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

Maximum dataset rows (1–100).

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

Use Apify RESIDENTIAL with country GB (or NL/US). Datacenter may work; residential is safer if Cloudflare challenges.

## Actor input object example

```json
{
  "mode": "all",
  "maxItems": 30,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "GB"
  }
}
```

# Actor output Schema

## `records` (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": "all"
};

// Run the Actor and wait for it to finish
const run = await client.actor("noahadler/footballtransfers").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": "all" }

# Run the Actor and wait for it to finish
run = client.actor("noahadler/footballtransfers").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": "all"
}' |
apify call noahadler/footballtransfers --silent --output-dataset

```

## MCP server setup

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

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/VNuCFm6AVREjNv7Du/builds/krGYuJRO6E3m5oIZr/openapi.json