What this release added
Public API Tracking Data Message retrieval with associated interface control document support
Optional image-chip retrieval for supported tracks
Supporting OpenAPI/schema updates
TLE Alpha-5 egress support
Extended numeric NORAD ID support across orders, API responses, and Portal search
Highlights by area
Public API tracking-data retrieval
The Public API now supports a track-centric workflow for Tracking Data Messages. Developers can search for tracks for a known object over a bounded completion window, then retrieve a raw KVN TDM with ICD content, and optionally request image chips when available for the track.
Track discovery: search by Slingshot object ID or NORAD ID over a completion time window
TDM retrieval: retrieve one track’s TDM export with ICD included by default
Optional image chips: request encoded chip payloads separately when observation type supports them
Extended NORAD support
Portal and API surfaces were updated to support canonical numeric NORAD identifiers beyond the historical five-digit assumption. This affects search, orders, and API request handling, while keeping customer-facing identifiers numeric rather than Alpha-5 text.
Orders: Marketplace and order APIs now support six- to nine-digit numeric NORAD IDs
Search: Data Suite, DST, and Anomaly Analytics searches accept extended numeric NORAD values
TLE generation: Alpha-5 encoding is applied on TLE output where required by the ID range, while OMM and API-facing identity remain numeric