j1.3.0
API Overview
The Content Delivery Network (CDN) API is for managing the embedded CDN (eCDN) that is included with Commerce Cloud and configured with Business Manager.
Use the API to:
- Ensure that traffic doesn’t circumvent proxies layered in front of your eCDN.
- Accelerate the delivery of resources to users with caching, compression, and prioritization.
- Customize how users interact with resources and how requests are processed, including custom pages and routing rules.
- Provide proactive and complete application protection against new and existing exploits from bad actors.
Authentication & Authorization
For resource access, you must use a client ID and client secret from Account Manager to request an access token. The access token is used as a bearer token and added to the Authorization header of your API request.
The API client must also have at least one of the following OAuth scopes: sfcc.cdn-zones or sfcc.cdn-zones.rw.
For detailed setup instructions, see the Authorization for Admin APIs guide.
You must include the relevant scope(s) in the client ID used to generate the token. For details, see the Authorization Scopes Catalog.
Response Details
Timeouts
Admin API requests must respond within 60 seconds. If a response exceeds this threshold, an HTTP 504 status code is returned. For details, see Timeouts and Limits.
Error Handling
Error responses follow the RFC 7807 problem detail format. To trace errors, include a correlation-id header in your request — the response returns it as x-correlation-id. For details, see HTTP Status Codes and Errors.
Use Cases
For detailed usage information, refer to the CDN Zones Guides.
Let us know so we can improve!