Teams, Players & Rosters

Dated roster registrations

NPB-only. npb.jp's 出場選手登録 (top-team active roster) as of each date, from npb.jp/announcement/roster/roster_MMDD.html, one doc per date (date, YYYY-MM-DD). players are the registered players and transactions that day's moves (action: registered or removed); each entry carries officialId (the 8-digit npb.jp player id), playerId (null when the id is not yet mapped), name as printed, teamCode / teamId, position (投手, 捕手, 内野手, 外野手) and jersey. A list is stored only when it reads as all twelve clubs. Written by npb_official:roster-registrations every six hours; the publication hour is not known, so a game's registration is the prior day's list.

Requires the stats entitlement (a paid plan). See Responses & Errors for the success envelope and availability rules.

GEThttps://api.sportquanta.com/v1/npb/roster-registrations

Reference context: NPB.

Overview · Response conventions

curl --request GET \
  --url 'https://api.sportquanta.com/v1/npb/roster-registrations?season=1946' \
  --header 'Authorization: Bearer <token>'

{
  "data": {
    "season": 0,
    "items": [
      {}
    ]
  },
  "_meta": {
    "request_id": "REQUEST_ID",
    "served_from": "live",
    "cache_ttl_seconds": 300
  }
}

Authorizations

Authorizationstringheaderrequired

Send a workspace API token in the Authorization: Bearer <token> header.

Query Parameters

seasonintegerrequired

Season (calendar year).

Required range: 1946 <= x, x <= 2100

datestring

One list's date, YYYY-MM-DD.

limitintegerdefault:200

Required range: 1 <= x, x <= 2000

provenancebooleandefault:false

Opt in to per-field provenance on supported single game, match, team, player, and venue reads. Lists and composites accept the flag but generally omit provenance. It is returned under _meta.provenance only when source metadata exists.

Response

application/json

Every stored list for the season that matches the filters, by date.

dataobjectrequired

data.seasonintegerrequired

data.itemsobject[]required

_metaobject

Response request/cache metadata. Optional evidence fields are specific to this handler; cache TTL does not measure source-data freshness.

_meta.request_idstring

_meta.served_fromenum<string>

Available options: live, cache

_meta.cache_ttl_secondsinteger

Response cache TTL; independent of source freshness. Omitted when zero.