Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
openapi: 3.2.0
info:
title: ConstellationOS Telemetry API
version: v1
summary: ML-native operations API for satellite fleets — connect telemetry, read fleet topology, run link forecasts.
description: The ConstellationOS HTTP API lets satellite fleet operators ingest ground telemetry through a single schema, read the live fleet topology graph, and run ML link forecasts on live fleet context.
contact:
name: Constellation Space Corp
email: contact@constellation.space
url: https://docs.constellation.space
x-apievangelist-provenance:
method: searched
source: https://docs.constellation.space/connect/api-tokens
note: Reconstructed from public docs; operations + scopes documented, bodies not published.
servers:
- url: https://api.constellation.space
description: Production
- url: https://api-staging.constellation.space
description: Staging
- url: https://api-dev.constellation.space
description: Development
security:
- bearerAuth: []
tags:
- name: Telemetry
description: Ingest ground telemetry metrics aligned to the fleet graph.
paths:
/api/v1/telemetry/ingest:
post:
operationId: ingestTelemetry
summary: Ingest ground telemetry
description: Ingest telemetry metrics from ground agents/edge collectors, aligned to the fleet graph. Requires the telemetry:write token scope. The fleet agent posts metrics in line protocol.
tags:
- Telemetry
security:
- bearerAuth:
- telemetry:write
responses:
'200':
description: Telemetry accepted for ingestion.
'401':
description: Missing, invalid, or revoked API token.
'403':
description: Token lacks the required telemetry:write scope.
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: 'API token issued from the console (Settings -> API), sent as "Authorization: Bearer <token>". Production tokens are prefixed cos_live_ and non-production tokens cos_dev_. Tokens are scoped, shown once at creation, and can be revoked instantly.'
x-token-prefixes:
production: cos_live_
non_production: cos_dev_
x-scopes:
topology:read: Read the fleet topology graph.
telemetry:write: Ingest telemetry metrics.
predictions:run: Run ML predictions.