Skip to main content
GET
Get schedule detail
Only scheduleId is required. The schedule must belong to a team in the API key organization. When teamTwoId is set on the schedule, the response looks up that team (same pattern as teamOneId) so you get an object with at least _id and name, not only a bare id string.

Scores

  • teamOneScore / teamTwoScore — final (or live running) game totals on the schedule.
  • matchupFormat — quarters, halves, or runningClock (default on create is often halves).
  • scoreBreakdown — period breakdown derived from scoring plays (points + clockStage), same layout as the Post Game Summary email:
scoreBreakdown.teamOne.final / scoreBreakdown.teamTwo.final always mirror teamOneScore / teamTwoScore. Period sums can be lower than final when OT (quarters) or plays lack clockStage — treat final as authoritative. Example (matchupFormat: "quarters"):
The same scoreBreakdown object is also available under data.meta on Get schedule player statistics.

Authorizations

Authorization
string
header
required

Public integration API key (bb_live_...). Not a login JWT.

Path Parameters

scheduleId
string
required

Schedule document Mongo _id from create or list.

Example:

"507f1f77bcf86cd799439012"

Response

Schedule detail

teamOneScore
number
teamTwoScore
number
matchupFormat
enum<string>
Available options:
halves,
quarters,
runningClock
scoreBreakdown
object

Period breakdown by matchupFormat (same rules as Post Game Summary email). final mirrors teamOneScore/teamTwoScore.