The team-level counterpart to player research: one directory across every title, one stable kr_tm_* id per team, and the context a preview or model actually needs — form, roster, maps, H2H and main lines.
A real directory hit — 8,424 CS2 teams behind one stable id space.
Attach only what you need: include=form for recent results, roster for the lineup, maps for the map pool and win rates, main_lines for moneyline open/close per book. Pass team1+team2 for a head-to-head.
{
"available": true,
"sport": "cs2",
"total": 8424,
"teams": [
{
"canonical_team_id": "kr_tm_b349f7d0bab9",
"name": "mens",
"slug": "mens",
"rank": null
}
]
}Recent results plus upcoming fixtures on the same team object.
The current lineup and per-map win rates for CS2, Valorant and the map-based titles.
Moneyline open/close per book, record against the close, and direct head-to-head.
A team directory keyed by stable kr_tm_* ids. Search by name with q= or fetch one team by id=, then attach what you need with include=: recent form, current roster, map pool and map win rates, head-to-head, upcoming fixtures, and main lines (moneyline open/close per book plus record against the closing line).
Pass team1= and team2= together — the response returns the meeting history and shared context for the pair. Each team can be a kr_tm_* id or a slug.
include=main_lines attaches the team's moneyline history per book — open, close, and how the team performed against the closing line — on the same schema as /lines.
Yes. A team has one kr_tm_* id no matter how an upstream source spells or orders the name — the same id you get back from /v7/{sport}/matches.
Teams is on Hobby and above — from $29/mo. Player-level research on the same key is in /v7/{sport}/players.
