For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tasking API

The Tasking API lets you request new drone captures of an area of interest and track their progress from submission through delivery. Submit an order specifying the area, the products you need, and your customer details - then follow each product through its lifecycle.

Endpoints

Area of Interest

An order's area is defined one of two ways, never both: a list of H3 zones, or a GeoJSON geometry polygon.

Products

Each order requests one or more products. Every product on an order is tracked independently and moves through its own status lifecycle.

Order Product Status Lifecycle

Each product on an order moves independently through this lifecycle:

Status
Definition

submitted

Order received, not yet reviewed

in_review

Spexi is reviewing the request

feasibility_check

Assessing whether the capture is achievable (site access, airspace, terrain, etc.)

pending_confirmation

Awaiting customer confirmation before mission planning begins

in_planning

Mission planning in progress

capture_in_progress

Pilots are actively capturing the area

processing

Captured data is being stitched/processed into the final product

qa

Product is in quality review before delivery

delivered

Product delivered

cancelled

Order product was cancelled

unfulfillable

Spexi determined the product can't be completed (e.g. failed feasibility)

The status filter on List Tasking Orders uses this lifecycle: current matches orders with at least one product not yet in a terminal state, past matches orders where every product has reached delivered, cancelled, or unfulfillable.

Authentication

All tasking endpoints accept an API key via the x-api-key header or the api_key query parameter.

Last updated