Changelog for June 27, 2024

  • POST tasking/v1/tasks endpoint — the createTask operation request now takes an optional eula parameter to select the end user license agreement (EULA) that applies to the tasking products. For details, see EULA.

  • GET tasking/v1/price endpoint — the getPrice operation request now takes a required eula parameter to select the end user license agreement (EULA) that applies to the tasking products. For details, see EULA.

  • GET company/v1/contracts/{contractID} and GET company/v1/contracts endpoints — the response to a getContract operation or a listContracts operation now includes the applicable EULA value in the eula property.

  • GET tasking/v1/tasks/{taskID} and GET tasking/v1/tasks endpoints — the response to a getTask operation or a listTasks operation now includes the applicable EULA value in the eula property.

  • GET tasking/v1/tasks/{taskID} and GET tasking/v1/tasks endpoints — the response to a getTask operation or a listTasks operation now includes a list of deliveryLocations.

  • All endpoints — the ICEYE Constellation API Suite (ICAS) now incorporates a validation framework that checks all incoming requests to make sure that they conform to the API specifications. In particular:

    • If any required parameters are missing, an HTTP 400 error is returned.

    • If any unknown parameters are provided (could also be caused by mis-spelling a parameter), an HTTP 400 error is returned.

    • If a parameter value is missing or does not conform to the API specification, an HTTP 400 error is returned.