Boxing Data API - Explore details about past and upcoming fights
Fights are the individual bouts contested by boxers. Every fight has 2 boxers, a division_id
and if any belts are on the line, an array of title_ids
.
Understanding the fight data
Fight status
Upcoming fights that are happening in the future will have status = NOT_STARTED
, while fights that are happening today will have status = LIVE
and past fights will have status = FINISHED
.
Who won the fight?
Once a fight has finished we will update the final results, scores and identify the winner with winner = true
in the fighters details.
What was the result?
Details of the final result are in the results key which will contain the outcome and the round the fight ended.
Possible outcome values can include:
What was the score?
If the judges scorecard was used, e.g. in results that are not knockouts, the scores will be in the scores key.
Exploring the Fights Endpoint
The Fights endpoint enables you to build detailed fight schedules, live score boards and post fight analsys. There are two primary functionalities offered by this endpoint:
1. Search and filter many Fights:
- Endpoint URL:
https://boxing-data-api.p.rapidapi.com/v1/fights/
- Description: This request retrieves a list of fights according to any filters that you apply.
2. Get Details of a specific Fight:
- Endpoint URL:
https://boxing-data-api.p.rapidapi.com/v1/fights/<fight_id>
(replace<fight_id>
with the specific ID you want) - Description: By providing a specific fight ID, you can retrieve detailed information about that particular fight.
Utilizing the Fight endpoint in your code
Here are some code examples demonstrating how to interact with the Fight endpoint using various programming languages.
List all Fights
The following query params can be used to filter the fights returned
Query Param | Description | Example | Default | Required |
---|---|---|---|---|
date | The status of the event, either NOT_STARTED , LIVE or FINISHED . | NOT_STARTED | Null | No |
data_from | The starting date of date range, in format YYYY-MM-DD . | 2024-12-01 | Null | No |
date_to | The ending date of a date range, in format YYYY-MM-DD . | 2025-01-01 | Null | No |
date_sort | To sort the response by descending or ascending date order, either ASC or DESC . | DESC | DESC | No |
division_id | The division id the bout is fought in. | 671513530ad13034eb88265a | Null | No |
event_id | The event the fight is related to. | 671d12333012a998846efa3c | Null | No |
fighter_id | The id of a fighter involved in the fight. | 6715fc1faf69bb50508b7c72 | Null | No |
page_size | To limit the amount of items returned in the response. | 10 | 25 | No |
page_num | The page number of the response. | 5 | 1 | No |
Example response:
Get specific Fight
Example response:
Remember to replace [Your RapidAPI Key]
with your actual RapidAPI key in your code.