MLB 2026 Season Changes
MLB Coverage Switch
We are introducing a new event to enhance your ability to react to changes in our MLB data coverage, particularly concerning the quality of our data feed. This update is crucial for customers managing markets based on player data, where timely information about data source changes is paramount for appropriate market closure.
What's New?
We will be adding a new event with ID 2400, named "MLB Coverage change." This event will include an extrainfo parameter:
extrainfo=0: Indicates a switch to a secondary data source, signifying a decreased quality of the feed.
To start receiving the "MLB Coverage change" event (ID 2400), you will need to enable the following configuration:
Config: Include coverage switch event (ID 243)
Please ensure this configuration is enabled in your system to benefit from these critical notifications.
We recommend enabling this configuration as soon as possible to ensure you receive these important updates and can take appropriate action for your MLB markets.
If you have any questions or require assistance with enabling the configuration, please do not hesitate to contact our support team.
ABS Challenge System
Starting with the 2026 season, Major League Baseball introduced the ABS Challenge System, which allows teams to challenge ball and strike calls made by the home plate umpire. The umpire still makes the initial decision, but certain players on the field can request a review if they believe the call was incorrect.
Both teams start the game with two challenges each. Only the batter, pitcher, or catcher can initiate a challenge, and it must be done immediately after the pitch without assistance from the dugout. If the challenge is successful, the team keeps its challenge.
When a challenge is made, the Automatic Ball-Strike System uses pitch-tracking technology to determine whether the pitch passed through the strike zone. The result is shown shortly after, and the original call is either confirmed or overturned.
Betstop - Timeout would be triggered and the Timeout event (1035) sent when an ABS challenge is initiated.
If the decision is overturned, a Stats Correction event (1832) would be sent to update the counts and the game would return to betstart.
If the original call is confirmed, Timeout Over (1047) would be sent and the game would return to betstart.
Player Out - Base Info for Stretching Out
This update adds more granular detail to specific "Player Out" events classified as "stretching" outs by indicating the last base safely reached by the batter-runner. To clarify the impact, please see the examples below for the config Include baseinfo attribute for stretching outs (ID 246):
1. Config Disabled (Current Behavior): The 2149 event for a "stretching" out will not include the baseinfo attribute.
2. Config Enabled (New Behavior): The 2149 event for a "stretching" out (where extrainfo="46") will now include the baseinfo attribute. In the example below, baseinfo="0:1" indicates the runner was out while attempting to reach second base, having safely cleared first.
Last updated
Was this helpful?