2 minutes to read
In this article
You can create a Content Delivery Network node by using the API.
Configurations that are created for endpoints are not immediately available.
To ensure that the custom domain name and ICP number that you entered match and are valid, you must first review them. This process can take up to one business day to complete. If the details do not pass the Internet Content Provider (ICP) review, delete the Content Delivery Network endpoint you created, and then create a new endpoint by using the correct custom domain name and ICP number. If the details do pass the ICP review, the Content Delivery Network service will be registered within 60 minutes, so that the network can propagate it. At the same time, you must also configure the CNAME mapping details, as indicated by the notifications in the interface, before the cache content can finally be accessed via the custom domain name.
Subscription unique identifier
Required. Enter the current UTC request time in yyyy-MM-dd hh:mm:ss format.
Required. Refer to
CDN API signing mechanism for authorization headers.
To create a Content Delivery Network node, specify the following parameters. An example JSON file is provided here:
Accelerated domain names
Return-to-source host header
ICP record number
Return-to-source address collection
Web: Web page acceleration
Download: Download acceleration
VOD: On-demand acceleration
LiveStreaming: Live-streaming acceleration
ImageProcessing: Image-processing acceleration
A response comprises a status code, response headers, and a response body.
Indicates that the server has successfully accepted the request.
General response indicating that an error has occurred.
The request’s unique identifier, which is used to track request information.
JSON example for request succeeded:
Node unique identifier
NotSet: State not set
Processing: Currently processing
ICP record verification information
IcpVerifying: Currently being verified
IcpVerifyFailed: Verification has failed
IcpVerified: Verification has succeeded
CreationFailed: Creation failed
Indicates whether the accelerated domain name CNAME record is already configured.
Indicates whether the trial period has expired.
Time of last update.
JSON example for request failed:
"Message": "Missing authorization header."
CredentialInvalid: Invalid credentials
ParameterMissing: Parameter missing
ParameterInvalid: Invalid parameter
MissingAuthorizationHeader: Authorization header missing
InvalidRequestDateHeader: Invalid request date header
MissingRequestDateHeader: Missing request date header
AuthorizationHeaderExpired: Authorization header expired
InvalidAuthorizationHeader: Invalid authorization header
ApiKeyNotFound: API key not found
InvalidApiKey: Invalid API key
WrongSignature: Wrong signature
SubscriptionNotFound: Subscription does not exist
EndpointDoesNotBelongToSubscription: Endpoint does not belong to subscription
EndpointNotInActiveState: Endpoint not in active state
EndpointNotFound: Endpoint does not exist
MaliciousItemPathDetected: Malicious item path detected
PermissionDenied: Insufficient permissions
RequestThrottled: Request throttled