BoxRec APIboxrec.com ↗
Access BoxRec fighter profiles, career records, KO percentages, titles, and trending boxers via 4 structured API endpoints. Search by name or BoxRec ID.
What is the BoxRec API?
The BoxRec API exposes 4 endpoints covering professional boxer profiles, career statistics, and trending fighter lists sourced from BoxRec. The get_boxer_stats endpoint returns over 10 structured fields per fighter — including total bouts, rounds, KO percentage, debut date, stance, height, and current titles — given a numeric BoxRec ID. Two search endpoints let you look up fighters by fuzzy name match or by exact registered full name.
curl -X GET 'https://api.parse.bot/scraper/40f10f57-6691-4b9a-80e2-859b4cd5a6a2/get_boxer_stats?boxer_id=659772' \ -H 'X-API-Key: $PARSE_API_KEY'
Get detailed statistics for a professional boxer by their BoxRec ID. Returns profile data including division, total bouts, rounds, KO percentage, career span, debut date, titles held, nationality, stance, height, and other biographical details. Fight history (recent_fights) requires site authentication and may be empty for unauthenticated access.
| Param | Type | Description |
|---|---|---|
| boxer_idrequired | string | The numeric BoxRec ID of the boxer (e.g. '659772' for Oleksandr Usyk, '628407' for Naoya Inoue). |
{
"type": "object",
"fields": {
"id": "string - BoxRec numeric ID",
"kos": "string - KO percentage",
"name": "string - fighter full name",
"bouts": "string - total number of professional bouts",
"debut": "string - debut date (YYYY-MM-DD)",
"career": "string - career span years",
"height": "string - height measurement",
"rounds": "string - total rounds fought",
"stance": "string - fighting stance",
"titles": "array of title strings held",
"division": "string - weight division",
"nationality": "string - country",
"recent_fights": "array of fight objects (may be empty without authentication)"
},
"sample": {
"data": {
"id": "659772",
"age": "39",
"kos": "64%",
"sex": "male",
"name": "Oleksandr Usyk",
"bouts": "25",
"debut": "2013-11-09",
"career": "2013-2026",
"height": "6′ 3″ / 191cm",
"rounds": "217",
"stance": "southpaw",
"titles": [
"IBF World Heavy",
"IBO World Heavy",
"WBC World Heavy"
],
"company": "Usyk17 Promotion",
"ratings": "#1 / 1,647#1 / 40",
"division": "Heavy",
"residence": "Oxnard, California, USA",
"birth_name": "Олександр Олександрович Усик",
"birth_place": "Simferopol, Crimea, Ukraine",
"nationality": "Ukraine",
"manager/agent": "Egis Klimas",
"recent_fights": []
},
"status": "success"
}
}About the BoxRec API
Endpoints and Data Coverage
The get_boxer_stats endpoint is the core lookup: supply a numeric boxer_id (e.g. 659772 for Oleksandr Usyk) and receive a structured profile with fields including kos (KO percentage), bouts, rounds, debut (YYYY-MM-DD), career span, height, stance, and a titles array listing any championship belts currently held. The get_trending_fighters endpoint requires no parameters and returns up to 30 fighters currently featured on the BoxRec homepage, each with a numeric id and name.
Searching for Fighters
Two search endpoints handle different lookup scenarios. search_fighters accepts a partial or full name string — including aliases like 'Canelo' — and returns a list of matching fighters with their BoxRec id, full name, alias, record (W-L-D string), division, and career span. This is the right endpoint for fuzzy or nickname-based searches. search_boxers_by_full_name performs a stricter filter: every word supplied in full_name must appear in a fighter's registered name, case- and accent-insensitive. It also accepts an optional max_pages integer (1–10) to control how many result pages are scanned, and returns metadata fields like pages_fetched, results_scanned, and more_results_available so callers know whether additional results exist beyond the scanned range.
Combining Endpoints
The intended workflow is: use search_fighters or search_boxers_by_full_name to find a boxer's numeric BoxRec id, then pass that id to get_boxer_stats to retrieve the full profile. The get_trending_fighters endpoint is useful for populating dashboards or discovery features without requiring a known fighter name or ID in advance.
The BoxRec API is a managed, monitored endpoint for boxrec.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when boxrec.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official boxrec.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a fighter comparison tool using
bouts,kos,rounds, andtitlesfromget_boxer_stats - Populate a trending boxers widget by polling
get_trending_fightersfor the current homepage lineup - Resolve fighter aliases to canonical BoxRec IDs using
search_fighterswith nickname inputs like 'Canelo' - Deduplicate fighter records in a database by using
search_boxers_by_full_nameto match against registered names - Track career debut dates and span data for historical boxing research via
get_boxer_stats - Aggregate title holders across divisions by collecting the
titlesarray from multiple fighter lookups - Build an autocomplete search for professional boxers using partial name queries against
search_fighters
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does BoxRec have an official developer API?+
What does `get_boxer_stats` return, and does it include individual fight results?+
bouts, rounds, kos (KO percentage), debut, career span, height, stance, titles, and biographical identifiers. Individual fight-by-fight history (the recent_fights field mentioned in the endpoint description) requires a separate request and is not included in the base response from this endpoint.What is the difference between `search_fighters` and `search_boxers_by_full_name`?+
search_fighters returns BoxRec's native fuzzy results, which can match aliases, nicknames, and approximate spellings — useful when you only know a fighter by a ring name. search_boxers_by_full_name is stricter: every word you supply must appear in the fighter's registered name. It also lets you control pagination depth via max_pages and returns results_scanned and more_results_available so you know the completeness of results.