Dispatch and monitor multi-dock missions through DJI FlightHub 2's OpenAPI
domain: enterprise.dji.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Provision DJI FlightHub 2 (cloud SaaS or on-premises AIO deployment) and enable OpenAPI access for third-party integration
Use the REST API to launch on-demand flight missions from an external system (e.g., ticketing or CRM) and track progress in real time
For DJI Dock 2 deployments, dispatch tasks across multiple docks simultaneously through the same API surface
Pull centralized fleet data — drone position, status, telemetry, battery, and assigned operator — for a unified operations map
Integrate multi-channel livestream monitoring (up to 16 simultaneous feeds) into a custom command-center UI where needed
Known gotchas
Choosing between cloud SaaS and on-premises AIO deployment has real integration implications (network topology, latency, data residency) and is not simply a config toggle after the fact
Multi-dock simultaneous dispatch capability depends on the Dock 2 generation and FlightHub 2 licensing tier — older Dock hardware may not support the same fan-out
OpenAPI access is a distinct enablement from the base FlightHub 2 license; integrations should confirm API entitlement before designing around it
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?