# UFC Scraper: Fighters, Cards, Results, Rankings & Odds (`automatic/ufc-fight-data`) Actor

Get UFC.com fighter profiles and career stats, full fight cards, results, official rankings, displayed moneylines and a saved card-change journal. Built for MMA analysts, bettors, fantasy apps, journalists and AI agents. Start with {} for a quick sample.

- **URL**: https://apify.com/automatic/ufc-fight-data.md
- **Developed by:** [Philip Kirkbride](https://apify.com/automatic) (community)
- **Categories:** Sports
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 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?

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

## UFC Scraper: Fighters, Cards, Results, Rankings & Odds

Get UFC.com fighter profiles and career stats, complete fight cards, results, official rankings, displayed moneylines and a saved journal of card changes. Built for MMA analysts, bettors, fantasy and app builders, journalists, and AI agents.

**Start with `{}` for a quick sample:** the next announced event's card, up to 15 bout rows. The Console form is prefilled for the next two events.

- **Fighters:** names, athlete identities, nicknames, records, divisions, career status, birthplace, measurements, gym and optional striking, grappling and win-method statistics.
- **Fight cards and results:** red and blue corners, card segment and order, main/co-main billing, weight class, title and bonus flags, winner, finish method, round and time.
- **Rankings:** every official list, including men's and women's pound-for-pound, champions, contenders and rank movement.
- **Moneylines:** the American odds displayed next to each bout on UFC.com, with the time observed.
- **Card changes:** added, cancelled, replaced, rescheduled, billing, weightclass, result and odds changes, each with before/after evidence and a detection time.
- **Fight week:** official weigh-in weights, the limit for each bout, made or missed weight, purse forfeits and catchweights, joined to the card's athlete identities, plus a journal of missed weights, replacements, cancelled or added bouts and weight-class changes.

### Also available

The sports odds and data suite: pick the job.

| Actor | Use when |
|---|---|
| **UFC Fight Data (this Actor)** | Fighters, cards, results and moneylines |
| [ESPN Scores & Odds](https://apify.com/automatic/espn-sports) | Scores, schedules and ESPN's betting lines |
| [Pinnacle Odds](https://apify.com/automatic/pinnacle-odds) | Sharp lines with stake limits |
| [US Sportsbook Odds](https://apify.com/automatic/actionnetwork-odds) | DraftKings, FanDuel and BetMGM lines side by side |
| [Tennis Results & Odds](https://apify.com/automatic/tennis-results-odds) | ATP and WTA results with bookmaker odds |

### Start collecting

Next two announced cards:

```json
{"mode":"events","eventType":"upcoming","maxEvents":2}
```

A completed event with every bout and its results:

```json
{"mode":"events","eventSlugs":["ufc-fight-night-november-07-2026"],"maxEvents":1}
```

Find a fighter by name, including career stats:

```json
{"mode":"fighters","searchTerms":["Ciryl Gane"],"includeStats":true,"maxResults":10}
```

Find active heavyweights born in France by name:

```json
{"mode":"fighters","searchTerms":["Gane"],"division":"heavyweight","fighterStatus":"active","country":"France","maxResults":20}
```

All official ranking lists:

```json
{"mode":"rankings"}
```

Watch specific cards for changes:

```json
{"mode":"events","eventSlugs":["ufc-334"],"onlyChangesSinceLastRun":true,"stateKey":"my-fight-desk","maxEvents":1,"maxResults":100}
```

The first complete observation establishes a baseline and returns zero change rows. Repeat with the same `stateKey` to receive subsequent changes. Use a separate key for each independent watchlist. Cards outside the current selection keep their previous observations; changing a date window never cancels a card.

Fight week: the next card with its official weigh-in results, one row per bout:

```json
{"mode":"fightWeek"}
```

A past card with a named weigh-in article (two missed weights and a 190 lb catchweight):

```json
{"mode":"fightWeek","eventSlugs":["ufc-334"],"weighInArticleSlug":"official-weigh-results-polymarket-ufc-334-gane-vs-hokit"}
```

Fight-week changes only, for a schedule that runs every 15–30 minutes from Monday of fight week:

```json
{"mode":"fightWeek","onlyChangesSinceLastRun":true,"stateKey":"my-fight-week"}
```

Start the fight-week journal before the weigh-ins: each card's first complete observation is its own baseline and returns no changes, and later runs report what moved since.

### Inputs

| Field | Meaning |
| --- | --- |
| `mode` | `events`, `fighters`, `rankings` or `fightWeek`. Omitted: events; `athleteSlugs` alone selects fighters. |
| `eventSlugs` | Specific UFC event slugs. Omit to select from the calendar. `fightWeek` takes one slug; omitted, it follows the next upcoming card. |
| `weighInArticleSlug` | `fightWeek` only: the UFC.com news slug of the Official Weigh-In Results article. Omitted, the Actor finds it in UFC.com's news search from six days before the card. |
| `athleteSlugs` | Specific UFC athlete slugs, such as `ciryl-gane` or `heili-alateng`. |
| `searchTerms` | Fighter names or event names; results from each term are merged. Numbered events such as `UFC 300` resolve directly. |
| `eventType` | `upcoming` (default), `past` or `all`; applies to calendar selection. |
| `dateFrom`, `dateTo` | Inclusive UTC dates, `YYYY-MM-DD`, using the published main-card start time. |
| `division` | Weight division slug, such as `lightweight`, `light-heavyweight`, `womens-flyweight`; rankings also accept `mens-pound-for-pound`, `womens-pound-for-pound` or `pound-for-pound`. |
| `fighterStatus` | `active`, `not-fighting` or `retired`. |
| `country` | Country of birth, such as `Brazil`, `France` or `United States`. |
| `gender` | `male` or `female`, from the published division; fighters and rankings. |
| `includeStats` | Include displayed career statistics; default `true`. |
| `maxEvents` | Cards to collect, 1–50; default 2, or 1 for the quick sample. |
| `maxResults` | Delivered rows, 1–10,000; default 1,000, or at most 15 for the quick sample. |
| `onlyChangesSinceLastRun` | Enable the saved journal; default `false`. Requires `mode: events` or `fightWeek`, and `stateKey`. |
| `stateKey` | Your journal name, up to 120 characters. Reuse it to continue a watchlist. |

Omit optional source lists to use discovery. Explicit empty lists, empty strings and null input values end the run as `no_results` and identify the field. Lists accept up to 50 entries; an unusable or duplicate entry is skipped into `OUTPUT.skippedSearches` and the rest still runs; when no usable entry remains the run ends as `no_results`. Names accept Unicode; slugs use lowercase letters, digits and hyphens. Search terms are limited to 200 characters, slugs and journal keys to 120, and country names to 100. Advanced collection limits are available in the Console; `OUTPUT` reports coverage, limits reached and any failed page URLs.

### What each row contains

`recordType` identifies a `bout`, `fighter`, `ranking`, `weighin` or `change`. All rows include `schemaVersion`, `recordKey`, `source`, `sourceUrl`, `sport`, `league` and `collectedAt`. Export the dataset as JSON, CSV or Excel, or consume it through the Apify API. Dataset views focus on cards, weigh-ins, fighters, rankings and changes.

| Row | Main fields |
| --- | --- |
| Bout | `event`, `eventKey`, `eventId`, `eventSlug`, `eventTitle`, `startTime`, `boutKey`, `boutId`, `fighterIds`, `redCorner`, `blueCorner`, `cardSegment`, `order`, `billing`, `weightClass`, `isTitleFight`, `bonuses`, `fightOfTheNight`, `performanceOfTheNight`, `status`, `result`, `odds`, `canonicalMarkets` |
| Fighter | `id`, `athleteKey`, `name`, `nickname`, `division`, `divisionKey`, `gender`, `status`, `record`, `wins`, `losses`, `draws`, `hometown`, `city`, `country`, `height`, `weight`, `reach`, `legReach`, `age`, `octagonDebut`, `trainsAt`, `fightingStyle`, `stats`, `statsAvailable`, `statsRequested`, `imageUrl` |
| Ranking | `division`, `divisionKey`, `gender`, `champion`, `topRanked`, `rankings` containing athlete identity, rank, native `change` text and signed `rankMovement` |
| Weigh-in | `eventKey`, `eventSlug`, `eventTitle`, `startTime`, `boutKey`, `boutId`, `fighterIds`, `fighters` (each with `athleteId`, `name`, `weighInName`, `weight`, `limit`, `madeWeight`, `missedBy`, `pursePercentForfeited`, `note`), `weightClass`, `weighInLabel`, `weightClassKey`, `catchweightLimit`, `weightLimit`, `isTitleFight`, `cardSegment`, `order`, `billing`, `status`, `cancelledBy`, `weighInStatus`, `missedWeight`, `onCard`, `inWeighInArticle`, `weighInArticleUrl`, `eventUrl` |
| Change | `changeId`, `changeType`, `eventKey`, `boutKey`, `previousBoutKey`, `before`, `after`, `beforeValue`, `afterValue`, `detectedAt`, `effectiveAt`, `confidence`, `evidenceUrls`; fight-week changes add `fighter` |

Ranking `topRanked` uses the linked caption leader. Pound-for-pound lists can also
resolve that athlete from their linked rank-1 entry. For division lists, `champion`
and `topRanked` are null when the champion is vacant or has no athlete link; the
first contender is not a champion, and names alone do not establish an identity.

Weigh-in rows follow the card: every card bout is one row, and the article only
annotates it. `weighInStatus` is `not_published` before the article exists,
`not_listed` when the article omits that bout, `awaiting` or `partial` while the
live article is still filling in weights, and `weighed_in` once both weights are
listed. Weights are pounds as printed. `limit` is the division limit plus UFC's
one-pound allowance for non-title bouts, the exact limit for title bouts, or the
catchweight. `madeWeight` is `false` when UFC's note says the fighter weighed in
above the limit or the weight exceeds it, and null until weighed or when no limit
is known. Article names are joined to the card's athlete slugs; a weigh-in line
that matches no card bout is listed in `OUTPUT.weighIn.unmatchedWeighIns` and
never invents a bout.

### Run summary (OUTPUT)

The key-value store's `OUTPUT` record reports status, delivered row counts,
`cards`, `failedPages`, collection limits and journal baseline/state flags.
Each failed or recovered page lists every attempt and its `attemptCount`, and
`retries` counts automatic retries. Timeouts, dropped connections and HTTP 429
or 5xx responses are retried up to three times per route with backoff; other
HTTP statuses and pages that fail validation are not retried and fail closed.
Fight-week runs add `weighIn` (event slug, article URL and how it was found,
bouts joined, missed weights, the article's notes) and `changeEventsCharged`.
Every `cards[]` entry includes `eventKey`, `eventSlug`, `bouts`, `complete`,
`cardPublished` and `errors`.

An upcoming event with valid event metadata and a future main-card start time
can have no published fight card yet. It reports `bouts: 0`, `complete: true`,
`cardPublished: false` and no errors. It delivers no bout rows and counts as a
complete observation, so an otherwise complete run has `status: succeeded`,
even when every selected card is unpublished. The journal can establish its
baseline from these empty observations; bouts first published afterward appear
as `added` changes.

Cards are read from both UFC's sectioned fight-card layout and its event-fights
listing layout. Listings without explicit section IDs use `cardSegment: null`
and `billing: "card"`; `order` follows the source's bout order. Main card and
prelims are assigned only when their section IDs are present. Athlete links
retain the same slug identities across English and Spanish site hosts, with
optional `/en/` or `/es/` prefixes. Displayed names, countries and weight-class
labels are preserved in the source language.

If saved journal history shows that an event previously published a card, a
missing card is incomplete and appears in `failedPages`. It never advances
disappearance counters or cancels prior bouts. Ordinary runs have no saved
history to compare. Past/started events without a card, malformed pages, and
existing card containers with missing or unreadable bouts remain failures.
`cardPublished` reports whether the page has a recognized fight-card or
event-fights listing container; `complete` determines whether every listed bout
parsed and that observation is safe to use.

### Output example

A real bout collected from the upcoming card on 12 November 2026:

```json
{
  "schemaVersion": "1.0",
  "recordType": "bout",
  "recordKey": "ufc:event:ufc-334:evan-elder:samuel-sanches",
  "source": "ufc",
  "sourceUrl": "https://www.ufc.com/event/ufc-334",
  "sport": "mma",
  "league": "ufc",
  "collectedAt": "2026-11-12T22:48:25.310518Z",
  "event": {
    "id": "159503",
    "fmid": "1345",
    "slug": "ufc-334",
    "eventKey": "ufc:event:ufc-334",
    "title": "Polymarket UFC 334",
    "startTime": "2026-11-15T02:00:00Z",
    "startTimePrecision": "main_card",
    "venue": "Madison Square Garden, \n    New York\nUnited States",
    "url": "https://www.ufc.com/event/ufc-334"
  },
  "eventKey": "ufc:event:ufc-334",
  "eventId": "159503",
  "eventSlug": "ufc-334",
  "eventTitle": "Polymarket UFC 334",
  "startTime": "2026-11-15T02:00:00Z",
  "boutKey": "ufc:event:ufc-334:evan-elder:samuel-sanches",
  "boutId": "13236",
  "fighterIds": [
    "evan-elder",
    "samuel-sanches"
  ],
  "redCorner": {
    "id": "evan-elder",
    "athleteKey": "ufc:athlete:evan-elder",
    "name": "Evan Elder",
    "url": "https://www.ufc.com/athlete/evan-elder",
    "country": "United States",
    "outcome": null
  },
  "blueCorner": {
    "id": "samuel-sanches",
    "athleteKey": "ufc:athlete:samuel-sanches",
    "name": "Samuel Sanches",
    "url": "https://www.ufc.com/athlete/samuel-sanches",
    "country": "Brazil",
    "outcome": null
  },
  "cardSegment": "early-prelims",
  "order": 13,
  "billing": "card",
  "weightClass": "Lightweight Bout",
  "isTitleFight": false,
  "bonuses": [],
  "fightOfTheNight": false,
  "performanceOfTheNight": false,
  "status": "scheduled",
  "statusNative": null,
  "result": {
    "winnerId": null,
    "winner": null,
    "method": null,
    "round": null,
    "time": null,
    "redOutcome": null,
    "blueOutcome": null
  },
  "odds": {
    "red": -110,
    "blue": -110,
    "redRaw": "-110",
    "blueRaw": "-110",
    "format": "american",
    "provider": null,
    "source": "ufc_display",
    "observedAt": "2026-11-12T22:48:25.310518Z"
  },
  "canonicalMarkets": [
    {
      "schemaVersion": "1.0",
      "recordId": "ufc:event:ufc-334:evan-elder:samuel-sanches:moneyline",
      "source": {
        "name": "ufc",
        "url": "https://www.ufc.com/event/ufc-334",
        "nativeId": "13236"
      },
      "event": {
        "nativeId": "159503",
        "slug": "ufc-334",
        "title": "Polymarket UFC 334",
        "participants": [
          "Evan Elder",
          "Samuel Sanches"
        ],
        "startTime": "2026-11-15T02:00:00+00:00",
        "endTime": null,
        "live": null
      },
      "sport": {
        "id": "mma",
        "label": "MMA"
      },
      "league": {
        "id": "ufc",
        "label": "UFC"
      },
      "market": {
        "family": "moneyline",
        "nativeType": "moneyline",
        "nativeName": "Displayed moneyline",
        "period": "game",
        "line": null,
        "lineRaw": null
      },
      "outcomes": [
        {
          "name": "Evan Elder",
          "price": 1.9090909090909092,
          "probability": 0.5238095238095238
        },
        {
          "name": "Samuel Sanches",
          "price": 1.9090909090909092,
          "probability": 0.5238095238095238
        }
      ],
      "liquidity": null,
      "volume": null,
      "status": "unknown",
      "provenance": {
        "actor": "ufc-fight-data",
        "collectedAt": "2026-11-12T22:48:25.310518+00:00"
      },
      "extensions": {
        "ufc": {
          "boutId": "13236",
          "fighterIds": [
            "evan-elder",
            "samuel-sanches"
          ],
          "provider": null,
          "oddsSource": "ufc_display",
          "firstParty": false
        }
      }
    }
  ]
}
```

Career `stats` preserve UFC.com's labels and displayed values, including striking accuracy, significant strikes landed and absorbed per minute, takedown accuracy and defense, takedown and submission averages, knockdowns, average fight time and KO/TKO, decision and submission win breakdowns. Measurements keep the units displayed by the source.

### Use stable identities across runs

Events use `ufc:event:<event-slug>` and retain the UFC node ID and event FMID in `event`. Fighters use their UFC athlete slug, including `heili-alateng` when a page displays “Alatengheili.” A bout key combines its event key with both athlete slugs sorted alphabetically. Corner swaps and name variants do not create a different bout. Opponent changes and event moves produce a new bout key linked through `previousBoutKey`.

Moneylines are in `odds.red` and `odds.blue`; missing prices are null. `canonicalMarkets` uses the same versioned market envelope as our other sports Actors, with `source.name: ufc`, `market.family: moneyline`, decimal outcome prices, and a UFC extension retaining athlete IDs. `provider` stays null: a displayed UFC.com line is not attributed to a sportsbook or represented as an opening or closing price.

### Read the change journal

| `changeType` | Detection rule |
| --- | --- |
| `added` | New pairing after the first baseline. |
| `cancelled` | UFC marks the bout cancelled, or the pairing is absent from two consecutive complete observations of that card. Confidence distinguishes the source status from an observed disappearance. |
| `replaced` | UFC retains the same bout ID, changes one opponent and retains the other athlete. |
| `rescheduled` | Published main-card time changes, or a unique athlete pair moves between two fully observed cards. |
| `billing` | Main/co-main designation, order, card segment, title flag or bonus changes. |
| `weightclass` | Published bout weight-class label changes. |
| `result` | Winner, outcomes, method, round, time or result status changes, including corrections. |
| `odds` | Displayed prices change, including becoming available or disappearing. |

Fight-week journals (`mode: fightWeek`) use their own change types:

| `changeType` | Detection rule |
| --- | --- |
| `missed_weight` | The official weigh-in results show a fighter above the limit (or UFC's note says so) where the previous observation did not. `fighter` and `afterValue` carry the weight, limit, overage and purse forfeit. |
| `replacement` | A bout leaves the card and a new one shares exactly one athlete: the same UFC bout ID, or a unique shared athlete on the same card. `beforeValue.out` and `afterValue.in` name who left and who came in. |
| `bout_cancelled` | UFC marks the bout cancelled on the card, the weigh-in article strikes it or notes its cancellation, or it is absent from two consecutive complete observations. |
| `bout_added` | A new pairing on a card already observed. |
| `weight_class_changed` | The bout's division changes on the card, or the weigh-in results move it to a catchweight or another division. |

Each fight-week change carries `sourceUrl` (the weigh-in article when it supplied the evidence, otherwise the card), `evidenceUrls` and `detectedAt`. A fight-week key never shares history with an events-mode key of the same name. Each card's first complete observation is its baseline, so the next card does not arrive as a batch of additions. Fight-week history older than 30 days is retired.

Failed, partial or capped collections never remove prior bouts. Complete cards are compared before delivery limits are applied; changes that cannot be delivered stay available for the next run. Abrupt bulk removals are held for review. A new source bout ID with one shared athlete remains an addition and a possible later disappearance, rather than an asserted replacement.

Undelivered changes remain available when a row or spending limit is reached. Reuse the same key to collect them. Deduplicate by `changeId`: an interrupted run may repeat a delivered ID. Two runs cannot update the same journal at once; use separate keys for independent watchlists. Dormant card history older than 180 days is retired.

### Pricing

**$0.015 per result ($15 per 1,000) plus $0.005 per run start.** One result is one bout, one fighter profile, one official ranking list, one weigh-in row, or one card change; nested stats and contenders are included. Fight-week change rows (`mode: fightWeek` with `onlyChangesSinceLastRun`) add a **$0.02 fight-week change** event, $0.035 per change in total. The start fee is charged per GB of memory; the default 512 MB run is one start event. Under pay per event there is no separate compute or proxy charge.

| Example | Results | Cost |
| --- | ---: | ---: |
| Quick sample (`{}`) | 13 | $0.20 |
| Next two fight cards | 22 | $0.335 |
| All 13 ranking lists | 13 | $0.20 |
| Change check with nothing new | 0 | $0.005 |
| Fight-week snapshot of a 13-bout card | 13 | $0.20 |
| Fight-week change check reporting two missed weights | 2 | $0.075 |
| 1,000 results | 1,000 | $15.005 |

### Good to know

- This is UFC.com data, not UFCStats round tables or a multi-book odds history. Missing source fields stay null; rankings follow the lists UFC currently publishes.
- Cards, rankings and prices can change after observation. Detection time is when this Actor noticed a change; it does not establish when the change occurred or confirm the reason for a withdrawal. Main-card time is not a scheduled individual bout time. `scheduled` means UFC displays no result yet; older pages can retain such pairings. Draws have no winner, and finish details can be missing.
- Large or broad fighter searches may stop before reaching every match. Narrow them by name or athlete slug and check `OUTPUT` for incomplete coverage. Journal state follows Apify storage retention.
- Independent tool, not affiliated with UFC. Use the data in accordance with the source's terms and applicable permissions.

# Actor input Schema

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

Collect fight cards, fighter profiles, official rankings, or fight-week weigh-ins (fightWeek: the next card or one eventSlugs card joined to its Official Weigh-In Results).

## `eventSlugs` (type: `array`):

Specific UFC event slugs, for example ufc-334. Omit to select from the calendar. fightWeek takes one slug. An empty list is an error.

## `weighInArticleSlug` (type: `string`):

fightWeek only: the UFC.com news slug of the Official Weigh-In Results article, for example official-weigh-results-polymarket-ufc-334-gane-vs-hokit. Omit to find it automatically during fight week.

## `athleteSlugs` (type: `array`):

Specific UFC athlete slugs. Use heili-alateng for Alatengheili. An empty list is an error.

## `searchTerms` (type: `array`):

Fighter names or event names. Each term is searched separately and merged by source identity. An empty list is an error.

## `eventType` (type: `string`):

Upcoming, past or all events. Specific eventSlugs bypass calendar selection.

## `dateFrom` (type: `string`):

Include events whose main card starts on or after YYYY-MM-DD.

## `dateTo` (type: `string`):

Include events whose main card starts on or before YYYY-MM-DD.

## `division` (type: `string`):

Filter fighters or rankings to one division.

## `fighterStatus` (type: `string`):

Filter fighter profiles by official career status.

## `country` (type: `string`):

Filter fighter profiles by country of birth, for example France.

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

Filter fighters or rankings by male or female division.

## `includeStats` (type: `boolean`):

Include the statistics displayed on each athlete profile.

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

Maximum event cards to collect: 1–50. Omitted: 2, or 1 for the quick sample.

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

Maximum bouts, fighters, ranking lists or changes delivered. Pending changes carry forward.

## `onlyChangesSinceLastRun` (type: `boolean`):

Save a complete first baseline, then return typed changes on later runs with the same stateKey. Works with events and fightWeek.

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

Required for changes only. Reuse a key for the same watchlist; use a new key for an independent baseline.

## `maxPages` (type: `integer`):

Bound calendar or athlete discovery. OUTPUT names incomplete discovery.

## `maxRequests` (type: `integer`):

Bound all page requests including fallback attempts.

## `useDatacenterFallback` (type: `boolean`):

Allow an alternate Apify datacenter connection after a page failure. Applies only to platform runs.

## Actor input object example

```json
{
  "mode": "events",
  "includeStats": true,
  "maxResults": 1000,
  "onlyChangesSinceLastRun": false,
  "maxPages": 10,
  "maxRequests": 40,
  "useDatacenterFallback": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (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": "events"
};

// Run the Actor and wait for it to finish
const run = await client.actor("automatic/ufc-fight-data").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": "events" }

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

```

## MCP server setup

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

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/NS422753t0eFESvLk/builds/bIs2d9wjTO2iJdD1b/openapi.json
