All other tool changes remain unsupported on hosting subscriptions, since they could produce files incompatible with the existing data collection. As with any subscription update, the change applies only to future deliveries.

New Features

• Configure auto-delivery on order create with a nested delivery.destination block containing a ref and an optional path_prefix, matching the Orders API shape. Use pl:destinations/default to deliver to your organization's default destination.

"delivery": {
  "destination": {
    "ref": "pl:destinations/my-s3-destination-CKxV9io",
    "path_prefix": "planet-scenes"
  }
}

• Organize delivered assets with an optional path_prefix:
  • Allowed characters: letters (Unicode included), digits, and _ - . / +.
  • A forward slash (/) is treated as a folder; cannot be at the start or end.
  • Maximum 128 bytes (UTF-8).
• Redelivery requests to /v2/delivery-tasks/ accept the same nested delivery block. Omit it to inherit the original delivery task's destination and prefix; supply it to override either or both. Uniqueness is now enforced on the (destination, path_prefix, assets, capture) tuple, so redelivering to the same destination with a different prefix is allowed.
• DeliveryTask responses now expose pl_ref and path_prefix alongside the existing delivery_destination_id.
• The Tasking Dashboard delivery component (order entry and Deliver Again modal) now includes a "Path prefix (optional)" input. Detail views show the path prefix alongside the destination when set.

Breaking Changes

The flat auto_delivery_destination_id (on orders) and delivery_destination_id (on redelivery) fields are deprecated and will be removed in a future version. Use the nested delivery.destination.ref shape instead. Supplying both shapes with conflicting values will be rejected.

Affected services:

• Processing API
• Asynchronous Processing API
• Statistical API
• Batch Statistical API
• Batch Processing API
• Catalog API
• Zarr Import API
• Bring Your Own COG (BYOC) API

Impact

• Both old and new URL formats continue to work with no breaking changes.
• Response links from services now use the new path format.
• We updated documentation to reflect the new path format.

Deprecation Notice

The legacy /api// format will be deprecated in the future. We recommend migrating your integrations to the new format soon.

A null value means backfill is in progress or not applicable (e.g. forwardfill subscriptions), while a timestamp marks its completion (UTC). This allows workflows to check backfill status without relying on webhook notifications.

For detailed information about how suspension and reactivation works, see the Suspension and Reactivation section in the Subscriptions API documentation.

Announcements 📣

Future quarterly updates to Forest Carbon Monitoring will happen on the last day of the month for each quarter, as usual. However, since these are scheduled and automated, there will no longer be a post to this changelog. The changelog will still be used for important changes or version releases to Forest Carbon Monitoring.

Support has been added to v3.3.0 of the Planet SDK.

The geometry relation will now always be returned in the subscription source (for catalog subscriptions). Subscriptions created before this release will be populated with intersects as that is the historical and default behavior.

Support has been added to v3.4.0 of the Planet SDK.

The following Soil Water Content 1000m v4.0 and Vegetation Optical Depth 1000m v4.0 resources were deprecated on November 1, 2025:

Soil Water Content 1000m v4.0 (soil_water_content_1000m layer):

• SWC-AMSRE-C_V4.0_1000
• SWC-AMSRE-X_V4.0_1000
• SWC-AMSR2-C_V4.0_1000
• SWC-AMSR2-X_V4.0_1000
• SWC-SMAP-L_V4.0_1000

Vegetation Optical Depth 1000m v4.0 (vegetation_optical_depth_1000m layer):

• VOD-AMSRE-C_V4.0_1000
• VOD-AMSRE-X_V4.0_1000
• VOD-AMSR2-C_V4.0_1000
• VOD-AMSR2-X_V4.0_1000
• VOD-SMAP-L_V4.0_1000

All running subscriptions have since been completed, and no new subscriptions can be created.

These legacy resources have been superseded by v5.0 resources, which offer improved accuracy.

The following Soil Water Content 100m v1.0 resources in the soil_water_content_100m layer were deprecated on October 1, 2025:

• SWC-AMSR2-C_V1.0_100
• SWC-AMSR2-X_V1.0_100
• SWC-SMAP-L_V1.0_100

All running subscriptions have since been completed, and no new subscriptions can be created.

These resources have been superseded by v2.0 resources, which offer improved accuracy.