Slingshot Portal
1.1.0
Latest July 15, 2026
Observation tracks and TDM exports
Adds Space Object Catalog observation-track discovery and per-track export products. Clients search tracks for a space object or NORAD ID over a completion time window, then retrieve a CCSDS TDM (KVN) with ICD, or encoded image chips, as separate exports. Also updates published SPU prices for catalog TLE and predicted-ephemeris endpoints.
Added
Space Object Catalog — search observation tracks for one object by spaceObjectId or noradId over a completedFrom / completedTo window (completedTo defaults to current UTC).
GET /v1/catalog/tracksSpace Object Catalog — export a track as a raw CCSDS Tracking Data Message (TDM) in KVN text, including ICD content.
GET /v1/catalog/tracks/{trackId}/exports/tdmSpace Object Catalog — export encoded image chips for a track (base64 + zlib, 32 by 32). Returns 404 when image chips are not available for the track.
GET /v1/catalog/tracks/{trackId}/exports/image-chips
Changed
Space Object Catalog OpenAPI document version bumped from 1.0.0 to 1.1.0.
API cost matrix — published SPU prices for track search (0.001), TDM export (9.475284), and image-chip export (3.158428 per trackId); updated latest TLE and day TLE to 9.949048; updated predicted ephemeris to 10.422812.
GET /v1/catalog/tracks``GET /v1/catalog/tracks/{trackId}/exports/tdm``GET /v1/catalog/tracks/{trackId}/exports/image-chips``GET /v1/catalog/tle/{spaceObjectId}/-latest-``GET /v1/catalog/tle/{spaceObjectId}``GET /v1/catalog/ephemeris/predicted/{spaceObjectId}
Added
- MCP tool registry — list_tracks, get_track_tdm_export, and get_track_image_chips_export added for the new catalog observation-track operations.
1.0.0
April 14, 2026
General Availability
First production release of the Slingshot Developer Suite customer-facing APIs and documentation toolchain: Space Object Catalog (list summaries, TLE, predicted ephemeris), Space Contextual Data (Seradata) across spacecraft and subsystem domains, daily out-of-family analytics for LEO/GEO cohorts, marketplace order history, and OpenAPI 3.1 specifications with cursor-based list pagination and a standardized JSON error envelope. The developer portal includes Key Management (API keys via internal APIs), docs, and status; additional catalog (TDM), analytics, marketplace, and GSN tracking routes remain marked Coming Soon in the specs where applicable. A GSN Tracking OpenAPI document is published as an implementation preview.
Added
Space Object Catalog — paginated list of space object summaries with optional filters (noradIds as comma-separated NORAD IDs, objectType, cursor, limit).
GET /v1/catalogSpace Object Catalog — latest mean-elements TLE for a space object (Slingshot spaceObjectId).
GET /v1/catalog/tle/{spaceObjectId}/-latest-Space Object Catalog — all TLEs for a single UTC calendar day for a space object.
GET /v1/catalog/tle/{spaceObjectId}Space Object Catalog — predicted ephemeris (OCM) for a space object.
GET /v1/catalog/ephemeris/predicted/{spaceObjectId}Space Contextual Data (Seradata) — list and detail endpoints for spacecraft, rocket bodies, debris, countries, companies, launch sites and vehicles, launches, engines, power and comms subsystems, events, and typed payloads (44 routes in OpenAPI).
GET /v1/contextual/antennas``GET /v1/contextual/antennas/{antennaId}``GET /v1/contextual/batteries``GET /v1/contextual/batteries/{batteryId}``GET /v1/contextual/companies``GET /v1/contextual/companies/{companyId}``GET /v1/contextual/countries``GET /v1/contextual/countries/{countryId}``GET /v1/contextual/debris``GET /v1/contextual/debris/{spaceObjectId}``GET /v1/contextual/engines``GET /v1/contextual/engines/{engineId}``GET /v1/contextual/events``GET /v1/contextual/events/{eventId}``GET /v1/contextual/launch/sites``GET /v1/contextual/launch/sites/{launchSiteId}``GET /v1/contextual/launch/vehicles``GET /v1/contextual/launch/vehicles/stages``GET /v1/contextual/launch/vehicles/{launchVehicleId}/spec``GET /v1/contextual/launch/vehicles/{launchVehicleId}/stages``GET /v1/contextual/launches``GET /v1/contextual/launches/{launchId}``GET /v1/contextual/payloads/communication``GET /v1/contextual/payloads/communication/{communicationPayloadId}``GET /v1/contextual/payloads/early-warning``GET /v1/contextual/payloads/early-warning/{earlyWarningPayloadId}``GET /v1/contextual/payloads/navigation``GET /v1/contextual/payloads/navigation/{navigationPayloadId}``GET /v1/contextual/payloads/optical``GET /v1/contextual/payloads/optical/{opticalPayloadId}``GET /v1/contextual/payloads/radar``GET /v1/contextual/payloads/radar/{radarPayloadId}``GET /v1/contextual/payloads/scientific-or-other``GET /v1/contextual/payloads/scientific-or-other/{scientificOrOtherPayloadId}``GET /v1/contextual/payloads/sigint``GET /v1/contextual/payloads/sigint/{sigintPayloadId}``GET /v1/contextual/rocket-body``GET /v1/contextual/rocket-body/{spaceObjectId}``GET /v1/contextual/solar-arrays``GET /v1/contextual/solar-arrays/{solarArrayId}``GET /v1/contextual/spacecraft``GET /v1/contextual/spacecraft/{spaceObjectId}``GET /v1/contextual/spacecraft/{spaceObjectId}/aliases``GET /v1/contextual/thrustersSpace Object Analytics — daily out-of-family (cohort) anomaly snapshot per orbit regime, with optional comma-separated noradIds filter.
GET /v1/analytics/anomalies/outOfFamily/reportMarketplace — paginated list of the authenticated account’s orders (sort by requestedOn descending; optional orderStatusName filter).
GET /v1/marketplace/ordersOpenAPI 3.1 specifications published for GA customer-facing routes (catalog, contextual, analytics, marketplace), plus companion tracking and Coming Soon operations where documented.
Cursor-based list pagination across list endpoints: data array with page object (limit, nextCursor).
URL-path API versioning (/v1/...) with documented minimum deprecation notice for future versions.
Bearer API key authentication (Authorization: Bearer).
Standard JSON error envelope: root error object with code, message, request_id, timestamp, and optional structured details for rate limits and billing.
Developer portal Key Management experience (create, rotate, revoke API keys; usage and audit views via internal APIs — not part of the public REST surface in these specs).
Machine-readable developer guides: API cost matrix (SPU), MCP tool registry, and workflow scenarios aligned to the OpenAPI specs.
The beginning — project inception.