Vega
API Reference

Getting Started

Pull interference forecasts, satellite metadata, and coverage results programmatically.

For developers and data teams who need to pull forecast data into their own systems.

1. Authenticate

Pass your API token as a bearer credential:

Authorization: Bearer <token>

See Authentication for how to obtain a token.

2. Single-point query

GET /api/v1/interference/at_point returns interference intensity at a specific coordinate and timestamp.

curl "https://vega.space/api/v1/interference/at_point?tracked_satellite_id=123&lat=37.77&lon=-122.42&timestamp=2026-05-20T12:00:00Z" \
  -H "Authorization: Bearer $VEGA_API_TOKEN"

Example response

{
	"intensity": 14,
	"timestamp": "2026-05-20T12:00:00Z",
	"risk_level": "moderate",
	"nside": 64,
	"cell_resolution_deg": 0.92,
	"frequency_band": "Ku"
}

intensity is the count of interfering satellites. See Interference analysis for the full schema and risk-level thresholds.

3. Time-series data

Two endpoints provide interference over time:

  • GET /api/v1/interference/timeseries — over a geographic coordinate
  • GET /api/v1/interference/ground_station_timeseries — during passes over a ground station

Rate limit: 100 requests/minute. Maximum timeseries window: 7 days (10,080 minutes at 1-minute resolution). See Rate limits.

Production integration

Go beyond co-visibility forecasting by sharing link-level parameters with Vega.

You provide

  • Beam geometry and antenna patterns
  • EIRP, bandwidth, polarization, G/T, modulation
  • Measured Eb/N0 and noise-floor telemetry

You receive

  • ΔC/I and ΔEb/N0 calculations
  • Expected link-margin degradation
  • Model calibration feedback

Co-visibility is a statistical proxy, but elevated density strongly correlates with noise-floor excursions in shared bands.

On this page