# UFC Fight Results – Fight Cards, Records, Finishes & Odds (`rowfeed/ufc-fight-results-scraper`) Actor

UFC fight results from ESPN's public API: method, round, time, fighter records and countries, plus Kalshi exchange odds joined in by fighter and date. One row per fight, upcoming or past cards.

- **URL**: https://apify.com/rowfeed/ufc-fight-results-scraper.md
- **Developed by:** [Rowfeed](https://apify.com/rowfeed) (community)
- **Categories:** Sports, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 fights

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

Get **UFC fight results and fight-card data** as one clean JSON row per fight: both fighters' names, records and countries, the finish (method, round, time) once a fight is over, and **Kalshi exchange odds joined in** when a market exists.
Built for MMA stats sites, betting-research tools, dashboards and AI agents that need machine-readable UFC fight cards without scraping HTML, solving a login, or running a browser.
Pulled straight from [ESPN's public MMA API](https://www.espn.com/mma/), with retries and a silent-failure check so a scheduled run keeps working when ESPN hiccups - runs on Apify's infrastructure with full API access, scheduling and monitoring built in.

### What you get

- **One row per fight** - both fighters (name, record going in, country, who won), weight class, card position (last fight on the card is always the main event), venue and status.
- **The finish, once it's final** - `method` (KO/TKO, Submission, Decision, ...), `round`, and elapsed `time` in that round, read straight from ESPN's own result data.
- **Kalshi odds joined in for free** - each fighter's Kalshi yes-ask price and vig-removed win probability while the market is trading (upcoming and live fights), matched to the ESPN fight by fighter surname and card date. No live market (a brand-new pairing, a card Kalshi doesn't list, or a market Kalshi has already settled, which has no price left) means `null` - never guessed.
- **Every UFC card ESPN lists** - numbered PPVs, Fight Nights and Dana White's Contender Series - for the next 31 days or the last 31 days.

### Sample row

One upcoming fight, `mode: "upcoming"`, matched to a live Kalshi market:

```json
{
  "event_name": "UFC Fight Night: Rosas Jr. vs. Barcelos",
  "event_date": "2026-09-26T21:00Z",
  "venue": "Meta APEX",
  "weight_class": "W Strawweight",
  "card_order": 1,
  "fighter_a": { "name": "Vanessa Demopoulos", "record": "11-8-0", "country": "USA", "winner": false },
  "fighter_b": { "name": "Yazmin Jauregui", "record": "11-2-0", "country": "Mexico", "winner": false },
  "result": null,
  "status": "STATUS_SCHEDULED",
  "status_detail": "Sat, September 26th at 5:00 PM EDT",
  "kalshi": {
    "event_ticker": "KXUFCFIGHT-26SEP26DEMJAU",
    "fighter_a_yes_ask": 0.13,
    "fighter_b_yes_ask": 0.87,
    "fighter_a_probability": 0.1263,
    "fighter_b_probability": 0.8737
  },
  "scraped_at": "2026-09-25T08:42:43+00:00",
  "url": "https://www.espn.com/mma/fightcenter/_/id/600061266/league/ufc"
}
```

Once a fight is over, `result` fills in, e.g. `{"method": "Submission", "round": 2, "time": "4:22"}`, and `kalshi` turns `null` as soon as Kalshi settles the market.

### How to use it

1. Click **Start**, or leave the input as-is - the default run scrapes every UFC card in the next 14 days.
2. To pull results instead, switch `mode` to "Date range" and set `dateFrom`/`dateTo` (up to 31 days).
3. Export the dataset as JSON, CSV or Excel, fetch it through the Apify API, or schedule the Actor to run daily so new cards and settled results stay current.

### Input

| Field | Default | What it does |
|---|---|---|
| `mode` | `upcoming` | `upcoming` scrapes the next `daysAhead` days from today. `range` scrapes `dateFrom`/`dateTo`. |
| `daysAhead` | `14` | Days from today to scan, when `mode` is `upcoming` (1-31). |
| `dateFrom` / `dateTo` | `""` | Explicit `YYYY-MM-DD` window when `mode` is `range`, inclusive, capped at 31 days. |
| `includeKalshi` | `true` | Join Kalshi's `KXUFCFIGHT` market onto each fight when one matches. |
| `maxFights` | `500` | Cap on fight rows returned. |

A day or a range with no card simply contributes zero rows - not an error.

### Output

One dataset row per fight with the fields shown above. Download as JSON, HTML, CSV, Excel or XML, pull it through the Apify API, or pipe scheduled runs into Google Sheets, Make, Zapier, n8n or your own code.

### Pricing

Pay per event, no subscription: **$2 per 1,000 fights** and **$0.001 per run start**. A 14-day upcoming window is typically one or two cards (10-14 fights each), so a default run costs a few cents. Kalshi odds ride along for free - they never add a charged event.

### Details

- **Sources**: ESPN's public site API (`site.api.espn.com`) for fight cards and results, and Kalshi's public trade API (`api.elections.kalshi.com`) for exchange odds. No login, no API key, no browser, no proxies. **Not affiliated with ESPN, UFC/Zuffa LLC, or Kalshi.**
- **Reliability**: 429 and 5xx responses are retried with exponential backoff (5 tries), an HTTP 200 without the expected data counts as a failure, and one bad date never stops the run - it becomes an uncharged error row (`date`, `error`, `errorMessage`) and the rest continues. A run fails only when it produced no rows *and* ESPN requests failed; a quiet stretch with no cards is a successful run with zero rows.
- **Kalshi matching**: fighters are matched by surname (the last word of their full name) plus the card's date, the same date Kalshi's own market rules describe as "originally scheduled for". A fight that doesn't match gets `kalshi: null` rather than a guess, and so does a pairing Kalshi lists twice as live markets on the same date (it relists fights now and then).
- **Unannounced bouts**: ESPN's "TBA vs Opponent TBA" placeholder carries no fighter data, so it is skipped and never charged. A bout with one named fighter is kept.
- **Run stats**: the `STATS` record in the run's key-value store holds fight rows, Kalshi matches, error rows, skipped/incomplete fights, and request counts.
- **Rate**: a short pause between every request, no concurrency, no proxies - polite to both APIs by default.

# Actor input Schema

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

"Upcoming cards" scrapes the next daysAhead days from today. "Date range" scrapes the explicit dateFrom/dateTo window below.

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

How many days from today to scan for cards when mode is "upcoming". A day with no card contributes zero rows, not an error.

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

Start date (YYYY-MM-DD) when mode is "range". Fetched one day at a time - ESPN rejects date ranges for this sport.

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

End date (YYYY-MM-DD) when mode is "range", inclusive. Capped at 31 days after dateFrom.

## `includeKalshi` (type: `boolean`):

Join each fight to its Kalshi KXUFCFIGHT market by fighter surname + card date, when one exists. Unmatched fights get a null kalshi block - never guessed.

## `maxFights` (type: `integer`):

Cap on fight rows returned. Each row is one `fight` event.

## Actor input object example

```json
{
  "mode": "upcoming",
  "daysAhead": 14,
  "dateFrom": "",
  "dateTo": "",
  "includeKalshi": true,
  "maxFights": 500
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("rowfeed/ufc-fight-results-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("rowfeed/ufc-fight-results-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 '{}' |
apify call rowfeed/ufc-fight-results-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rowfeed/ufc-fight-results-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/bGFvq1X0czbfTLxoI/builds/f4QFRSSeVGCeZ1s2F/openapi.json