We're updating the API path structure for several Sentinel Hub APIs on the Copernicus Data Space Ecosystem. The new path formats will be gradually rolled out starting Tuesday, March 17th over the following week.
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
What's changing
API endpoints now support an additional format alongside the existing paths:
- Legacy format: /api/<version>/<service>
- New format /<service>/<version>
| Legacy format | New format |
| /api/v1/process | /process/v1 |
| /api/v1/async | /async/v1 |
| /api/v1/statistics | /statistics/v1 |
| /api/v1/statistics/batch | /statistics/batch/v1 |
| /api/v2/batch | /batch/v2 |
| /api/v1/catalog/1.0.0 | /catalog/v1 |
| /api/v1/zarr | /zarr/v1 |
| /api/v1/byoc | /byoc/v1 |
Impact
- Both path formats will continue to work - No immediate action is required from API consumers
- Response links will use the new format - Services that return self-referential links (such as Catalog, BYOC, Zarr and Batch APIs) will return URLs using the new path structure
- No breaking changes now - All existing integrations will continue to function normally
- Legacy paths will be deprecated - The /api/<version>/<service> format will be deprecated for these APIs in the future. A deprecation timeline will be announced separately.
Action required
None at this time.
We're rolling this out gradually starting Tuesday, March 17th. Please do not make any changes to your integrations at this time. Both the current and the new additional URL formats will be supported.
We're announcing this change in advance for transparency and to answer any questions you may have.
Questions
If you have questions about this change, please post them in the Copernicus Data Space Ecosystem APIs forum.
