---
title: "Head-to-head intelligence vs one opponent"
method: GET
path: "/v1/teams/{id}/h2h-intelligence"
tags: ["teams"]
---

# Head-to-head intelligence vs one opponent

`GET /v1/teams/{id}/h2h-intelligence`

## Request

- Base URL: `https://api.bigballsdata.com`
- URL: `https://api.bigballsdata.com/v1/teams/{id}/h2h-intelligence`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Head-to-head record and betting context against a specific opponent, including a trailing-365-day record, revenge context, cover/over rates and the last 3 meetings. **Solo plan or higher**: head-to-head intelligence starts at Solo; Free receives a 403 naming the tier and linking the docs and pricing pages.

## Path parameters

- `id` string, uuid, required: A stored BigBalls id. This is the identifier every match, team, player and league endpoint returns, and the one every `{id}` path segment accepts. Take it from the `id` field of the corresponding list endpoint and use it as-is.

## Query parameters

- `opponent_id` string, uuid, required

## Response `200`

ok. `{ data }` with h2h_record, h2h_last_365_days, revenge_factor, revenge_context, h2h_cover_rate, h2h_over_rate and last_3_meetings. No meta/error wrapper.

- object
  - `data` object, required
    - `team_id` string, uuid
    - `opponent_id` string, uuid
    - `h2h_record` object
    - `h2h_last_365_days` object
    - `last_3_meetings` object[]

## Other responses

- `400`: Invalid team id, missing ?opponent_id=, or opponent_id equal to the team id.
- `403`: plan_required (Solo or higher)

---

[API](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api.md) · [All operations](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/revisions/31fb54ac414e?raw)