# UFC Event Fight Card API

> UFC fight cards by event id: bouts, fighters with records and stats, results, referees and venue

- Vendor: `ufceventfightcardapi` · version 1.0 · category Sports · tags ufc api, mma api, fight card api, ufc results api, mma fighters api, ufc events api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/ufceventfightcardapi
- This document: https://apiclay.com/docs/ufceventfightcardapi.md
- OpenAPI 3.1: https://apiclay.com/api/ufceventfightcardapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `ufceventfightcardapi`
- Updated: 2026-11-18

## About

## UFC Event Fight Card API

The live event feed behind UFC.com: for one event, its name, start time, status and venue, and every bout on the card with order, card segment and broadcaster, weight class, rule set, referee, both fighters (record, age, height, reach, stance, fighting out of, weigh-in) and the result with method, round and time.

Data comes from **ufc.com** (https://www.ufc.com). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/event?event_id=1335`; event ids increase over time (1310 is UFC 328 in May 2026).

### Routes

#### GET `/event` - Event fight card
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| event_id | path | number | yes | UFC event id, e.g. `1310`. |

Returns: `LiveEventDetail` with `EventId`, `Name`, `StartTime`, `Status`, `Location` (venue, city, country) and `FightCard[]` (`FightOrder`, `CardSegment`, `WeightClass`, `Referee`, `Fighters[]` with `Name`, `Record`, `Age`, `Height`, `Reach`, `Stance`, `Outcome`; `Result` with `Method`, `EndingRound`, `EndingTime`).

### Caveats

- There is no event search; ids are sequential. Live events update the same document during the fights.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by ufc.com.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /event — Event fight card
- Gateway: `GET https://api.apiclay.com/v1/api/ufceventfightcardapi/event`
- Public query params: `event_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/ufceventfightcardapi/event?event_id=<event_id>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
