Deletes an edge CNAME.
Upon deleting an edge CNAME, it is strongly recommended to either point the corresponding CNAME record away from our CDN service or remove that record from the DNS zone. This best practice is designed to reduce your risk exposure.
A request to delete an edge CNAME is described below.
HTTP Method | Request URI |
---|---|
DELETE |
https://api.edgecast.com/v2/mcc/customers/AccountNumber/cnames/EdgeCNAMEID |
Define the following variable when submitting the above request.
VariableA variable represents a value that must be replaced. A variable consists of either a URL segment (e.g., "0001" in /0001/) or a query string value (e.g., "3" in mediaTypes=3). | Description |
---|---|
Required |
|
Required |
Replace this variable with the ID of the edge CNAME that should be deleted. A list of edge CNAME configurations and their corresponding system-defined IDs can be retrieved through the following endpoints: |
This endpointIdentifies a request's connection point to our REST API service. only takes advantage of common request headers.
Request body parameters are not required by this endpoint.
The response to the above request includes an HTTP status code, response headers, and a response body.
A status code indicates whether the request was successfully performed.
The response for this endpoint only includes standard HTTP response headers.
The response body for a successful request does not contain a response parameter.
The response body for an unsuccessful request may contain an error parameter that provides additional information.
The request format is identical for both JSON and XML. A sample request is shown below.
DELETE https://api.edgecast.com/v2/mcc/customers/0001/cnames/123456 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Host:api.edgecast.com
The response is identical for both JSON and XML. A sample response is shown below.
HTTP/1.1 200 OK
Cache-Control: private
Date: Thu, 15 Apr 2021 12:00:00 GMT