Release openEO API v1.3.0

[m-mohr]

Background

We've collected improvements and useful new features since mid-2023. This publishes clarifications and improvements to the public.

You can review the changes at Open-EO/openeo-api#582.

The following changes have been made to the API in detail:

Added

• New extensions:
  • Remote Process Definition Extension
  • Processing Parameters Extension
  • Workspaces Extension
• GET /: New relation type web-editor #577
• GET /credentials/oidc: Added authorization_parameters property to enforce specific parameters for the authorization endpoint #534
• POST /result: Added response header "OpenEO-Identifier" to expose an identifier associated with a synchronous processing request.
• Added stacktrace to log entries (e.g. for GET /jobs/{job_id}/logs) #512
• Added version property to GET /processes #517
• Added queued, started and unpublished to the batch job metadata and the corresponding STAC results #542
• Added a status diagram that explains the status changes of batch jobs #436
• Added all the batch job timestamps (including the new timestamps above) to the Collection type of batch job results
• Support for standard JSON Web Tokens (JWT) being used as Bearer tokens #558

Deprecated

• Deprecated the openEO-specific Bearer token format (authentication mechanism/provider id/access token) #558
• STAC 0.9.x

Changed

• Migrate from openEO-specific tokens to JWT, i.e. deprecating the openEO-specific format in favor of JWT #558
• GET /: Requires the fields type and conformsTo
• GET /udf_runtimes: Requires at least one UDF runtime to be provided. #511
• Updated Federation Extension to v0.2.0

Fixed

• GET /conformance: Added missing security definitions
• GET /file_formats: Base parameter on top of normal JSON Schema, not Process JSON Schema
• PATCH /services/{service_id} and PATCH /jobs/{job_id}: Explicitly allow updating back-end specific properties (as in POST)
• GET /services/{service_id} and GET /jobs/{job_id}: Explicitly allow listing back-end specific properties (as provided in POST)
• GET /jobs/{job_id}/results: Clarify that signed URLs (used as "canonical" link) should be regenerated each time.
• GET /jobs/{job_id}/results: Clarify that "canonical" job result link should include/encode the original query parameters
• Clarified for log levels which default values apply
• Clarified how the relation types license, version-history and author can be used to enrich the process metadata. #531
• Clarified the behaviour of federation:backends for POST /validation
• Clarified the meaning of expires in batch job results
• Clarified that last_successful_check (from Federation Extension) can be null.
• Clarified the relation between result and end nodes, the usage of the result flag, and the relation between the outermost ("root") and child process graphs #547
• Fixed various OpenAPI issues reported by redocly lint

Proposal

I'm proposing to release openEO API 1.3.0 in February 2026.

Depending on when reviews come in, we may still add Open-EO/openeo-api#581 to the release.
I'll inform you here if any additional changes come in until we approved the release here.

Additional context

Deadline: February 2, 2026

[m-mohr]

+1

[jdries]

+1

[mkadunc]

+1

[edzer]

+1