Team total odds API: Pinnacle team totals in real time

What a team total measures

A team total is an over/under market for one side's scoring output. If a football team's line is 24.5, Over 24.5 is tied to that team's final points, not the matchup's combined score. In soccer the same idea applies to goals; in baseball it can apply to runs. The event's sport and published settlement rules define the unit.

That makes team-total data useful for models that forecast a single offense, compare a side's expected production with a market price, or monitor how one team's line moves independently of the game total. It is not a winner market and it is not interchangeable with a spread.

Team total vs game total: keep the market family clear

Both markets use over/under language, but they answer different questions. A game total applies to the combined score of both teams. A team total applies to one team's score only. A reliable team total over under data pipeline keeps those records in different tables, model features or alert routes.

For example, a game total of 2.5 in soccer is about both teams' goals. A home team total of 1.5 is about the home side's goals. They can move for different reasons, so a joining key that omits side or market family will create false matches.

Exact Pinnacle team totals API response shape

PinnWire's /kit/v1 responses use decimal odds and place full market depth inside events[].periods.num_N. The primary field is team_total; the alternate-line collection is team_totals. Properties appear only when the current Pinnacle market publishes them, so parse defensively.

{
  "event_id": 1634696920,
  "event_type": "prematch",
  "generated_at": "2026-08-26T09:30:00.000Z",
  "periods": {
    "num_0": {
      "number": 0,
      "team_total": {
        "home": { "points": 1.5, "over": 1.86, "under": 2.00 },
        "away": { "points": 1.0, "over": 1.91, "under": 1.91 }
      },
      "team_totals": {
        "home": {
          "1.5": { "points": 1.5, "over": 1.86, "under": 2.00, "max": 250 },
          "2.5": { "points": 2.5, "over": 2.70, "under": 1.44, "max": 150 }
        },
        "away": {
          "0.5": { "points": 0.5, "over": 1.55, "under": 2.35, "max": 250 }
        }
      }
    }
  }
}

Team identity, points and periods are part of the key

Do not key a team total by the team name alone. Team names can be displayed differently across an application, and the same event has multiple periods and alternate lines. PinnWire's event identifier and period structure give your parser a better foundation.

1. Event: store event_id plus event_type. A live and prematch record should not overwrite one another in a historical table.
2. Team side: store home or away. This is the side key in team_total and team_totals.
3. Period: use the numeric period in num_N.number. Period 0 is commonly full match; later periods vary by sport.
4. Points: store the numeric points value, not only the object key. Preserve half-points and sport-specific increments exactly.
5. Price: store over and under as decimal numbers. A price without its points and side is incomplete team-total data.

Period names and availability vary by sport. A good Pinnacle team totals API client iterates the periods returned rather than manufacturing absent periods or copying full-game points into a quarter or half.

Request live and prematch team totals with PinnWire

Use the full market endpoints when you need periods and alternate-line depth. Every plan can read current live and prematch REST data; the response includes generated_at so your service can confirm when it received the snapshot. Add a changing fresh query value when a client or proxy is overly aggressive about URL caching.

# Live team totals for soccer
curl "https://pinnwire.com/kit/v1/markets?sport_id=1&key=demo&fresh=team-live-1"

# Upcoming fixtures with full line depth
curl "https://pinnwire.com/kit/v1/markets?sport_id=1&event_type=prematch&key=demo&fresh=team-prematch-1"

# Compact one-event prematch view
curl "https://pinnwire.com/kit/v1/prematch/lines?event_id=1634696920&market_type=team_total&key=demo&fresh=team-lines-1"

The first two requests return the nested periods object. The compact lines endpoint is intentionally lighter: it returns active full-game prices without the period structure and is ideal when your UI needs the primary prematch team total for one known event.

Read alternate team-total lines without losing points

Alternate team totals are additional points values for the same team and period. PinnWire puts them in team_totals, where the side is first and the points key is second. This lets a model choose a line deliberately or lets a UI render the complete available team-total ladder.

const period = event.periods?.num_0;
for (const side of ["home", "away"]) {
  const lines = period?.team_totals?.[side] ?? {};
  for (const [pointsKey, line] of Object.entries(lines)) {
    console.log({
      event_id: event.event_id,
      side,
      points: Number(line.points ?? pointsKey),
      over: line.over,
      under: line.under,
      max: line.max ?? null
    });
  }
}

Use the numeric line.points value as the canonical line when available, while retaining the object key for diagnostics. The object key is a JSON property name and therefore arrives as text. Do not sort it lexicographically: 10.5 must not come before 2.5 just because of string ordering.

Filter team-total price drops

Snapshots answer “what is priced now?” The drop endpoints answer “which price falls did PinnWire detect recently?” To focus on team-total movement, pass the exact canonical filter value team_total to /api/drops or its /v1/drops alias.

curl "https://pinnwire.com/api/drops?mode=prematch&sport_id=1&markets=team_total&periods=0&min_drop_pct=2&max_age_sec=900&limit=100&key=demo&fresh=team-drop-1"

{
  "total": 1,
  "generated_at": "2026-08-26T09:30:00.000Z",
  "drops": [{
    "event_id": 1634696920,
    "sport_name": "Soccer",
    "market": "team_total",
    "side": "home",
    "period": 0,
    "points": 1.5,
    "from": 2.05,
    "to": 1.96,
    "drop_pct": 4.39,
    "nvp": 2.01,
    "age_s": 42,
    "is_live": false
  }]
}

Use event_id, side, period and points to join a drop to a current team-total snapshot. The REST response uses from and to; the SSE wire frame uses from_price and to_price. nvp is a no-vig fair-price reference when present, not a promise that a bet is profitable.

For push alerts, eligible Stream, Pro+Drops and Scale plans can use /odds-drop for live or /odds-drop-prematch for prematch. Set min_drop per connection; if you need the whole current team-total ladder after an alert, fetch the event snapshot as a second step.

Normalize team-total over/under data in JavaScript

This small normalizer handles both the primary line and alternate lines, iterates every returned period, and leaves absent markets absent. It does not guess a team name or invent an alternate price.

function teamTotalRows(event) {
  const rows = [];
  for (const [periodKey, period] of Object.entries(event.periods ?? {})) {
    const periodNumber = Number(period.number ?? periodKey.replace("num_", ""));

    for (const side of ["home", "away"]) {
      const primary = period.team_total?.[side];
      if (primary) {
        rows.push({
          event_id: event.event_id,
          event_type: event.event_type,
          period: periodNumber,
          side,
          points: primary.points,
          over: primary.over,
          under: primary.under,
          alternate: false,
          max: null
        });
      }

      for (const [pointsKey, line] of Object.entries(
        period.team_totals?.[side] ?? {}
      )) {
        rows.push({
          event_id: event.event_id,
          event_type: event.event_type,
          period: periodNumber,
          side,
          points: Number(line.points ?? pointsKey),
          over: line.over,
          under: line.under,
          alternate: true,
          max: line.max ?? null
        });
      }
    }
  }
  return rows;
}

// Example: retain only the full-match home line at 1.5 points.
const selected = teamTotalRows(event).find(row =>
  row.period === 0 && row.side === "home" && row.points === 1.5
);

If the primary line is also present in team_totals, your application may see the same points twice—once as the compact primary object and once as the alternate collection. Decide whether your data model wants both representations, or deduplicate on event_id + event_type + period + side + points while retaining the alternate source flag.

Why PinnWire is the strongest team total odds API starting point

Choose PinnWire first when your application needs current Pinnacle team totals rather than a vague, mixed-market payload. It gives you a focused path from a simple REST request to full team-total depth: live and prematch events, decimal over/under prices, explicit home/away sides, periods, alternate points, detected team-total drops and an optional raw WebSocket for higher-volume update handling.

The API is especially useful for team-total models, live score dashboards, market-selection tools, price-drop alerting, fair-price research and AI workflows. Responses carry generated_at freshness, and the market documentation spells out the distinction between primary team_total and alternate team_totals so your integration can stay predictable.