Constellation for Enterprise
Start here if your company has its own Constellation deployment. The rest of these docs apply to you, with the differences on this page.
What you have
Your company runs its own Constellation deployment with a dedicated API host and Platform site. Your telemetry, forecasts, and API keys stay in that deployment; see Tenant isolation.
| Service | Your address |
|---|---|
| Platform | https://platform.<your-company>.constellation.space |
| HTTP API | https://<your-company>.api.constellation.space |
Your Constellation contact confirms both addresses during onboarding.
Your deployment also gets Silver and Gold data and models as they are released, and refines your own data in place; see Medallion Tiers.
Sign in
- Open your Platform address.
- Enter your code name. It comes from your Constellation contact.
- Enter your team password. If your company's sign-in has been set up with Constellation, you can choose Continue with <your company's sign-in> on the same step instead.
There is no self sign-up. Ask your Constellation contact for access or a new password. Repeated wrong team passwords lock sign-in for a while; if that happens, contact your Constellation contact.
Your API base URL
Use your API host wherever these docs show https://api.constellation.space. Endpoints, parameters, scopes, and the x-api-key header are the same.
export CONSTELLATION_API_URL="https://<your-company>.api.constellation.space"
Keys work only on the deployment that issued them. A key sent to the shared host fails with 401 auth_failed. Repeated failed attempts return 429 auth_lockout for a while, even after you fix the key.
API keys
Create keys on the Keys page of your Platform site: choose Create live key, pick an Expiration, select the scopes your integration needs, and copy the secret. It is shown once. Keys are shared across your team.
Send the key in the x-api-key header:
export CONSTELLATION_API_KEY="cos_live_..."
- Keep keys in an environment variable or secrets manager. Do not commit them, log them, or ship them in frontend code.
- Use one key per integration so you can revoke one without breaking the others.
- To rotate, create the new key, deploy it, then revoke the old one on the Keys page.
- Give the team's keys an expiry that matches your rotation schedule. Watch the Expires column on the Keys page: a key due within 7 days shows in amber, and a past one reads Expired and gets
401 auth_failed. Rotate before that.
See Authentication for scopes, expiry, and lockout behavior.
Make a first call
Check that your API host is up. Health endpoints need no key:
curl -sS "$CONSTELLATION_API_URL/health"
Then confirm your key with a fleet read:
curl --fail-with-body -sS \
-H "x-api-key: $CONSTELLATION_API_KEY" \
"$CONSTELLATION_API_URL/topology?freshness_seconds=900"
A 200 confirms the key works; the key needs topology:read, and config:read, config:write or workflows:write for config to be filled. An empty state array means no telemetry has arrived in the last 15 minutes.
Forecast your first pass
Your deployment forecasts from a network config: you describe your stations and satellites once, then ask for any link at a time you name. Use a key with config:write, telemetry:write and predictions:read.
-
Upload your network config. Save your ground stations, antennas, satellites and radios as
topology-config.json, starting from the example document, and upload it:curl --fail-with-body -sS -X PUT \-H "x-api-key: $CONSTELLATION_API_KEY" \-H "Content-Type: application/json" \--data @topology-config.json \"$CONSTELLATION_API_URL/topology/config"Fix anything listed in
issuesin the response; each one names the field it is about. -
Forecast a pass. Ask for SNR at the start, the highest point and the end of an upcoming pass, one request per time. Replace the times with your pass's:
for AT in 2026-10-29T08:12:00Z 2026-10-29T08:18:30Z 2026-10-29T08:25:00Z; docurl --fail-with-body -sS -G \-H "x-api-key: $CONSTELLATION_API_KEY" \"$CONSTELLATION_API_URL/predictions" \--data-urlencode "model_family=snr" \--data-urlencode "ground_station_id=gs-1" \--data-urlencode "satellite_id=sat-1" \--data-urlencode "at=$AT"doneEach response has one item per antenna with
value.snr_db_p50, or an entry inentity_errorsthat says why there is none. See Declines. -
Send telemetry during passes. Write one telemetry record per link at least once a minute while it is in view, with
es_n0_db,elevation_degandrange_m:curl --fail-with-body -sS -X POST \-H "x-api-key: $CONSTELLATION_API_KEY" \-H "Content-Type: application/json" \"$CONSTELLATION_API_URL/telemetry" \-d '[{"time": "2026-10-29T08:18:30Z", "ground_station_id": "gs-1", "ground_antenna_id": "ant-1","satellite_id": "sat-1", "fields": {"es_n0_db": 12.5, "elevation_deg": 45.0, "range_m": 1200000.0}}]'Until an antenna has calibrated, its SNR forecast is the link budget alone. On the data we have evaluated so far, the quick adjustments settle within 10 to 30 passes per antenna, and calibration converges after a few hundred. See Telemetry.
The Common questions page answers what teams usually ask next, such as how far ahead you can forecast and how to add many stations.
What is different from self-serve
- No sign-up or billing pages. Plans and pricing in these docs do not apply to you.
- Constellation enables features for your deployment. A feature that is not enabled returns a clear error, such as
404 predictions_not_enabled, and Platform shows a notice instead of the page. - Your Constellation contact handles access, passwords, and enabling features.
Get help
Contact your Constellation contact. Include the request time, the endpoint, and the error code or incident_id from the response.