Connect an aircraft to Flow in an afternoon.

Loading the live contract…

Authentication

curl -s https://YOUR-HOST/api/v1/telemetry \
  -H "X-Api-Key: scsk_…" -H "Content-Type: application/json" \
  -d '{"asset_id":"NL-041","position":{"lat":52.36,"lon":4.84,"alt_m":110},"speed_ms":26.4,"heading_deg":118,
       "flight_mode":"CRUISE","soc_pct":71.5,"batt_temp_c":33.1,"link":{"primary":"up","contingency":"up","quality":0.93},"faults":[]}'

Keys are issued by a Simplycity administrator in the console (Administration → Integrations), are scoped and revocable, and only their hash is stored.

Endpoints

What Simplycity does with your data

Rules it enforces

Telemetry older than the policy limit (default 20 s) fails the communications ready gate.
State of charge is compared to route + wind + 30 % reserve energy.
Faults, battery temperature and configuration version gate aircraft healthy.
In flight: cross-track above 60 m warns; above 120 m raises a geofence breach incident.
Silence for 25 s of flight raises loss-of-link with the last known position retained.

Mission lifecycle you will see

REQUESTED → PAYLOAD_READY → PREFLIGHT_CHECK → RELEASED → LAUNCHING → AIRBORNE → APPROACHING → LANDED → HANDED_OVER → CLOSED
Exceptions: ON_HOLD · RETURNING · DIVERTING · INCIDENT_REVIEW · ABORTED

Poll /missions/{id}/package for release status; the OEM stays the source of truth for aircraft data, Simplycity stores source, quality and time.

Sandbox contract — subject to change with the selected OEM/operator. Shown live from /api/v1/spec.