Changelog

[0.2.0-alpha] - 2026-01-09

Added

• New Possession Touches data set

[0.1.0-alpha] - 2026-01-08

Added

• Initial creation of the CTG Pro Data Feed API documentation
• New is_live_ball_rebound field on Rebounds data set - Indicates whether the rebound was secured as a live ball (not a team rebound or out of bounds). This is a clearer name for what was previously is_rebounded
• New offense_players and defense_players fields on Chances data set - Arrays of NBA player IDs for the five players on offense and defense during each chance
• New context and outcome fields on Chances data set - in_garbage_time (indicates if chance occurred during garbage time), shot_location (court zone where shot was taken), is_shot_made, is_shot_blocked, is_shooter_fouled, and led_to_offensive_rebound (shot outcome indicators)
• New statistical fields on Chances data set - fga_pts (points scored on field goal attempt), fgm, fga, ftm, fta, tov, fg_dreb, and fg_oreb (four factors and basic statistics)
• Standardized field names across markings data sets for consistency:
  • New game_id_nba field on Passes, Deflections, Dribbles, Contested Rebound Touches, Anthro Measurements, Free Throws, Falls - Consistent NBA game ID naming
  • New player_id_nba field on Dribbles, Contested Rebound Touches, Anthro Measurements, Free Throws, Falls - Consistent NBA player ID naming
  • New passer_id_nba and intended_receiver_id_nba fields on Passes - Correct suffix for NBA player IDs
  • New def_player_id_nba and off_player_id_nba fields on Deflections - Added missing _nba suffix
  • New pbp_event_id field on Shots, Jump Shots, Jump Shot Contests, Interior Shots, Interior Shot Contests, Rebounds, Fouls, Turnovers - Consistent PBP event ID naming
  • New set_point_he_frame, last_ball_in_hands_he_frame, last_ball_in_hands_wall_clock, first_shooting_wrist_below_eye_after_release_he_frame, first_shooting_wrist_below_eye_after_release_wall_clock, first_non_shooting_wrist_below_eye_after_release_he_frame, first_non_shooting_wrist_below_eye_after_release_wall_clock fields on Free Throws - Aligned naming with Jump Shots
  • New possession_id_ctg field on Chances data set - CTG-generated possession ID that links chances to their parent possession, enabling grouping of chances that belong to the same possession (e.g., after offensive rebounds)

Changed

• New heave option added to chance_outcome on Chances data set - Indicates an official heave

Deprecated

• is_rebounded on Rebounds - Use is_live_ball_rebound instead. The old field name was confusing; the new name better describes the field's purpose
• attacking_positive_x on Rebounds - This information is not particularly accurate and not useful in this data set
• event_pbp_descriptor on Rebounds - This field is always null and provides no value
• event_pbp_qualifiers on Rebounds - This information is redundant with other fields in the response
• attacking_positive_x on Fouls - This information is not particularly accurate and not so useful in this data set
• event_pbp_foul_personal_total on Fouls - This data is already available in the official NBA play-by-play feed
• event_pbp_foul_technical_total on Fouls - This data is already available in the official NBA play-by-play feed
• attacking_positive_x on Turnovers - This information is not particularly accurate and not useful for analyzing turnover events
• event_pbp_descriptor on Turnovers - This information is not particularly useful for analyzing turnover events
• event_pbp_qualifiers on Turnovers - This information is not useful for analyzing turnover events
• event_pbp_turnover_total on Turnovers - This data is already available in the official NBA play-by-play feed
• Deprecated field names replaced by standardized versions (all retain backward compatibility):
  • nba_game_id on Passes, Deflections, Dribbles, Contested Rebound Touches, Anthro Measurements, Free Throws, Falls - Use game_id_nba instead
  • nba_player_id on Dribbles, Contested Rebound Touches, Anthro Measurements, Free Throws, Falls - Use player_id_nba instead
  • passer_id_ctg and intended_receiver_id_ctg on Passes - Use passer_id_nba and intended_receiver_id_nba instead
  • def_player_id and off_player_id on Deflections - Use def_player_id_nba and off_player_id_nba instead
  • event_pbp_id on Shots, Jump Shots, Jump Shot Contests, Interior Shots, Interior Shot Contests, Rebounds, Fouls, Turnovers - Use pbp_event_id instead
  • set_point_frame, release_frame, release_wall_clock, first_frame_shooting_wrist_below_eye, shooting_wrist_below_eye_wall_clock, first_frame_non_shooting_wrist_below_eye, non_shooting_wrist_below_eye_wall_clock on Free Throws - Use standardized names matching Jump Shots
  • game_clock_running on Turnovers - This field is unreliable and not particularly useful for analyzing turnover events
• shot_clock_running on Turnovers - This field is unreliable and not particularly useful for analyzing turnover events
• game_clock_running on Fouls - This field is unreliable and not particularly useful for analyzing foul events
• shot_clock_running on Fouls - This field is unreliable and not particularly useful for analyzing foul events

Format and Versioning

The changelog format is based on Keep a Changelog.

It includes the following types of changes:

• Added - New data sets, fields, or API features
• Changed - Changes to existing data or behavior (may be breaking)
• Deprecated - Features that will be removed in future versions
• Removed - Features that have been removed
• Fixed - Bug fixes in data accuracy or API behavior

The API follows Semantic Versioning (SemVer). Version numbers are formatted as MAJOR.MINOR.PATCH with optional pre-release labels:

Component	When It Changes	Example
MAJOR	Breaking changes that require client updates	1.0.0 → 2.0.0
MINOR	New features added in a backward-compatible way	1.0.0 → 1.1.0
PATCH	Bug fixes that don't change the API contract	1.0.0 → 1.0.1

Pre-release Labels

• alpha - Early development; API may change significantly between releases
• beta - Feature complete; API is stabilizing but may still have minor changes
• rc (release candidate) - Final testing before stable release

Versioning Policy

• 0.x.x versions: The API is in active development. Breaking changes may occur between minor versions. We will notify you before this occurs.
• 1.0.0 and beyond: The API is stable. Breaking changes will only occur in major version bumps, with advance notice in the changelog.