Skip to main content

Starlink STC Access

Satcat integrates with Starlink's Space Traffic Coordination (STC) API to support Satcat-initiated actions that require authenticated access to Starlink's Space Safety system. When enabled for an organization, Satcat uses the configured credentials for Starlink-facing actions initiated from Satcat, including screening requests and operational ephemeris submission.

View Starlink STC API Docs

Scope​

The integration applies only to actions initiated from Satcat that call the Starlink STC API. It does not change how Starlink evaluates, accepts, or acts on submitted information; all downstream handling is governed by Starlink systems and policies.

Credential Configuration​

Starlink STC API access requires Starlink API credentials. Satcat supports two authentication modes: Kayhan-managed and Starlink-issued credentials.

Kayhan-Managed Credentials​

In this mode, Satcat authenticates to Starlink using Kayhan-managed Starlink credentials.

Requests initiated through Satcat are attributed to the Kayhan organization identity within the Starlink Space Traffic Coordination system. RSOs represented in submitted data are treated as Kayhan-owned within Starlink's system. Kayhan-managed credentials are used by default, and are used when no Starlink-issued credential set is configured as the primary.

warning

If RSOs are already registered to an operator organization in the Starlink Space Safety system, Kayhan-managed credentials cannot be used to submit data for those RSOs.

In this mode, Satcat authenticates to Starlink using a Starlink-issued credential set (.csr, .key, .crt) and a Starlink-assigned Operator ID, held in Starlink STC Integration under Control Center Integrations.

Requests initiated through Satcat are attributed to the operator's organization identity within the Starlink Space Traffic Coordination system. Starlink ownership restrictions apply as recorded in Starlink's system, including restrictions tied to organizations recorded as RSO owners.

Multiple credential sets may be uploaded for an organization. Satcat uses the credential set marked as the primary for Starlink STC API interactions.

Enabling the Integration​

An Admin configures Starlink-issued credentials in Control Center, under Integrations, in Starlink STC Integration.

  1. Add Credential uploads the credential set (.csr, .key, .crt) with a Credential Name and the Starlink-assigned Operator ID.
  2. Set as primary marks the set Satcat uses. The current one is shown as the Primary Credential, and Unset primary clears it.
  3. Enable the Starlink integration.

Once enabled, the configured credential connection is used for subsequent Satcat-initiated interactions that call the Starlink STC API.

When determining whether an operator can access a given object in Starlink, Satcat checks access using both the operator's Starlink-issued credentials and Kayhan-managed credentials. New objects are created under the primary credentials where available.

Data Usage​

Satcat uses the Starlink STC API for two Starlink-facing actions initiated from Satcat:

  • Operational ephemeris forwarding. Operational ephemerides forwarded to Starlink are submitted using the Starlink ephemeris classification DEFINITIVE.
  • Screening jobs. Screening job submissions to Starlink are submitted using the Starlink ephemeris classification HYPOTHETICAL.

Lifecycle and Changes​

Credential rotation, revocation, switching between credential modes, or changing which Starlink-issued credential set is marked as primary requires updating the configuration in the Control Center. Changes apply only to interactions initiated after the update.

Remove deletes a credential set. Previously transmitted data is not retroactively re-submitted.