Processing / Download Endpoints

Use this page as the endpoint map for data retrieval and processing-unit estimation.

This page is intentionally compact. For workflow choices, use Download with the API.

Before You Start

• Confirm your API key and headers: Authentication.
• Confirm the target date is available before processing: Availability endpoints.
• Keep schema-level details in OpenAPI, and use Download with the API for end-to-end flow decisions.

Minimal Request Example

Recommended sequence:

1. POST /api/satelliteimages/process/composite/available
2. POST /api/satelliteimages/process/composite/estimate
3. POST /api/satelliteimages/process/composite

Minimal composite process call (single-date geometry request):

curl -X POST "https://api.clearsky.vision/api/satelliteimages/process/composite" \
  -H "x-api-key: $CLEARSKY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "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",
    "Resolution": 10,
    "EpsgProjection": 32632,
    "Model": "Stratus2",
    "SatelliteConstellations": ["Sentinel1", "Sentinel2", "Landsat89"],
    "Bandnames": "rgb"
  }'

Endpoint index:

• POST /api/satelliteimages/process/composite/available
• POST /api/satelliteimages/process/composite/estimate
• POST /api/satelliteimages/process/composite
• POST /api/satelliteimages/process/tile
• POST /api/satelliteimages/process/minitile

Common Failure and Fix

• Failure: 400 when geometry mode is invalid or incomplete.
• Fix: send one geometry mode per request (Wkt or GeoJson) and keep estimate/process payload settings aligned.

Operational reliability baseline:

• Retry 429 and 5xx with exponential backoff and jitter.
• Do not blindly retry 400; fix the request payload first.
• For 401/403, verify key validity, scope, and account context.

Next Step

• Implement the full retrieval flow in Download with the API.
• Use CRS / EPSG / UTM guidance for projection decisions.