Eagle Eye DFR exposes a documented REST + real-time API and a launchable operator console. Your CAD deploys a drone to an incident, streams live telemetry, receives detections, and keeps a synchronized incident log — with no drone UI to build.
Base URL https://dronefleet-api.azurewebsites.net · JSON over HTTPS · prefix /api/v1. Supported aircraft: MAVLink autopilots only.
An org admin mints a credential (POST /api/v1/api-keys). Authenticate with HTTP Basic base64(clientId:secret) or the X-Api-Key + X-Api-Secret headers.
POST /missions → /start launches to the incident. Read /vehicles/{id}/telemetry or subscribe SignalR /hubs/fleet.
Open {base}/console?clientId=…&clientSecret=…&source=CFS&lat=…&lon=… — the operator interface, served same-origin, no CORS setup.
POST /targets and /missions/{id}/events; receive push via webhooks (target.detected) or SignalR.
GET/PUT /config/geofence — a box or polygon + altitude ceiling that every mission is validated against.
A closing incident-event (or /complete) finishes the mission and returns the drone to base.
Grab a free trial key (20 flights) to prototype, or an org admin mints a production credential.
On a drone event, open {base}/console?clientId=…&clientSecret=…&source=CFS&caseNo=…&lat=…&lon=… — the console does the rest.
Prefer your own UI? Call the REST + webhooks + SignalR endpoints directly. See the samples in the kit.