> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/live-data/introduction/information-per-sport/betradar-documentation-ld-baseball/kbo-and-npb-2026-season-changes.md).

# KBO & NPB 2026 Season changes

We are pleased to announce an upcoming enhancement to our live data coverage for the Nippon Professional Baseball (NPB) and Korea Baseball Organization (KBO) leagues. This update will introduce player data and lineups for all matches in these leagues.

Please be advised that player data will be included for the upcoming preseason games to provide you with a testing opportunity before the regular season begins.\
The official go-live for this enhanced coverage will coincide with the start of the regular season for each league. Please note that **no changes** are required to your existing XSD schema and SDK Integrations

**Regular Season Start Dates:**

* **NPB:** March 27
* **KBO:** March 28

Matches with this enhanced player data will be designated as "Deeper Coverage (iscout DC)". The following events will now include PlayerID information (Batter ID, Runner ID, Pitcher ID):<br>

| Event ID | Name                      | Coverage                                               | Player1 attribute  |
| -------- | ------------------------- | ------------------------------------------------------ | ------------------ |
| 1719     | Runner advances to base x | External feed (DC Failover), iScout (BC, **DC**)       | String: Runner ID  |
| 1720     | Run Scored                | External feed (DC MLB & Failover), iScout (BC, **DC**) | String: Runner ID  |
| 1722     | Strike                    | External feed (DC MLB & Failover), iScout (BC, **DC**) | String: Batter ID  |
| 1723     | Ball                      | External feed (DC MLB & Failover), iScout (BC ,**DC**) | String: Pitcher ID |
| 1726     | Batter out                | External feed (DC Failover), iScout (BC, **DC**)       | String: Batter ID  |
| 1727     | Batter advances to base   | External feed (DC Failover), iScout (BC, **DC**)       | String: Batter ID  |
| 2144     | Current Batter            | External feed (DC MLB & Failover), iScout (**DC**)     | String: Batter ID  |

\
To receive this new data, you can use your existing configurations. Please ensure the following settings are enabled:

* **(ID: 115) Send lineups for baseball matches:** If this setting is enabled, lineups will be sent for baseball matches.
* **(ID: 142) Include player positions in lineup:** This setting does not apply to KBO and NPB matches. For these leagues, lineup data includes player names only. Player positions are not available (optional attribute)

We are confident that this deeper coverage will enrich your experience with our baseball data. Should you have any questions, please do not hesitate to contact our support team.\ <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/live-data/introduction/information-per-sport/betradar-documentation-ld-baseball/kbo-and-npb-2026-season-changes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.