Skip to main content

Tasking V2 Migration Guide

NOTE Tasking API V2 is in final development and review. This draft documentation is subject to change at any time. Tasking V2 is not available for testing or running examples at this time.

Tasking documentation changelog​

Tasking V2 documentation has been made available prior to beta testing to allow for users to learn and prepare for the API changes as soon as possible. These documents are receiving constant updates as the V2 API nears its beta release for external testers.

Tasking documentation last updated: October 23, 2025

  • Updated that the download delivery option is not currently available in the V2 rollout but will return later.
  • "Get Monitor Events" endpoint removed. Events are included in the "Get Monitor" response.
  • Noted download is not a delivery option in V2
  • The following fields have changed in Tasking payloads:
    • The description field is now request_description
    • The product_licensing field has been shortened to licensing
    • product_type values now align with Archive Ordering pipeline names:
      • system-ready replaces 1B
      • view-ready replaces 2A
      • view-ready-ortho replaces OR2A
      • map-ready replaces 3D
  • In the left navigation bar, Tasking V1 is "Tasking", and Tasking V2 is "Tasking V2 Preview."
  • The defaults for product_option are based on the tasking tiers, not the product type. See Default Product Recipes: Product Option defaults.
  • There are changes to Tasking statuses to make it easier to track an order through the system. See Tasking V2 Statuses.
  • Added instructions for modifying the end date of a Flexview order. See Modifying the end date for a Flexview request.
  • Added more information to the Update Tasking requests section below. Please re-read this section.

Understand tasking tiers​

The V1 Tasking API had a concept of "Tasking Priority" which was one of several parameters that could be specified when submitting a tasking request. The tradeoffs between speed and configurability were left to the end user to understand and adjust. To make thing clearer, Tasking is now divided into two distinct tiers named Fastview and Flexview.

Fastview has limited options, but guarantees a collection within 24 hours. Flexview gives you more control over the image collection if a short time frame is not needed.

Update quote requests​

Getting a usage quote has been simplified and the endpoint has been moved to align with other APIs.

Only a minimum of parameters are now needed to generate a quote:

  • tasking_tier: Selects from Flexview and Fastview.
  • max_gsd: Determines whether to use 30cm class sensors only, or include 50cm class sensors for more opportunities.
  • geometry: Describes the geometry by either a polygon or a center point plus buffer.

The endpoint is now at /estimate instead of /quote.

See Quote a Tasking Request.

Update tasking requests​

The payload to submit a tasking request has been updated. Many fields are the same, but some have been grouped to better organize all the settings. You will need to adjust existing requests to use this new format.

Similarly, the response payload has also changed. You may need to adjust how you handle returned payloads. There are important differences in the Flexview and Fastview request parameters.

Some differences between the Fastview and Flexview requests are:

  • Flexview requires a start date and an end date. Fastview only accepts a start date. The tasking request will be collected within 24 hours of the start date.

  • A Fastview request is essentially a reservation for a 24 hour period. When the request is made, the requested start date is checked. If the date is available, the request is accepted. If the date is not available, the API returns a 4XX response with a list of surrounding available dates.

  • The start date for a Fastview request must be at least 8 hours out and no further than 14 days from the date the request is submitted.

  • Flexview takes a geojson polygon geometry. Fastview uses latitude and longitude points with buffer.

  • The validation_only query parameter can be applied to a POST tasking request to validate the request against the tasking schema. For Fastview orders, this also checks to see if the requested start date and time are available. If the requested date/time is not available, a 400 error code will be returned, along with a list of alternate dates to choose from.

See Submit Flexview Tasking and Submit Fastview Tasking.