Slingshot Portal

Daily Spacecraft Fleet Monitoring

Objective: Monitor a fleet of 50 spacecraft daily: list catalog summaries (each includes lastSeen), then fetch latest TLE only for spacecraft whose lastSeen indicates new data. Run the out-of-family (cohort) check once per UTC day (not on every catalog poll): one GET for the daily snapshot with orbitRegime matching your fleet—step 3 shows LEO; use GEO if your fleet is geosynchronous. Repeat calls the same UTC day for the same regime return the same payload.

Step Endpoint Purpose
1 GET /v1/catalog Daily catalog check including lastSeen for 50 spacecraft (30 days).
2 GET /v1/catalog/tle/{spaceObjectId}/-latest- Latest TLE only for spacecraft whose lastSeen indicates an update (e.g. 45 per day × 30 days).
3 GET /v1/analytics/anomalies/outOfFamily/report?orbitRegime=LEO Out-of-family daily snapshot: one call per UTC day for the regime that matches your fleet—this step uses orbitRegime=LEO; use GEO when appropriate—not on every catalog/TLE cycle. Optional noradIds query parameter (comma-separated NORAD IDs) filters the objects array to your fleet.

Outcome

Fleet visibility via catalog and lastSeen; TLE refresh only when data has changed; out-of-family screening once per UTC day (one snapshot GET for your orbit regime) without redundant calls.

Maneuver Detection and Analysis

Objective: Analyze orbital decay and maneuver detection for a single spacecraft over 30 days. Pull historical TLEs day by day, then enrich with spacecraft metadata and propulsion context: list thrusters to see which engines the vehicle uses, then get full engine details for each (e.g. 2 engines). Use this to interpret delta-V from TLEs, attribute maneuvers to specific propulsion, or assess performance against known hardware.

Step Endpoint Purpose
1 GET /v1/catalog/tle/{spaceObjectId} One call per day for 30 days (endpoint returns TLEs for a single day)
2 GET /v1/contextual/spacecraft/{spaceObjectId} Spacecraft metadata for the object under analysis
3 GET /v1/contextual/thrusters See which thrusters (spacecraft–engine links) the vehicle is equipped with
4 GET /v1/contextual/engines/{engineId} Full engine details for 2 engines the spacecraft is equipped with

Outcome

30-day TLE history plus contextual spacecraft and propulsion data for maneuver and decay analysis.

Keep external Seradata (contextual) copy up to date

Objective: Weekly sync driven by launch activity: ~5 launches per week with ~20 spacecraft per launch (100 spacecraft). A quarter of those (25) introduce new engines, thrusters, or payloads. Reference data such as companies and countries is not refreshed (assumed stable). List endpoints run once per week; detail fetches scale with launches and new spacecraft/components.

Step Endpoint Purpose
1 GET /v1/contextual/spacecraft Weekly list check for new/updated spacecraft
2 GET /v1/contextual/spacecraft/{spaceObjectId} 5 launches × 20 spacecraft
3 GET /v1/contextual/spacecraft/{spaceObjectId}/aliases Weekly list check
4 GET /v1/contextual/rocket-body/{spaceObjectId} 5 launches (upper stages)
5 GET /v1/contextual/launch/sites Weekly list check
6 GET /v1/contextual/launch/sites/{launchSiteId} 5 launches from 1–2 sites
7 GET /v1/contextual/launch/vehicles Weekly list check
8 GET /v1/contextual/launch/vehicles/stages Weekly list check
9 GET /v1/contextual/launch/vehicles/{launchVehicleId}/stages 3 vehicle types used across 5 launches
10 GET /v1/contextual/launch/vehicles/{launchVehicleId}/spec 3 vehicle types
11 GET /v1/contextual/launches Weekly list check
12 GET /v1/contextual/launches/{launchId} 5 launches
13 GET /v1/contextual/engines Weekly list check
14 GET /v1/contextual/engines/{engineId} 25 spacecraft with new engines (¼ of 100)
15 GET /v1/contextual/thrusters Weekly list check (25 spacecraft with new thrusters)
16 GET /v1/contextual/solar-arrays Weekly list check
17 GET /v1/contextual/solar-arrays/{solarArrayId} New arrays for 25 spacecraft (subset)
18 GET /v1/contextual/batteries Weekly list check
19 GET /v1/contextual/batteries/{batteryId} New batteries for 25 spacecraft (subset)
20 GET /v1/contextual/antennas Weekly list check
21 GET /v1/contextual/antennas/{antennaId} New antennas for 25 spacecraft (subset)
22 GET /v1/contextual/events Weekly list check
23 GET /v1/contextual/events/{eventId} 5 launch events
24 GET /v1/contextual/payloads/communication Weekly list check
25 GET /v1/contextual/payloads/communication/{communicationPayloadId} New payloads from 25 spacecraft
26 GET /v1/contextual/payloads/optical Weekly list check
27 GET /v1/contextual/payloads/optical/{opticalPayloadId} New payloads from 25 spacecraft
28 GET /v1/contextual/payloads/radar Weekly list check
29 GET /v1/contextual/payloads/radar/{radarPayloadId} New payloads from 25 spacecraft
30 GET /v1/contextual/payloads/navigation Weekly list check
31 GET /v1/contextual/payloads/navigation/{navigationPayloadId} New payloads from 25 spacecraft
32 GET /v1/contextual/payloads/early-warning Weekly list check
33 GET /v1/contextual/payloads/early-warning/{earlyWarningPayloadId} New payloads from 25 spacecraft
34 GET /v1/contextual/payloads/sigint Weekly list check
35 GET /v1/contextual/payloads/sigint/{sigintPayloadId} New payloads from 25 spacecraft
36 GET /v1/contextual/payloads/scientific-or-other Weekly list check
37 GET /v1/contextual/payloads/scientific-or-other/{scientificOrOtherPayloadId} New payloads from 25 spacecraft

Outcome

External copy of contextual data kept in sync with weekly list checks and detail fetches driven by launch activity.

Summary

Workflow Main Endpoints

Use list endpoints to discover IDs, then get-by-ID and catalog state endpoints for detailed context.