Cross-game transfers and tournament tracking
Usa los endpoints de BO3.gg para convertir cross-game transfers and tournament tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Traducción en curso. Esta página se muestra temporalmente en inglés mientras se prepara la traducción al español.
Deportes y juegos28 endpoints activosapiKey
BO3.gg Esports Data API
Join BO3.gg match and tournament details with transfer, award, round, forum, and ranking records while preserving source IDs and scope.
Research BO3.gg matches, transfers, MVP awards, tournament stages, forum indexes, leaderboards, and player or team profiles.
Familias de endpoints
6
Parámetros documentados
130
Ejemplos
28
Snapshot en vivo del catálogo
Cobertura de BO3.gg
Endpoints activos
28
Métodos
GET
Parámetros obligatorios
41
Referencias de esquema
28
Economy Baseline1
Forum1
Forum Categories1
Match1
{
"platform": "BO3.gg",
"endpoint": "bo3-economy-baseline",
"method": "GET",
"path": "/bo3/economy-baseline",
"auth": "apiKey"
}Casos de uso
Workflows que encajan con BO3.gg
Research BO3.gg matches, transfers, MVP awards, tournament stages, forum indexes, leaderboards, and player or team profiles.
Match rounds and MVP award monitoring
Usa los endpoints de BO3.gg para convertir match rounds and mvp award monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Player, team, and leaderboard analysis
Usa los endpoints de BO3.gg para convertir player, team, and leaderboard analysis en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cómo maneja Crawlora esta plataforma
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de BO3.gg — 28 endpoints, 130 parámetros de solicitud documentados y 28 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
Documented endpoint coverage
28 documented BO3.gg endpoints, grouped into 28 request families — Economy Baseline, Forum and Forum Categories, plus 25 more.
Published request surface
130 request parameters are documented across those BO3.gg endpoints, 41 of them required — the full input contract is public before you write any integration code.
Known response shape
28 of the 28 BO3.gg endpoints ship a recorded example response, and 28 carry a documented response schema — you can code against the real JSON before the first request.
Documented failure modes
BO3.gg endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
Agent-callable MCP tools
28 hosted MCP tools back the BO3.gg endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
Descubre qué puede recopilar la API antes de integrarla
1 endpoints
Economy Baseline
/bo3/economy-baseline
GETapiKey
1 endpoints
Forum
/bo3/forum
GETapiKey
1 endpoints
Forum Categories
/bo3/forum-categories
GETapiKey
1 endpoints
Match
/bo3/match
GETapiKey
1 endpoints
Match Games
/bo3/match-games
GETapiKey
1 endpoints
Match History
/bo3/match-history
GETapiKey
Endpoints destacados
Endpoints de la API de BO3.gg
GETapiKeyexample
/bo3/economy-baselineBO3.gg CS2 economy baseline
Returns the site-wide CS2 round win rate for every pairing of buy levels (rounds, wins, win rate), the baseline to compare a team's `economy` view of bo3-team-stats with. Levels: -1 full eco, 0 semi-eco, 1 half buy, 2 full buy; the opposing level is null when it is unknown.
Notas de la respuesta
- `team_level` and `enemy_level` are buy levels: `-1` full eco, `0` semi-eco, `1` half buy and `2` full buy. `enemy_level` is `null` when the opposing buy is unknown. The extremes were checked against BO3.gg's per-team counters (full buy against full eco and the reverse); level `1` is the label with the least evidence. - Each cell has `rounds`, `wins` and `win_rate`. Cached for up to one hour.
Herramienta MCP bo3_economy_baseline
x-api-key:header
GETapiKeyexample
/bo3/forumBO3.gg forum threads with category and sort filters
Returns BO3.gg forum threads for one game with paging: a `category` id from bo3-forum-categories and `sort` (`activity` with pinned threads first, `newest`, `comments`, `rating`), up to 100 per page. Each thread has slug, title, category, comment count, rating, pinned flag, created and last-activity times and the author's nickname; post bodies, reactions and replies are not returned.
Notas de la respuesta
- `total` counts the threads that fit the filters (221 for CS2 today) and `has_more` says whether another page exists. A game without a forum, such as Dota 2, returns an empty list. - Only thread metadata is returned; posts and replies are user-written content and are not exposed. A category filter makes one extra request to validate the id. The response is cached for up to ten minutes.
Herramienta MCP bo3_forum
x-api-key:headergame:querycategory:query+3 más
GETapiKeyexample
/bo3/forum-categoriesBO3.gg forum categories
Returns the BO3.gg forum categories of one game (id, slug and title, ordered by id; CS2 has CS2, IDEAS AND BUGS and OFF TOP) that the `category` filter of bo3-forum accepts.
Notas de la respuesta
- The list is read live per game, so it follows the site; a game without a forum returns an empty list. The response is cached for up to one day.
Herramienta MCP bo3_forum_categories
x-api-key:headergame:query
GETapiKeyexample
/bo3/matchBO3.gg match detail
Returns one BO3.gg match by slug: teams with scores and winner, status, best-of, tier, start and end time, tournament, stage and round, the maps played with scores, the site's AI prediction, live and recorded streams and the key-fact insights for each team. The slug comes from bo3-match-history.
Notas de la respuesta
- `status` is `upcoming`, `current` (live), `finished`, `defwin` (default win), `canceled` or `postponed`; `tier` is `s`, `a`, `b`, `c` or `d`; `event_type` is `lan` or `online`; each map `status` is `upcoming`, `current` or `finished`; a stream `platform` is `twitch`, `youtube`, `kick` or `other`. - `maps` lists the maps with winner score and loser score, `prediction` is the site's AI forecast and `insights` the key facts per team (English). Lineups are not part of this route: use [bo3-team](bo3-team.md) for rosters and [bo3-match-players](bo3-match-players.md) for player statistics. An unknown slug returns `404`. The response is cached for up to ten minutes.
Herramienta MCP bo3_match
x-api-key:headerslug:query
GETapiKeyexample
/bo3/match-gamesBO3.gg esports match maps with round-by-round results
Returns the maps of one BO3.gg match with round-by-round results: for each map the number, map name, state, start, duration in seconds, final score, per-half side results (CT or T score, overtime) and every round with its number, duration, end reason, winning side and running score. A match with no maps yet returns an empty list.
Notas de la respuesta
- Durations are converted from the upstream's nanoseconds to seconds. `rounds[].end_reason` is passed through as BO3 reports it (CS2 values seen: `CTWin`, `BombDefused`, `TerroristsWin`, `TargetBombed`, `TargetSaved`); `winner_side` is `CT` or `T` for CS2. - A valid match whose maps have not been played, and an unknown id, both return an empty `games` list. The response is cached for up to ten minutes.
Herramienta MCP bo3_match_games
x-api-key:headermatch_id:query
GETapiKeyexample
/bo3/match-historyBO3.gg esports match history
Returns BO3.gg's esports match history for one game, newest first by default, with paging and filters: `status` (`finished`, `defwin`, `upcoming`, `current`, `canceled`, `postponed`; the default is finished and default-win matches together), `tier` (`s` to `d`), an inclusive `from`/`to` day range (UTC), `sort` and `offset`/`limit` (up to 100 per page). Each match has teams, scores, winner, best-of, tournament, maps and the site's AI prediction; `total` and `has_more` page through the full history.
Notas de la respuesta
- `total` is the number of matches that fit the filters (for example more than 76,000 finished CS2 matches) and `has_more` says whether another page exists; step `offset` by `limit` to page. - Match `status` is one of `upcoming`, `current` (live), `finished`, `defwin` (default win), `canceled` or `postponed`; `tier` is `s`, `a`, `b`, `c` or `d`; each map `status` is `upcoming`, `current` or `finished`. - An invalid `tier`, `status`, game, date or page size returns `400`; the upstream treats an unknown tier as an empty list, so the service rejects it instead. The response is cached for up to two minutes.
Herramienta MCP bo3_match_history
x-api-key:headergame:querystatus:query+6 más
APIs relacionadas
Más cobertura de deportes y juegos
Sports & Gaming
FanDuel Sportsbook
Browse public sports and event data from FanDuel Sportsbook. Discover market-specific event types, follow a league or schedule, and read the markets and prices FanDuel publishes for that event and market.
Sports & Gaming
FanDuel Racing
Follow public horse-racing cards across tracks and countries. Discover today's tracks, inspect races and runners, and read official results, wager-type reference data, and published pool information without placing a wager.
Sports & Gaming
FanDuel Research
Explore FanDuel Research's public editorial and sports-data surfaces. Discover sport slugs and teams, read articles and player updates, inspect live fixtures, and retrieve the published projection tables with their source-specific slate identifiers.
Cómo hacer scraping de BO3.gg
Extrae datos de BO3.gg en 13 pasos
BO3.gg describes itself as an esports and gaming platform spanning CS2, VALORANT, Dota 2, League of Legends, Rainbow Six Siege, and Mobile Legends. Its site combines match and tournament data with news, guides, analysis, wiki pages, predictions, and game-specific forums; its own methodology says analysts review material and sources can include tournament organizers, official APIs, and gaming communities. The 28 production-published routes cover match/tournament lists and details, maps and rounds, transfer metadata, editorial/forum indexes, player/team records, recent-form pages, tournament map pools and squads, economy baselines, leaderboards, and team rankings. The editorial feed also accepts 16 locale choices; its game-review section applies only to the general `games` feed. An English review probe returned one record on 2026-10-30; a Japanese review request returned HTTP 503, so non-English availability remains unverified. Keep category IDs from their matching directories and reuse returned slugs and numeric IDs. Recent team/player match pages return at most 30 newest matches without date paging; team prize money counts tournaments by end date. Forum routes expose thread metadata, not user posts/replies. BO3's team-ranking dates distinguish Valve-published rankings from its own daily estimates.
- Paso 1
Choose documented match filters
/bo3/match-history accepts game values cs2, valorant, lol, dota2, r6siege, and mlbb; status values finished, defwin, upcoming, and current; and tiers s through d. Use from/to as inclusive UTC day filters, then follow offset and has_more with a limit no greater than 100. Site navigation labels are not extra API parameters.
- Paso 2
Filter tournament lists with supported fields
/bo3/tournaments accepts game, current/upcoming/finished status, tier s through d, LAN/online event type, sort, and offset/limit. It has no date, name, or country filter; narrow with documented options, save the returned slug, and use has_more rather than inventing pagination values.
- Paso 3
Page editorial records by section and locale
Call /bo3/news-categories first and use an exact returned category id with /bo3/news-feed. The feed accepts game, `section=news|article|wiki|predictions|reviews`, `locale` from 16 supported languages, an optional `tag` copied from a returned item's tags, newest/oldest sort, and offset/limit up to 100. To retrieve reviews, set `section=reviews` and `game=games`; category and section are independent. English reviews returned one record in a 2026-10-30 live probe. A Japanese review request returned HTTP 503 and its retry ended in a TLS error, so test each non-English locale before relying on it. Returned authors are source bylines, not profile links; the feed exposes record metadata and URLs, not full article bodies.
- Paso 4
Index forum categories without collecting posts
Call /bo3/forum-categories for the chosen game, then pass an exact category id to /bo3/forum with activity, newest, comments, or rating sort and a page offset. Some games have no forum and return no threads. Responses contain titles, authors, and counts, but no user-written posts or replies; treat those as a deliberate coverage boundary.
- Paso 5
Follow list results to detail routes
Use /bo3/match-history slugs with /bo3/match for maps, scores, streams, and prediction; match lineups are separate at /bo3/match-players. Use a slug from /bo3/tournaments with /bo3/tournament. Team and player slugs from rankings, rosters, or leaderboard rows open /bo3/team and /bo3/player. Pass game explicitly for non-CS2 detail because many routes default to CS2.
- Paso 6
Retrieve maps, rounds, and tournament stages
/bo3/match-games requires the numeric match_id from a match-history row; it returns map and round outcomes. A valid match with no played maps can return an empty games list, so do not treat that as a failed lookup. /bo3/tournament-stages needs the tournament slug from /bo3/tournaments and returns stages ordered by sequence.
- Paso 7
Carry source slugs into statistics and records
Reuse a match slug from /bo3/match-history with /bo3/match-players. Player and team stats require their own returned slugs, with general, maps, accuracy, advanced, economy, or map-pool views. /bo3/records is CS2-only, accepts match/tournament/team/player slugs and an open record_type set; reuse the types returned in the response because there is no directory route. The player leaderboard is CS2-only and pages by next_offset; its minimum-games threshold changes with the date window.
- Paso 8
Keep CS2 and VALORANT leaderboard scope separate
/bo3/player-leaderboard covers CS2; /bo3/valorant-leaderboard covers VALORANT. Both accept UTC day windows, sort and order, and offset/limit pages, but each has a moving minimum-games threshold. The Valorant leaderboard has no tier filter, and its player slug is not interchangeable with a CS2 player slug.
- Paso 9
Filter transfer and MVP records with returned identifiers
/bo3/transfers has no game filter: use action/role or returned team_id/player_id and preserve the row's game. /bo3/tournament-mvps returns award, tournament, player, team, and article_url metadata; the linked story body is outside this endpoint.
- Paso 10
Interpret team prize money by tournament end date
/bo3/team-prize-money sums teams' tournament earnings when the tournament ended inside the requested from/to UTC day window; it defaults to the recent six months. It has no region or country filter. Preserve the date range and do not equate this team-window total with the career prize value on each returned player.
- Paso 11
Read recent form and event-specific map data
/bo3/team-recent-matches and /bo3/player-recent-matches accept returned team/player slugs plus optional opponent or tournament filters, but cap at 30 newest matches and have no date cursor. `/bo3/tournament-map-pool` and `/bo3/tournament-squads` require a CS2 tournament slug; the economy baseline is a site-wide buy-level matrix, not a per-team history.
- Paso 12
Separate official rankings from site rankings
Call /bo3/team-ranking-dates for the game's published ranking dates and supported region labels before requesting /bo3/team-rankings. A listed Valve publication date is marked official with source valve_official; a different date yields BO3.gg's internal daily ranking. Preserve date, region, source, and official flags rather than combining these series as equivalent observations.
- Paso 13
Respect editorial ownership and scope
BO3.gg's Use of Services names DINAH HOLDINGS LIMITED as the content rights holder and reserves the right to remove user materials. Treat the feed as editorial metadata and structured data access, not a license to reproduce article bodies or forum content; there is no author-profile or arbitrary byline-search route.
Preguntas frecuentes
Scraping de BO3.gg: preguntas frecuentes
Can I retrieve every BO3.gg match or tournament in one response?
No. Both lists are paged with offset and limit, capped at 100 per response. Follow has_more and retain the returned total with each dated snapshot.
How do I find a valid match slug?
Start with /bo3/match-history and reuse a slug from a returned match row with /bo3/match-players. Do not substitute a guessed team or event name.
How do I call a BO3.gg detail route?
Reuse a match slug from match history, a tournament slug from tournaments, and team or player slugs from returned rosters, rankings, or leaderboard rows. Pass the matching game when needed; no IDs or slugs should be invented.
Can I filter the transfer feed by game?
No. BO3.gg ignores discipline filters on this feed. Use the returned game field and filter by a team_id or player_id that you obtained from another BO3.gg response.
Does BO3.gg expose one leaderboard for every game?
No. CS2 and VALORANT have separate leaderboard routes and stat fields; each uses its own source scope and minimum-games threshold. The CS2 route has no game parameter, and the Valorant route has no tier filter.
Are all dates in team rankings official Valve rankings?
No. Dates listed by /bo3/team-ranking-dates map to Valve's official ranking and are labeled accordingly. Other dates use BO3.gg's internal daily ranking, so retain source and official metadata.
Does the editorial feed return full articles or author profiles?
No. It returns paged news, article, wiki, or prediction records with categories, bylines, dates, and public URLs; it does not extract full bodies or provide author-profile or byline-search routes.
Can I read full stories from the editorial feed?
No. The feed returns section and category records, byline metadata, dates, and public URLs. It does not return full article bodies or expose author profiles; follow only the documented feed and keep publisher ownership context attached to any reuse.
How do I request BO3.gg game reviews?
Use /bo3/news-feed with `section=reviews` and `game=games`. The review section is separate from the esports news feed; choose a supported locale and retain the returned category, byline, date, and URL metadata.
Are all 16 BO3.gg review locales verified?
No. The English review section returned a record in a production probe, but a Japanese request returned HTTP 503 and its retry ended in a TLS error. Treat non-English review availability as unverified until a successful response for that locale is observed.
Does the forum endpoint include user posts and replies?
No. It lists thread metadata and activity counts only. Use the returned game and category values to filter that index, and do not represent it as a forum-content or reply API.