statleaders.ufc.com APIstatleaders.ufc.com ↗
Access UFC career, fight, round, and event stat leaderboards plus fighter and fight search/details via the statleaders.ufc.com API. 10 endpoints.
curl -X GET 'https://api.parse.bot/scraper/b2309d6f-3760-4fc9-9cb6-1bc89af26115/get_career_stats_leaders?country=usa&weight_class=HW&fighter_status=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve career-level stat leaderboards including Total Fights, Wins, Finishes, Striking, Grappling categories. Returns top 3 records per category.
| Param | Type | Description |
|---|---|---|
| country | string | Filter by country code (e.g., 'US', 'BR'). |
| weight_class | string | Filter by weight class. |
| fighter_status | string | Fighter status filter. Accepted values: '0' (all), '1' (active), '2' (retired). |
{
"type": "object",
"fields": {
"<category_id>": "object containing title (string), subtitle (string), and records (array of objects with rank, fighters, value, extra)"
},
"sample": {
"data": {
"TotalFights": {
"title": "Total Fights",
"records": [
{
"rank": "1",
"extra": "",
"value": "44",
"fighters": [
{
"link": "http://www.ufc.com/athlete/Jim-Miller",
"name": "Jim Miller"
}
]
}
],
"subtitle": ""
}
},
"status": "success"
}
}About the statleaders.ufc.com API
This API exposes 10 endpoints covering UFC statistical leaderboards and fighter/fight records sourced from statleaders.ufc.com and the UFC JSON:API. The get_career_stats_leaders endpoint returns top-3 ranked records across categories like Total Fights, Wins, Finishes, Striking, and Grappling, with optional filters for country, weight class, and fighter status. Separate endpoints cover single-fight records, combined two-fighter stats, round-level records, and event-level achievements.
Leaderboard Endpoints
Four leaderboard scopes are available: career (get_career_stats_leaders), single-fight (get_fight_stat_leaders), single-round (get_round_stat_leaders), and event-level (get_event_stat_leaders). Each returns a map of category IDs to objects containing a title, subtitle, and a records array. Every record includes rank, fighters, value, and extra fields. Career leaderboards accept country (e.g., 'US', 'BR'), weight_class, and fighter_status ('0' for all, '1' for active, '2' for retired). Fight and round endpoints accept country and weight_class. Event leaderboards take no filter parameters.
Combined Leaderboards
Two additional endpoints — get_fight_combined_stat_leaders and get_round_combined_stat_leaders — return records representing the combined output of both fighters in a single fight or round, rather than one fighter's individual performance. These accept a weight_class filter but not a country filter. Useful for identifying historically high-output fights by total significant strikes, takedowns, or similar two-fighter aggregate metrics.
Fighter and Fight Search
search_fighters accepts a name string and returns an array of UFC JSON:API athlete nodes, each with an id, type, attributes (including title, nickname, dob, and stats), and relationships. The id from those results feeds directly into get_fighter_details to retrieve a full fighter profile. Similarly, search_fights uses partial (CONTAINS) matching on fight titles (formatted as Fighter A vs Fighter B) and returns fight nodes with fight_final_method, fight_final_round, and fight_final_time. The fight id feeds into get_fight_details for complete fight data including finish method, round, and time.
Response Structure Notes
All JSON:API-based endpoints (search_fighters, get_fighter_details, search_fights, get_fight_details) include a jsonapi metadata object and a links object with pagination and self references. Leaderboard endpoints return a flat object keyed by category ID — the category IDs are not fixed strings documented in this spec, so callers should treat them as dynamic keys and rely on the title and subtitle fields within each category object for display labeling.
- Build a UFC record book page showing top-3 career leaderboards filtered by weight class and fighter status.
- Identify which country produces the most finishes by filtering
get_career_stats_leaderswith acountrycode. - Find the highest-output fights in UFC history using
get_fight_combined_stat_leadersranked by combined significant strikes. - Look up a fighter's biographical data and career stats by chaining
search_fighterswithget_fighter_details. - Retrieve the finishing method, round, and time of any historical UFC fight using
search_fightsandget_fight_details. - Track single-round performance records broken down by weight class via
get_round_stat_leaders. - Display event-level records such as most KO/TKO wins or shortest event using
get_event_stat_leaders.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does UFC have an official developer API?+
How many records does each leaderboard category return, and can I get beyond the top 3?+
Can I filter career leaderboards by both country and weight class at the same time?+
get_career_stats_leaders accepts country, weight_class, and fighter_status as independent optional parameters, and you can combine them in a single request to narrow results to, for example, active Brazilian middleweights.Does the API return full fight-by-fight history for a fighter?+
get_fighter_details returns fighter attributes including stats and bio, but does not return a structured list of individual past fights for that fighter. The fight endpoints (search_fights, get_fight_details) are separate lookups by fight title keyword or UUID. You can fork the API on Parse and revise to add an endpoint that queries a fighter's fight history by their UUID.What does `fighter_status` actually filter in `get_career_stats_leaders`?+
'1' limits results to currently active fighters, '2' to retired fighters, and '0' (or omitting the parameter) includes both. This filter only applies to the career leaderboard endpoint; fight and round leaderboards do not expose a status filter.