Changelog for February 17, 2026

Simplified Incidence Angle handling for future satellite generations

As ICEYE continues expanding and upgrading our satellite constellation, we’re introducing an improvement to how ICAS handles incidence angles. This update makes it easier to task across multiple satellite generations while maintaining optimal imaging performance.

What’s changing

Previously, incidence angles were defined only as numeric values (integers) in both query and response parameters, for example:

"incidenceAngle": {
  "min": 10,
  "max": 42
}

Starting now forward, the incidenceAngle.min and incidenceAngle.max fields in the Tasking API will also support two new string values:

  • FULL_RANGE — optimizes for fastest possible acquisition

  • PERFORMANT — optimizes for the highest image quality

This allows the system to automatically adapt to the capabilities of each satellite generation without requiring you to manually adjust numeric ranges.

Details

To simplify integration across satellite generations, the incidenceAngle.min and incidenceAngle.max fields in the Tasking API now accept both numeric and string values.

Endpoints impacted:

  • POST /tasking/v2/feasibility

  • POST /tasking/v2/tasks

  • GET /tasking/v2/tasks/{taskID}

  • GET /tasking/v2/tasks