1-Immediate Task / 2-Repeat Task / 3-Single Scheduled Task / 5-Continuous Task. This is the most critical semantic control field of POST /flight-tasks.Real-time Control Tutorial → Fly-to Point for details); ② GET /flight-tasks/check verifies device + wayline match; ③ POST /flight-tasks/reject-takeoff checks flight blocking items (immediate tasks only).PUT /{task_uuid}/status) only pauses scheduling but retains the task; cancellation enters a terminal state; the "pause / continue / terminate" of executing tasks goes through PUT /drc/api/v2/projects/{uuid}/flight-wayline-tasks/commands (Real-time Control module).POST /flight-tasks/export returns task_id; the client polls GET /flight-tasks/export to see progress, and after completion uses GET /flight-tasks/oss-url-info to exchange for a signed URL to download the zip.Check Flight Task Flight Blocking Items (POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/reject-takeoff). This interface only accepts task_type=1; other values will be rejected by the server with HTTP 400 + code = 200101 (message: "param is invalid"). Returns the weather blocking results of the current / landing dock and the GPS wayline blocking results in mobile deployment mode, avoiding being stuck by the business layer after user submission.Check If Flight Task Meets Dispatch Conditions (GET /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/check) — Query parameters are sn (device SN, note that in spec it is sn not device_sn) + wayline_uuid, verifies whether the combination can be successfully dispatched, returns warning list but does not block creation.Query Flight Task Time Conflict List (POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/conflicts) — Request body required fields: task_type, time_zone, sn, etc. (consistent with the time rules when creating the task), reverse-queries the list of existing tasks under the same device SN that would conflict in time.Create Flight Task (POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks).Create Flight Task (Advanced, Returns Sub-tasks) (POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/advanced) — Same business rules, but the response carries sub-task information (repeat / continuous tasks will split into multiple sub-tasks), making it convenient to obtain the complete parent-child structure at once.Query Flight Task List (V2, supports multi-dimensional filter) (GET /openapi/v2.0/task/api/v2/workspaces/{proj_uuid}/flight-tasks) — Supports filtering by task name, device SN, time period, task type, status, etc., paginated in reverse chronological order.Get Flight Task Details (GET /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/{task_uuid}) — Includes rules, devices, waylines, status, sub-tasks, VLM configuration, breakpoint info, etc.Get Flight Task Detailed Info (V2, with execution details) (GET /openapi/v2.0/task/api/v2/workspaces/{workspace_id}/flight-tasks/detail) — More than V1: execution trajectory details / flight sortie list / media collection summary.Batch Query Flight Task Details by UUID (GET /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/batch) — Suitable for front-end task dashboard batch status refresh, cross-system status synchronization.Query Recent / Current Task of Dock (GET /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/recent) — Returns executing + paused tasks first, then the latest failed / terminated one; cache hits return directly.Get Current Active Wayline Task (Task Management) (GET /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/in-flight).Get Current Active Wayline Task (DRC Real-time Control) (GET /openapi/v2.0/drc/api/v2/projects/{prj_id}/flight-tasks/in-flight). Both interfaces have the same semantics; choose based on the calling context.Get Task Flight Trajectory (V2) (GET /openapi/v2.0/task/api/v2/workspaces/{workspace_id}/flight-tasks/track) — The actual waypoint latitude/longitude + altitude + timestamp sequence of completed tasks, used for trajectory playback.| Purpose | Interface |
|---|---|
| Edit (only undispatched scheduled / repeat sub / continuous sub) | PUT /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/{task_uuid} |
| Delete (only unexecuted / completed / terminated) | DELETE /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/{task_uuid} |
| Suspend / unsuspend / cancel | PUT /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/{task_uuid}/status |
| Media priority upload | POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/{task_uuid}/cmds |
| Mark as read (clear exception red dot) | PUT /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/read-confirm |
The pause / continue / terminate of executing tasks goes through "Real-time Control → Flight Control Command → In-flight Task" PUT /drc/api/v2/projects/{uuid}/flight-wayline-tasks/commands. Thestatusinterface of this module only controls the "suspend / cancel" semantics; seeReal-time Control Tutorialfor details.
Immediate Task Supporting Breakpoint Resume Flight (POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/resume-immediate), request body { "task_uuid": "<original task UUID>" }. Copies key fields such as name / wayline / RTH / resume mode / breakpoint JSON / wayline duration based on the original task, forcing task_type=Immediate, is_break_point_resume=true.Create Resume Flight Task (Preserves Original Breakpoint) (POST /openapi/v2.0/task/api/v1/workspaces/{workspace_id}/flight-tasks/{task_uuid}/resume), the request body also uses { "task_uuid": "<original task UUID>" }. Copies breakpoint info based on the completed task, preserving the original task_type.Query Flight Sortie List with AI Alerts by Device SN (GET /openapi/v2.0/drc/api/v2/projects/{uuid}/ai-alert-flight).Query Historical AI Alert Records (GET /openapi/v2.0/drc/api/v2/projects/{proj_uuid}/ai-alert-record) — flight_id[] is required query (accepts multiple values, corresponding to a set of sortie IDs); can be stacked with filters by time range / device / algorithm.Export Flight Task Records (Asynchronously Generate zip Task) (POST /openapi/v2.0/task/api/v2/workspaces/{workspace_id}/flight-tasks/export). Request body required fields: flight_task_ids (list of UUIDs of tasks to be exported), file_name, file_type, content_type, metrics.Query Flight Task Export History (GET /openapi/v2.0/task/api/v2/workspaces/{workspace_id}/flight-tasks/export) — status is an integer enum: 0=in progress / 1=completed / 2=failed / 3=cancelled.Flight Record File Download (GET /openapi/v2.0/manage/api/v1/workspaces/{uuid}/flight-tasks/oss-url-info) exchange for temporary signed URL by object_key.Cancel / Delete Export Task (PUT /openapi/v2.0/task/api/v2/workspaces/{workspace_id}/flight-tasks/export) — In-progress tasks can be cancelled (when status=0); completed records can be deleted (status=1/2).Query Flight Task Operation Log (V2) (GET /openapi/v2.0/task/api/v2/workspaces/{workspace_id}/flight-tasks/oper) returns all operation records of the specified task (create / edit / suspend / cancel, etc.), sorted by time, commonly used for audit tracing.Aligned with the V0.9 On-Premises "Execute Wayline Task API Call Guide", paths have been adapted to V2.0.