API overview
The Constellation API accepts telemetry, returns fleet state, and serves model predictions. Use it from backend integrations, gateway agents, or mission scripts.
Endpoints
| Method and path | Authentication | Purpose |
|---|---|---|
GET /health and GET /health/* | None | Service and subsystem health. |
GET /topology | x-api-key | Latest state per entity. |
GET /topology/series | x-api-key | Measured channels over a time window. |
POST /telemetry | x-api-key | Telemetry ingestion. |
GET /predictions | x-api-key | Model forecasts: SNR and demand. |
GET /account/state | x-api-key | Account state, entitlements, and usage. |
Read integrations poll the HTTP endpoints. Fleet agents can also publish through the gRPC ingest endpoint.
Access and environments
Pro includes Fleet SDK access. Requests require a valid key, the appropriate scopes, and enabled account access. Enterprise endpoints and credentials are supplied during onboarding.
| Environment | HTTP base URL |
|---|---|
| Shared production | https://api.constellation.space |
| Enterprise | The base URL provided by Constellation |
Guest, Free, and Pro use shared infrastructure. Tenant isolation is available on Enterprise; see Tenant isolation.
Keep keys server-side
Send the key in x-api-key. Use an environment variable or secrets manager, and keep credentials out of browser bundles. If a web application needs API data, call Constellation from your backend.
Start with Authentication, then run the connection smoke test. See Errors and limits before adding a polling loop.