# UFC & MMA Stats Scraper for espn.com — $0.50/1k (`blackfalcondata/espn-mma-scraper`) Actor

Scrape espn.com for MMA fights, fighters, rankings and events at $0.50 per 1,000 rows — the lowest price of any comparable UFC scraper. 42 measured stats per fighter per bout · reach, stance, gym & referee · career defence & closing sportsbook odds.

- **URL**: https://apify.com/blackfalcondata/espn-mma-scraper.md
- **Developed by:** [Black Falcon Data](https://apify.com/blackfalcondata) (community)
- **Categories:** Sports, Lead generation, Automation
- **Stats:** 2 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 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.

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

### What does UFC & MMA Stats Scraper for espn.com do?

Extracts MMA data from [espn.com](https://espn.com) in four shapes: fights, fighters, rankings and events. A fight row carries both corners of a bout — the method of victory, the ending round and clock, the weight class, the referee and the venue, plus 42 scored stats per fighter including significant strikes by target and position, takedowns, submission attempts, knockdowns and control time. Fighter rows add reach, stance, gym and a full career breakdown with measured career defence; ranking rows carry the board and the belt. Turn on odds and every fight row also carries the market: money line open, close and current, the best price across sportsbooks, and implied probability with the bookmaker margin divided out (priced for most bouts from 2020 on, none before 2019 or in 2026).

### How to use this actor

- 👉 **Register for a free Apify account** — no credit card required.
- 🎉 Just click **[Sign up free on Apify →](https://console.apify.com/sign-up?fpr=1h3gvi)** and complete a quick signup.
- 💰 A free Apify account includes $5 in monthly credits — enough to test this actor.
- ⏳ Scrape during the free trial, with no commitment or upfront payment required.

### Key features

- **🥊 42 measured stats per fighter per bout:** every bout yields one row per fighter carrying all 42 stats the source scores — significant strikes split by target *and* position, takedowns, advances, reversals, submissions and control time — plus the method, round, end time and referee. Present for both fighters in 25 of 25 sampled bouts in each of 1998, 2006, 2012, 2018 and 2024.
- **💰 Closing lines and no-vig win probabilities:** turn on `includeOdds` for the money line per fighter — open, close and current — the implied win probability with and *without* the bookmaker margin, line movement, the best price across every book on the bout, and how far the books disagree. A historical archive, and not a complete one: 2020-2025 priced 20-24 of every 21-24 bouts sampled, 2019 in part, closing lines for 2024-2025, nothing for 2026.
- **🎛️ Fights, fighters, rankings and events in one dataset:** pick with `mode`; every row is labelled `recordType`. Fighter rows add career rates and a full win/loss/draw/no-contest breakdown with title and finish counts; ranking rows carry the board, rank, trend and title defences; event rows carry the card and its bout count.
- **🛡️ Defensive numbers the source does not publish:** `includeCareerDefense` adds strikes absorbed per minute, striking defence and takedown defence, computed from the opponent side of every bout in the fighter's log — with `measuredBouts` and `measuredMinutes` on the row so you can see the basis. Every fight row also carries per-bout defence for free, because both corners are already read.
- **🎯 Filter before you pay:** narrow by date range, weight class, gender, country, stance, gym, minimum wins or losses, title fights only, method, result, fighter name, or active fighters only — applied before rows are delivered, so you are not charged for what you filtered out.
- **♻️ Only what changed:** recurring runs deliver and charge only for records that are new or whose tracked content moved — including a corrected statline or a re-priced market. Opt into UNCHANGED and EXPIRED rows when you need the full picture.
- **🔗 Paste a fighter or a fight page:** drop an espn.com fighter URL to get that fighter's whole bout log, a fightcenter URL to get the card, or a fightcenter URL that names one bout to get exactly that bout.
- **🔔 Notifications:** Telegram, Slack, Discord, WhatsApp Cloud API and a generic webhook, out of the box. Pair with incremental mode for alerts on new results.
- **📦 Compact and empty-field stripping:** `compact` keeps the identity and the core of whichever record type the row is; `excludeEmptyFields` drops nulls and empty values before push. Both shrink payloads for AI agents and dashboards.

### What data can you extract from espn.com?

Each row carries the identity every record type shares — `recordType`, `name`, `promotion`, `date`, `weightClass`, `url` — and then the columns its own type owns.

**Fight rows** carry both fighters, the winner, the method, the ending round and clock, the referee, the venue, and all 42 stats the source scores for that fighter in that bout: significant strikes split by target *and* position, takedowns, advances, reversals, submissions and control time. Defence comes free on the same row, because the opposite corner is already read.

**Fighter rows** carry the physical profile, the gym, and a full career breakdown: wins, losses, draws, no contests, title wins and finish counts, plus the published career rates. Turn on career defence for strikes absorbed per minute, striking defence and takedown defence, computed from the fighter’s own bout log with `measuredBouts` and `measuredMinutes` alongside them.

**Ranking rows** carry the board, the rank, the trend, title defences and whether the fighter holds the belt. **Event rows** carry the card, its venue and its bout count.

With `includeOdds`, fight rows also carry the market: money line open, close and current, implied win probability with and without the bookmaker margin, line movement, the best price across the books and how far they disagree. Odds are a historical archive and not a complete one: sampled 2026-09-01, 2020-2025 priced 20-24 of every 21-24 bouts checked, 2019 about half, 2018 and 2026 none. Closing lines exist only for 2024-2025, and a bout the books did not price ships those columns empty.

`includeDetails` adds each fighter’s published career rates to their fight rows. There is no separate detail page to scrape: the bout statline is always included.

### Input

The main inputs are a search keyword and a result limit. Additional filters and options are available in the input schema.

Key parameters:

- **`query`** — Promotion slug to scrape: "ufc", "pfl", "bellator", and 45 more that ESPN carries. Use a JSON array for several, e.g. \["ufc","pfl"]. This is NOT a free-text search — to find a fighter or an event by name, leave this as the promotion and use Name Search, or paste an ESPN URL into Start URLs.
- **`mode`** — fights = one row per fighter per bout with the full 42-stat line. fighters = roster profiles with career rates and a W-L-D breakdown. rankings = divisional + pound-for-pound boards. events = one row per card. (default: `"fights"`)
- **`season`** — Scope to one or more seasons, e.g. "2024". Accepts a JSON array like \["2023","2024"]. Applies to fights and events only — a roster and a ranking board are current, not historical, so fighters and rankings mode ignore it and say so in the log. Leave empty for ESPN’s current season.
- **`startUrls`** — Paste espn.com URLs. What each one returns depends on the Record type: in fights mode a fighter page gives that fighter’s whole bout log and a fightcenter page gives the card, while in fighters mode a fighter page gives that one profile and in events mode a fightcenter page gives that one event. A fightcenter link that names a bout (…/fightId/…) gives exactly that bout. Each URL becomes its own search and results are merged and deduplicated. A URL that does not match the selected mode is skipped with a message. Rankings are selected by promotion and cannot be addressed by URL. (default: `[]`)
- **`maxResults`** — Maximum rows to deliver (0 = unlimited). A row is whatever the selected mode produces: one fighter’s statline in a bout, a fighter, a ranking entry, or an event. In fights mode each bout yields two rows, one per corner. (default: `50`)
- **`fromDate`** — Only events on or after this date (YYYY-MM-DD). Narrowing by date marks the run coverage incomplete, so incremental mode will not mark unseen records as expired.
- **`toDate`** — Only events on or before this date (YYYY-MM-DD).
- **`weightClass`** — Substring match, e.g. "Lightweight", "Women's Strawweight". In rankings mode it matches the board name.
- **`gender`** — Restrict to one gender. Applies to fighters and rankings. (default: `""`)
- **`fighterCountry`** — Substring match on the fighter's citizenship, e.g. "Brazil".
- **`stance`** — Orthodox, Southpaw or Switch.
- **`gym`** — Substring match on the fighter’s gym, e.g. "American Top Team", "Pitbull".
- ...and 30 more parameters

### Input examples

**Basic search** — Keyword-driven search with a result cap.

→ Full payload per result — all standard fields populated where the source provides them.

```json
{
  "mode": "fights",
  "query": "ufc",
  "maxResults": 50
}
```

**Incremental tracking** — Only emit MMA records that changed since the previous run with this `stateKey`.

→ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set `emitUnchanged: true` to include unchanged records as well.

```json
{
  "query": "ufc",
  "maxResults": 200,
  "incrementalMode": true,
  "stateKey": "ufc-tracker"
}
```

**Compact output for AI agents** — Return only core fields for AI-agent and MCP workflows.

→ Small payload with the most important fields — ideal for piping into LLMs without token overhead.

```json
{
  "query": "ufc",
  "maxResults": 50,
  "compact": true
}
```

### Output

Each run produces a dataset of structured MMA records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

### Example MMA record

```json
{
  "recordType": "fight",
  "name": "Felipe Bunes",
  "fightId": "401623977",
  "eventId": "600039893",
  "eventName": "UFC Fight Night: Ankalaev vs. Walker 2",
  "date": "2024-01-13T21:00Z",
  "promotion": "ufc",
  "weightClass": "Flyweight",
  "cardSegment": "Prelims",
  "matchNumber": 11,
  "scheduledRounds": 3,
  "roundLengthSeconds": 300,
  "venue": {
    "name": "Meta APEX",
    "city": "Las Vegas",
    "state": "NV",
    "country": "USA"
  },
  "venueName": "Meta APEX",
  "venueCity": "Las Vegas",
  "venueState": "NV",
  "venueCountry": "USA",
  "location": "Las Vegas, NV, USA",
  "referee": "Mark Smith",
  "isCompleted": true,
  "fighter1Id": "5120301",
  "fighter1Name": "Joshua Van",
  "fighter2Id": "4916248",
  "fighter2Name": "Felipe Bunes",
  "winnerId": "5120301",
  "winnerName": "Joshua Van",
  "isDraw": false,
  "isNoContest": false,
  "isTitleFight": false,
  "method": "KO/TKO",
  "methodCategory": "ko/tko",
  "methodDetail": "Punches",
  "methodTarget": "Head",
  "round": 2,
  "time": "4:31",
  "fighterId": "4916248",
  "fighterName": "Felipe Bunes",
  "nickname": "Felipinho",
  "corner": "blue",
  "isWinner": false,
  "result": "loss",
  "opponentName": "Joshua Van",
  "opponentId": "5120301",
  "opponent": {
    "fighterId": "5120301",
    "fighterName": "Joshua Van",
    "corner": "red"
  },
  "country": "Brazil",
  "stance": "Orthodox",
  "reachInches": 69,
  "heightInches": 67,
  "weightLbs": 125,
  "gym": "Pitbull Brothers",
  "careerRecord": "14-9-0",
  "careerStrikeLPM": 3.17,
  "careerStrikeAccuracy": 0.549,
  "careerTakedownAvg": 1.08,
  "careerTakedownAccuracy": 0.25,
  "careerSubmissionAvg": 1.44,
  "careerKoTkoRate": 0,
  "careerDecisionRate": 0,
  "oddsProvider": "Consensus",
  "oddsProviderCount": 10,
  "moneyLine": 221,
  "moneyLineOpen": 175,
  "moneyLineClose": 240,
  "closingLineProvider": "Bet365",
  "moneyLineDecimal": 3.21,
  "moneyLineMovement": 65,
  "impliedProbabilityMovement": -0.069519,
  "bestMoneyLine": 250,
  "bestMoneyLineProvider": "ESPN BET",
  "impliedProbabilitySpread": 0.061508,
  "isFavorite": false,
  "isPickEm": false,
  "impliedWinProbability": 0.311526,
  "impliedWinProbabilityNoVig": 0.298355,
  "opponentMoneyLine": -274,
  "opponentImpliedWinProbability": 0.73262,
  "roundsOverUnder": 2.5,
  "overOdds": 104,
  "underOdds": -140,
  "knockDowns": 0,
  "totalStrikesAttempted": 101,
  "totalStrikesLanded": 57,
  "sigStrikesAttempted": 91,
  "sigStrikesLanded": 50,
  "sigDistanceHeadStrikesAttempted": 63,
  "sigDistanceHeadStrikesLanded": 28,
  "sigDistanceBodyStrikesAttempted": 16,
  "sigDistanceBodyStrikesLanded": 11,
  "sigDistanceLegStrikesAttempted": 11,
  "sigDistanceLegStrikesLanded": 10,
  "sigClinchBodyStrikesAttempted": 0,
  "sigClinchBodyStrikesLanded": 0,
  "sigClinchHeadStrikesAttempted": 1,
  "sigClinchHeadStrikesLanded": 1,
  "sigClinchLegStrikesAttempted": 0,
  "sigClinchLegStrikesLanded": 0,
  "sigGroundHeadStrikesAttempted": 0,
  "sigGroundHeadStrikesLanded": 0,
  "sigGroundBodyStrikesAttempted": 0,
  "sigGroundBodyStrikesLanded": 0,
  "sigGroundLegStrikesAttempted": 0,
  "sigGroundLegStrikesLanded": 0,
  "takedownsAttempted": 6,
  "takedownsLanded": 2,
  "takedownsSlams": 0,
  "takedownAccuracy": 0.33,
  "advances": 0,
  "reversals": 0,
  "submissions": 0,
  "timeInControl": "2:02",
  "sigDistanceStrikesAttempted": 90,
  "sigDistanceStrikesLanded": 49,
  "sigClinchStrikesAttempted": 1,
  "sigClinchStrikesLanded": 1,
  "sigGroundStrikesAttempted": 0,
  "sigGroundStrikesLanded": 0,
  "sigStrikesAbsorbed": 83,
  "sigStrikeDefense": 0.411348,
  "takedownsDefended": 0,
  "takedownDefense": 0,
  "sigStrikeAccuracy": 0.549451,
  "advanceToHalfGuard": 0,
  "advanceToSide": 0,
  "advanceToMount": 0,
  "advanceToBack": 0,
  "slamRate": 0,
  "url": "https://www.espn.com/mma/fightcenter/_/id/600039893",
  "portalUrl": "https://www.espn.com/mma/fightcenter/_/id/600039893",
  "listingId": "168e0faf1ef8c2d9c00817f8b42d7ecdeacdfc77b306455ec669e7cc2985f73d",
  "searchQuery": "ufc",
  "contentQuality": "full",
  "readIncomplete": false,
  "detailFetched": true,
  "scrapedAt": "2026-09-02T20:26:19.341Z",
  "source": "espn.com",
  "contentHash": "eb1eb4bb3ccdc3ded73f40a58a5f3f1bf77d4f6aad6db54ccabc60a4629448f7",
  "changeType": "NEW",
  "isRepost": false
}
```

### Incremental fields

When incremental mode is on, each record also carries:

- `changeType` — one of `NEW`, `UPDATED`, `UNCHANGED`, `REAPPEARED`, `EXPIRED`. Default output covers `NEW` / `UPDATED` / `REAPPEARED`; set `emitUnchanged: true` or `emitExpired: true` to opt into the others.
- `isRepost`, `repostOfId`, `repostDetectedAt` — populated when a new listing matches the tracked content of a previously expired one. Set `skipReposts: true` to drop detected reposts from the output.

### How to scrape espn.com

1. Go to [UFC & MMA Stats Scraper for espn.com](https://apify.com/blackfalcondata/espn-mma-scraper?fpr=1h3gvi) in Apify Console.
2. Pick a promotion under Promotion / Search Term(s) — "ufc", "pfl", "bellator" and 45 more — or paste an ESPN fighter or fightcenter URL into Start URLs.
3. Choose the Record type: fights, fighters, rankings or events.
4. Set `maxResults` to control how many rows you need (0 = unlimited).
5. Turn on Odds if you want the money line and implied win probability on each bout row.
6. Click **Start** and wait for the run to finish.
7. Export the dataset as JSON, CSV, or Excel.

### Use cases

- Extract MMA data from espn.com for market research and competitive analysis.
- Monitor new and changed MMA records on scheduled runs without processing the full dataset every time.
- Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
- Export clean, structured data to dashboards, spreadsheets, or data warehouses.

### How much does it cost to scrape espn.com?

UFC & MMA Stats Scraper for espn.com uses [pay-per-event](https://docs.apify.com/platform/actors/paid-actors/pay-per-event) pricing. You pay a small fee when the run starts and then for each result that is actually produced.

- **Run start:** $0.001 per run
- **Per result:** $0.0005 per MMA record

Example costs:

- 10 results: **$0.006**
- 25 results: **$0.014**
- 100 results: **$0.051**
- 200 results: **$0.1**
- 500 results: **$0.25**

#### Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of MMA records that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 200 MMA records per run, daily polling (30 runs/month). Costs scale linearly with the number of MMA records.

| Churn rate | Full re-scrape run cost | Incremental run cost | Savings vs full re-scrape | Monthly cost after baseline |
|---|---:|---:|---:|---:|
| 5% — stable niche query | $0.10 | $0.006 | $0.10 (94%) | $0.18 |
| 15% — moderate broad query | $0.10 | $0.02 | $0.09 (84%) | $0.48 |
| 30% — high-volume aggregator | $0.10 | $0.03 | $0.07 (69%) | $0.93 |

Full re-scrape monthly cost at the same cadence: $3.03. First month with incremental costs $0.28 / $0.57 / $1.00 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage is included in the per-result fee shown above.

### FAQ

#### How many results can I get from espn.com?

The number of results depends on the search query and available MMA records on espn.com. Use the `maxResults` parameter to control how many results are returned per run.

#### Does UFC & MMA Stats Scraper for espn.com support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed MMA records on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

#### Can I integrate UFC & MMA Stats Scraper for espn.com with other apps?

Yes. UFC & MMA Stats Scraper for espn.com works with Apify's [integrations](https://apify.com/integrations?fpr=1h3gvi) to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

#### Can I use UFC & MMA Stats Scraper for espn.com with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the [Apify API](https://docs.apify.com/api/v2). Client libraries are available for JavaScript, Python, and other languages.

#### Can I use UFC & MMA Stats Scraper for espn.com through an MCP Server?

Yes. Apify provides an [MCP Server](https://apify.com/apify/actors-mcp-server?fpr=1h3gvi) that lets AI assistants and agents call this actor directly. Use compact mode and `excludeEmptyFields` to keep payloads manageable for LLM context windows.

#### Is it legal to scrape espn.com?

This actor extracts publicly available data from espn.com. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

#### Your feedback

If you have questions, need a feature, or found a bug, please [open an issue](https://apify.com/blackfalcondata/espn-mma-scraper/issues?fpr=1h3gvi) on the actor's page in Apify Console. Your feedback helps us improve.

### You might also like

- [Transfermarkt Market Value & Transfer Scraper](https://apify.com/blackfalcondata/transfermarkt-market-value-scraper?fpr=1h3gvi) — Scrape Transfermarkt player market values with full value history, transfer records with fees, club.

### Getting started with Apify

New to Apify? [Create a free account with $5 credit](https://console.apify.com/sign-up?fpr=1h3gvi) — no credit card required.

1. Sign up — $5 platform credit included
2. Open this actor and configure your input
3. Click **Start** — export results as JSON, CSV, or Excel

Need more later? [See Apify pricing](https://apify.com/pricing?fpr=1h3gvi).

### Disclaimer

This actor accesses only publicly available data on espn.com. You are responsible for how you use the extracted data — in particular any personal information such as fighter names — and for complying with ESPN's terms of use, applicable data-protection law (including the GDPR where it applies), and the rules of any betting or data-redistribution regime that applies to you.

Odds are published sportsbook prices carried through as reported. They are historical market data, not a prediction, not advice, and not an invitation to bet.

### Search keywords

espn scraper, espn api, apify espn, espn data extraction, ufc & mma stats scraper, ufc & mma stats api, apify ufc & mma stats, ufc & mma stats data extraction, espn.com scraper, espn.com data, espn.com api.

# Actor input Schema

## `query` (type: `string`):

Promotion slug to scrape: "ufc", "pfl", "bellator", and 45 more that ESPN carries. Use a JSON array for several, e.g. \["ufc","pfl"]. This is NOT a free-text search — to find a fighter or an event by name, leave this as the promotion and use Name Search, or paste an ESPN URL into Start URLs.

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

fights = one row per fighter per bout with the full 42-stat line. fighters = roster profiles with career rates and a W-L-D breakdown. rankings = divisional + pound-for-pound boards. events = one row per card.

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

Scope to one or more seasons, e.g. "2024". Accepts a JSON array like \["2023","2024"]. Applies to fights and events only — a roster and a ranking board are current, not historical, so fighters and rankings mode ignore it and say so in the log. Leave empty for ESPN’s current season.

## `startUrls` (type: `array`):

Paste espn.com URLs. What each one returns depends on the Record type: in fights mode a fighter page gives that fighter’s whole bout log and a fightcenter page gives the card, while in fighters mode a fighter page gives that one profile and in events mode a fightcenter page gives that one event. A fightcenter link that names a bout (…/fightId/…) gives exactly that bout. Each URL becomes its own search and results are merged and deduplicated. A URL that does not match the selected mode is skipped with a message. Rankings are selected by promotion and cannot be addressed by URL.

## `maxResults` (type: `integer`):

Maximum rows to deliver (0 = unlimited). A row is whatever the selected mode produces: one fighter’s statline in a bout, a fighter, a ranking entry, or an event. In fights mode each bout yields two rows, one per corner.

## `fromDate` (type: `string`):

Only events on or after this date (YYYY-MM-DD). Narrowing by date marks the run coverage incomplete, so incremental mode will not mark unseen records as expired.

## `toDate` (type: `string`):

Only events on or before this date (YYYY-MM-DD).

## `weightClass` (type: `string`):

Substring match, e.g. "Lightweight", "Women's Strawweight". In rankings mode it matches the board name.

## `gender` (type: `string`):

Restrict to one gender. Applies to fighters and rankings.

## `fighterCountry` (type: `string`):

Substring match on the fighter's citizenship, e.g. "Brazil".

## `stance` (type: `string`):

Orthodox, Southpaw or Switch.

## `gym` (type: `string`):

Substring match on the fighter’s gym, e.g. "American Top Team", "Pitbull".

## `minWins` (type: `integer`):

Drop fighters whose career record shows fewer wins than this. A fighter with no record on file is dropped, not kept.

## `minLosses` (type: `integer`):

Drop fighters with fewer career losses than this.

## `titleFightsOnly` (type: `boolean`):

Keep only championship-length (five-round) bouts. ESPN ships no title flag, so a five-round main event without a belt is included too.

## `methodFilter` (type: `string`):

Keep only bouts that ended this way.

## `resultFilter` (type: `string`):

Keep only rows where this fighter won, lost, or drew.

## `searchQuery` (type: `string`):

Substring match on fighter name (or event name in events mode).

## `activeOnly` (type: `boolean`):

Fighters mode only: drop fighters ESPN marks inactive.

## `includeCareerDefense` (type: `boolean`):

Fighters mode only. Adds strikes absorbed per minute, striking defence and takedown defence — computed from the opponent side of every bout in the fighter’s log, because the source publishes no defensive career stat. Several times slower per fighter, so it is off by default. Each row reports `measuredBouts` and `measuredMinutes`, the basis the figures rest on.

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

Adds the money line for each fighter (open, close and current), the implied win probability with and without the bookmaker margin, line movement, the best price across the books, and the scheduled-rounds over/under. This is a HISTORICAL archive, not a live feed, and it is not complete: sampled 2026-09-01, 2020-2025 priced 20-24 of every 21-24 bouts checked, 2019 about half, 2018 and 2026 none at all. Closing lines exist only for 2024-2025. Bouts the books did not price, or that fall outside that window, come back with the odds columns empty.

## `includeDetails` (type: `boolean`):

Adds each fighter’s career averages to their fight rows: strikes landed per minute, striking and takedown accuracy, KO/TKO and decision shares. Slower per row. The 42-stat line for the bout itself is always included and is not affected by this.

## `compact` (type: `boolean`):

Core fields only (for AI-agent/MCP workflows).

## `excludeEmptyFields` (type: `boolean`):

Drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards.

## `incrementalMode` (type: `boolean`):

Compare against the previous run and label each row NEW, UPDATED, REAPPEARED, UNCHANGED or EXPIRED. By default you get NEW, UPDATED and REAPPEARED; the other two are opt-in below. stateKey is optional — leave it empty and the actor derives a stable key from the search inputs, so different filter sets never share state.

## `stateKey` (type: `string`):

Optional. Stable identifier for the tracked universe. Leave empty to auto-generate from search inputs.

## `emitUnchanged` (type: `boolean`):

Incremental mode only. Off by default: rows that have not changed since the previous run are skipped, so you are not billed for them again. Turn on to receive the full universe every run.

## `emitExpired` (type: `boolean`):

Incremental mode only. When a record a previous run delivered is gone from the source, emit a row for it marked EXPIRED, carrying its listingId so you can reconcile. Knowing something is gone requires seeing the whole set, so turning this on makes the run read the full universe for your search even when Max Results is small — the extra reading is not charged, and expired rows still count against Max Results. Suppressed automatically when the run used a date window or when part of the source failed to respond, because neither run saw the whole universe.

## `skipReposts` (type: `boolean`):

When incremental, skip records whose content matches an expired record from a prior run (cross-run duplicate detection).

## `telegramToken` (type: `string`):

Telegram bot token (from @BotFather). Required for Telegram notifications.

## `telegramChatId` (type: `string`):

Telegram chat or channel ID (e.g. "-100123456789"). Required when telegramToken is set.

## `discordWebhookUrl` (type: `string`):

Discord incoming webhook URL. Server Settings → Integrations → Webhooks → New Webhook.

## `slackWebhookUrl` (type: `string`):

Slack incoming webhook URL. api.slack.com/messaging/webhooks.

## `notificationLimit` (type: `integer`):

Maximum number of records included in each notification message (1–20).

## `notifyOnlyChanges` (type: `boolean`):

When Incremental Mode is on, only send notifications for records marked NEW, UPDATED or REAPPEARED. Has no effect outside incremental mode.

## `whatsappAccessToken` (type: `string`):

WhatsApp Cloud API permanent access token (System User token from Meta Business). Recipient must have messaged the business number within the last 24h (service-conversation window — free since Nov 2024).

## `whatsappPhoneNumberId` (type: `string`):

Your WhatsApp Business phone-number ID (numeric, from Meta dashboard). Required when whatsappAccessToken is set.

## `whatsappTo` (type: `string`):

Recipient phone in E.164 format without + (e.g. "436641234567"). Recipient must have messaged your business number within last 24h.

## `webhookUrl` (type: `string`):

Receives a JSON POST with {metadata, items} after each run. Universal escape hatch for n8n / Make / Zapier / custom backends.

## `webhookHeaders` (type: `object`):

Optional JSON object of custom headers (e.g. {"Authorization":"Bearer ..."}).

## `appConnector` (type: `string`):

Optional. Pick a connected app under Settings → API & Integrations to receive your results. The app receives up to the first 500 rows of the run and only rows that carry data — records marked EXPIRED are not sent, so an app-side copy will keep a record the source has dropped. The full run is always in the dataset. Best-effort across MCP connectors as Apify expands its catalog.

## `mcpIssueTeam` (type: `string`):

Only when the connected app is an issue tracker: the team (name or ID) the summary issue is created under, if that app requires one.

## Actor input object example

```json
{
  "query": "ufc",
  "mode": "fights",
  "season": "2024",
  "startUrls": [],
  "maxResults": 10,
  "gender": "",
  "titleFightsOnly": false,
  "methodFilter": "any",
  "resultFilter": "any",
  "activeOnly": false,
  "includeCareerDefense": false,
  "includeOdds": false,
  "includeDetails": true,
  "compact": false,
  "excludeEmptyFields": false,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "skipReposts": false,
  "notificationLimit": 5,
  "notifyOnlyChanges": false
}
```

# 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 = {
    "query": "ufc",
    "season": "2024",
    "maxResults": 10,
    "excludeEmptyFields": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("blackfalcondata/espn-mma-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 = {
    "query": "ufc",
    "season": "2024",
    "maxResults": 10,
    "excludeEmptyFields": False,
}

# Run the Actor and wait for it to finish
run = client.actor("blackfalcondata/espn-mma-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 '{
  "query": "ufc",
  "season": "2024",
  "maxResults": 10,
  "excludeEmptyFields": false
}' |
apify call blackfalcondata/espn-mma-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,blackfalcondata/espn-mma-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/n9TpnFlDDweesucWt/builds/hgFIgQyKZaHb7wrOb/openapi.json