Home/Guides/Data Hub

Baseball and softball webhook field names

The field names ScoreCastr reads from a baseball or softball webhook or Scoreboard OCR feed, the value formats it accepts, and what each one changes on the dashboard and scorebug.

Updated 4 min readPro

A baseball or softball scorebug carries a lot of state: the inning, the count, the outs and who's on base. If Scoreboard OCR or another program already has it, it can send it to ScoreCastr. Baseball and softball use the same field names. This page lists them, the formats they take and what each one changes.

Short versionPOST a JSON body to your match's Webhook URL with fields like away_score, home_score, inning, inning_half, balls, strikes, outs and runner_on_first. Send runners as true or false. Needs the Pro plan.

Before you start

  • The Pro plan. The ScoreCastr button on the baseball or softball Scoring tab opens the Data Hub.
  • A webhook turned on for the match: on the Scoreboard OCR tab, pick HTTP Client (Webhooks), click Enable ScoreCastr and copy the Webhook URL. See Send live data by webhook.
  • Scoreboard OCR users: see Connect Scoreboard OCR. Request format and replies: Webhook API reference.

Away means the away team from match setup (batting in the top of the inning); home is the home team. Field names are case sensitive. Send only what changed if you like; anything left out keeps its value.

Score, inning and count

Field names What it changes Format
away_score, awayScore, away_runs, awayRuns Away runs Number
home_score, homeScore, home_runs, homeRuns Home runs Number
inning, currentInning, current_inning Inning A number from 1 up
inning_half, inningHalf, half Top or bottom top or t; bottom, bot or b
balls Balls 0 to 4
strikes Strikes 0 to 3
outs Outs 0 to 3
runner_on_first, runnerOnFirst, first, base1 Runner on first true or false
runner_on_second, runnerOnSecond, second, base2 Runner on second true or false
runner_on_third, runnerOnThird, third, base3 Runner on third true or false
away_hits, awayHits Away hits Number
home_hits, homeHits Home hits Number
away_errors, awayErrors Away errors Number
home_errors, homeErrors Home errors Number

A count or out number outside its range is ignored, so a bad read can't put 5 balls on screen.

Watch outA runner is on base only when the value is true, the text "true" or the number 1. Anything else, including the text "1" or "yes", clears the base. A runner field you leave out keeps its value, so send all three each time to stay in step.

Pitcher, batter and team stats

Replace away_ with home_ for the home team. The away pitcher is the one throwing in the bottom of the inning.

Field name (away) What it changes
away_pitcher_name Away pitcher's name (text)
away_pitch_count Away pitcher's Pitches
away_ball_count Away pitcher's Balls Thrown
away_strike_count Away pitcher's Strikes Thrown
away_strikeouts Away pitcher's Strikeouts
away_walks Away pitcher's walks
away_batter_name Away batter's name (text)
away_lob Away runners left on base

The pitcher name and the four counters fill the PITCHING card and the pitcher bar. See Pitcher stats. These fields must use the snake_case names above, and number values that aren't numbers are skipped.

Example body

{
  "away_score": 2,
  "home_score": 3,
  "inning": 6,
  "inning_half": "bottom",
  "balls": 2,
  "strikes": 1,
  "outs": 1,
  "runner_on_first": true,
  "runner_on_second": false,
  "runner_on_third": true,
  "away_hits": 5,
  "home_hits": 7,
  "away_errors": 1,
  "home_errors": 0,
  "away_pitch_count": 84
}

What the scorebug does on its own

When a team's runs and hits both go up by one in the same update and the outs don't change, ScoreCastr reads it as a home run and plays the home run animation.

It skips this on the update where balls, strikes and outs all go back to 0 from a live count, because that's usually the end of a half inning and the totals can jump. A single that drives in one run, with no out on the play, looks the same to ScoreCastr and also plays it. Send the score and hits as running totals.

Fix common problems

Runners show on the wrong bases. Send each runner as true or false, not "1" or "yes", and send all three.

The count won't move past a value. Balls go up to 4, strikes and outs up to 3. Higher numbers are ignored.

The inning shows top all game. Send inning_half as top or bottom (t, bot and b work too).

Nothing changes at all. Check the names letter for letter and that the match's method is HTTP. See the Webhook API reference.

Checklist

  • Pro plan, webhook enabled with HTTP Client (Webhooks)
  • Inning as a number and inning_half as top or bottom
  • Count and outs within range
  • All three runners sent as true or false
  • Runs and hits sent as running totals
  • Pitcher names set for both teams