Skip to main content

Availability Endpoints

Use availability endpoints to prevent avoidable download failures and to gate automation reliably.

Availability checks answer two different questions:

  • Which dates exist for an AOI/time window?
  • Is one exact single-date request currently fulfillable?

Before You Start​

  • Confirm authentication and base URL: Authentication.
  • Prepare the same model/constellation/AOI settings you will later send to estimate and process.
  • Use API reference/OpenAPI for endpoint contracts, and Check availability for operational usage patterns.

Minimal Request Example​

Date discovery request (POST /api/satelliteimages/search/available):

{
  "Wkt": "POLYGON((9.87 56.47,10.19 56.47,10.19 56.28,9.87 56.28,9.87 56.47))",
  "From": "2025-04-01T00:00:00Z",
  "To": "2025-04-30T23:59:59Z",
  "SatelliteConstellations": ["Sentinel1", "Sentinel2", "Landsat89"],
  "Model": "Stratus2"
}

Single-date fulfillability check (POST /api/satelliteimages/process/composite/available):

{
  "Wkt": "POLYGON((9.87 56.47,10.19 56.47,10.19 56.28,9.87 56.28,9.87 56.47))",
  "Date": "2025-04-03T00:00:00Z",
  "Model": "Stratus2",
  "SatelliteConstellations": ["Sentinel1", "Sentinel2", "Landsat89"],
  "EpsgProjection": 32632,
  "Bandnames": "rgb"
}

Recommended call sequence:

  1. Discover candidate dates with POST /api/satelliteimages/search/available.
  2. Validate exact single-date fulfillment with POST /api/satelliteimages/process/composite/available.
  3. Use the same validated request shape for estimate and process.

Common Failure and Fix​

  • Failure: availability check passes, but estimate or process fails.
  • Fix: ensure both calls use the same request settings (date, AOI mode, model, constellations, and output-affecting fields).

If settings drift between calls, rerun availability with the final payload shape.

Next Step​