Create Your First Order

Our ordering flow is designed to support an automatic ordering flow, and the below example will go through the necessary endpoints. It will show example usage for our estimate and order endpoints for a given area as an composite and tile order. It's recommended to always use our estiamte endpoint before placing an order, as the estimate endpoint will return price, actual order area and the image dates you will receive imagery for.

Estimate Order Cost

The estimate payload and response example below is for an historical composite order, meaning we ask for an estimate for two months of imagery with no future dates using the composite order type.

Estimate endpoint: POST /api/tasking/orders/estimate

Example estimate payload:

{
  "Wkt": "GEOMETRYCOLLECTION (POLYGON ((8.675127 55.962046, 8.675127 55.963407, 8.679411 55.963407, 8.679411 55.962046, 8.675127 55.962046)), POLYGON ((8.472053 56.105382, 8.472053 56.337398, 8.948552 56.337398, 8.948552 56.105382, 8.472053 56.105382)), POLYGON ((8.678 55.948533, 8.678 56.068376, 8.878589 56.068376, 8.878589 55.948533, 8.678 55.948533)))",
  "SatelliteConstellations": [
    "Sentinel1",
    "Sentinel2",
    "Landsat89"
    ],
  "Model": "Stratus2",
  "StorageMonths": 2,
  "ApiRequests": 2,
  "ImageFrequency": 2,
  "ReferenceDate": "2023-06-01",
  "From": "2023-06-01",
  "To": "2023-07-31"
}

Example estimate response:

{
  "Data": {
  "StorageMonths": 2,
  "ApiRequests": 2,
  "SatelliteConstellations": [
    "Sentinel1",
    "Sentinel2",
    "Landsat89"
  ],
  "Model": "Stratus2",
  "CancellationDate": "2024-09-30",
  "AreaKm2": 931.61,
  "AreaKm2BeforeMinimum1Km2PerAoi": 930.65,
  "CurrentMonthCost": 1000009.98,
  "NextMonthCost": 1000009.98,
  "Costs": {
    "CurrencyCode": "EUR",
    "CurrentMonthOrderCostEstimate": 999999.99,
    "CurrentMonthStorageCosts": 9.99,
    "NextMonthOrderCostEstimate": 999999.99,
    "NextMonthStorageCosts": 9.99
  },
  "UsageUnits": {
    "CurrentMonthOrderUsageUnitsEstimate": 999999.99,
    "NextMonthOrderUsageUnitsEstimate": 999999.99
  },
  "Tiles": [ ],
  "MiniTiles": [ ],
  "AreasOfInterestWkt": "GEOMETRYCOLLECTION (POLYGON ((8.675127 55.962046, 8.675127 55.963407, 8.679411 55.963407, 8.679411 55.962046, 8.675127 55.962046)), POLYGON ((8.472053 56.105382, 8.472053 56.337398, 8.948552 56.337398, 8.948552 56.105382, 8.472053 56.105382)), POLYGON ((8.678 55.948533, 8.678 56.068376, 8.878589 56.068376, 8.878589 55.948533, 8.678 55.948533)))",
  "ImageDates": ["2023-06-01", "2023-06-03", "2023-06-05", "2023-06-07", "2023-06-09", "2023-06-11", "2023-06-13", "2023-06-15", "2023-06-17", "2023-06-19", "2023-06-21", "2023-06-23", "2023-06-25", "2023-06-27", "2023-06-29", "2023-07-01", "2023-07-03", "2023-07-05", "2023-07-07", "2023-07-09", "2023-07-11", "2023-07-13", "2023-07-15", "2023-07-17", "2023-07-19", "2023-07-21", "2023-07-23", "2023-07-25", "2023-07-27", "2023-07-29", "2023-07-31",]
  },
  "Succeeded": true,
  "Error": null
}

note

To help our customers we deduplicate overlapping composite areas within the same month, meaning if you have a tile or minitile order and a composite order that overlap, the part of the composite order that overlaps, will not be billed. The estimate endpoint does not account for this.

Create the Order

If the estimate endpoint returns acceptable numbers, we can continue with creating the actual order. We can use the same payload we used in the estimate for our order creation, using a different endpoint:

Order endpoint: POST /api/tasking/orders

Example estimate response:

{
  "Data": {
    "TaskOrderGuid": "c3528462-02fc-4301-bb37-8d226b45f149",
    "BillingCycle": "Monthly",
    "OrderingProcessStatus": "Initialize",
    "StorageMonths": 2,
    "ApiRequests": 2,
    "TaskOrderAreaKm2": 525.3,
    "SatelliteConstellations": [
        "Sentinel1",
        "Sentinel2",
        "Landsat89"
        ],
    "Model": "Stratus2",
    "ImageFrequency": 2,
    "ReferenceDate": "2023-06-01",
    "From": "2023-06-01",
    "To": "2023-07-31",
    "Tiles": [ ],
    "MiniTiles": [ ],
    "Wkt": "GEOMETRYCOLLECTION (POLYGON ((8.675127 55.962046, 8.675127 55.963407, 8.679411 55.963407, 8.679411 55.962046, 8.675127 55.962046)), POLYGON ((8.472053 56.105382, 8.472053 56.337398, 8.948552 56.337398, 8.948552 56.105382, 8.472053 56.105382)), POLYGON ((8.678 55.948533, 8.678 56.068376, 8.878589 56.068376, 8.878589 55.948533, 8.678 55.948533)))"
  },
  "Succeeded": true,
  "Error": null
}

You can see an description of all request body parameters for estimate and order endpoints on api.clearsky.vision.

Estimate Order Cost​

Create the Order​

Estimate Order Cost

Create the Order