The Planet Tasking API (2.0) provides high-resolution satellite imagery as a service. A tasking order is a request to capture new imagery of a specific area of interest (AOI) within a given time of interest (TOI); archive orders instead request high-resolution collects that are already in the archive.

Tasking orders are not to be confused with scene and Mosaics Order offered by the Planet Orders API — those deliver already-captured data, while a tasking order requests a new capture (archive orders request collects that are already in the archive).

Archive tasking - offers access to high-resolution imagery captured in the past. Purchasing archive imagery through the Tasking API is deprecated and will be fully sunset on November 1, 2026.

Key properties of a tasking order

A tasking order includes, among other fields:

• Geometry — the AOI, plus original_geometry (what you submitted) and fulfilled_geometry (the order's geometry, intersected with the combination of the geometries from its fulfilling captures). Original geometry types (original_geometry_type) are Point, LineString, and Polygon.
• Time of interest — start_time and end_time, with an early_start flag (Monitoring Tasking orders only).
• Capture constraints — such as cloud_threshold and minimum/maximum satellite elevation angles (sat_elevation_angle_min / sat_elevation_angle_max).
• Quota — estimated_quota_cost and used_quota, plus requested_sqkm and fulfilled_sqkm for area accounting.
• Cancellation — is_cancellable, cancellable_until, and whether a cancellation_fee_applied.
• Capture progress counters — counts of captures that are queued, processing, deriving, failed, or published, and capture assessments (successful / invalid).
• Satellite and products — for example satellite_types: ["SKYSAT"] and data_products: ["HIGH_RESOLUTION_SCENES"].

Order types

Scheduling types

The scheduling_type field takes one of: FLEXIBLE, LOCK_IN, MONITORING, EXPRESS, ASSURED, ARCHIVE.

Order statuses

A tasking order's status moves through values from this set:

RECEIVED, PENDING, IN_PROGRESS, EXPIRED, FULFILLED, FAILED, CANCELLED, REQUESTED, FINALIZING, PENDING_CANCELLATION, REJECTED, WAITLISTED, WAITLIST_ABANDONED, WAITLIST_EXPIRED

Listing and filtering your tasking orders

The List Tasking Orders endpoint retrieves all tasking orders you have access to, including all orders created within your organization. Results are paginated with limit (1–1000 results per page) and offset (0–30000), and can be sorted with ordering. Use fields or omit (comma-separated lists) to control which fields come back in the response.

Tasking orders can be filtered by created, start and end times, name and many other values via query parameters, with comparison suffixes such as __gt, __gte, __lt, __lte, __ne, __in, __notin, and __icontains for case-insensitive contains. Useful examples:

• status__in=IN_PROGRESS,FULFILLED — orders in one of the given statuses.
• name__icontains=<text> — orders whose name contains the text, case-insensitive.
• created_time__gte=<date-time> — orders created on or after a date.
• geometry__intersects=<GeoJSON or WKT> — orders whose geometry intersects a given geometry; geometry__centroid_within filters by centroid instead.
• satellite_types=SKYSAT — filter by satellite type.
• pl_number=<contract number> — filter by contract.
• ends_in_hours__lt=48 — filter by the ends in hours to be less than 48.
• cancellation_fee_applied=true — orders where a cancellation fee applied.

Learn more

• Tasking API Reference — full parameter list, response schema, and a downloadable OpenAPI specification