VDMS Web Services REST API Guide PDF
VDMS Web Services REST API Guide PDF
Trademark Information
VERIZON is a registered trademark of Verizon.
Introduction
Our Web Services REST API provides the means through which you can extend your own
technologies with the capabilities of our CDN. This allows you to programmatically integrate our
CDN with other programs, interfaces, or applications for the purpose of automating the manner
through which your media is managed.
Our Web Services consist of a REST-compliant API that operates through HTTPS requests and
responses. The HTTPS request and response bodies must be formatted using either JavaScript
Object Notation (JSON) or Extensible Markup Language (XML). This type of framework allows
you to use your preferred programming language (e.g., C#, C, PHP, Perl, etc.) to perform
operations on our CDN through HTTPS requests to a Web Services REST API server.
The security of the communication between your application and a Web Services REST API
server is ensured through Secure Sockets Layer (SSL) encryption. The Web Services REST API also
protects against unauthorized operations through a user account-specific token.
Change History
A summary of the major changes performed to this document can be viewed from the REST API
Help Center at:
• What's New?
Important: An administrative user determines whether a unique Web Services REST API token
will be available on your user account. If you are denied REST API access, then you will be unable
to view or generate a Web Services REST API token.
The Web Services REST API token is a unique 32 digit alphanumeric value that identifies a MCC
user account. The Web Services REST API server will perform the requested action through the
MCC user account associated with the specified token. This ensures that only operations that
have been authorized for that MCC user account can be performed.
Sample Token Value: 12345678-1234-1234-1234-1234567890ab
Important: The set of operations that can be performed through your Web Services REST API
token is determined by your CDN administrator. A 403 Forbidden will be returned when you
attempt to perform an operation that has not been authorized for the specified token.
Token Generation
The first step towards authenticating a request is to generate a Web Services REST API token.
This type of token can be viewed and generated from the Web Services REST API section of the
My Settings page in the MCC.
Note: The Web Service REST API Token section will only appear on the My Settings page if your
CDN administrator has granted your account access to the REST API.
Tip: It is highly recommended that the backup token only be used to transition your existing
applications to the new primary token.
By default, a primary token is assigned to each MCC user account. At any time, a user may
choose to generate a new primary token. Generating a new primary token will automatically
assign the old primary token as the backup token. This allows your existing applications to
authenticate to our Web Services REST API server, while you update your code to reflect the
new primary token. Once you have updated all of your applications, you can delete the backup
token.
Note: Keep in mind that the value associated with a backup token is automatically deleted when
a new primary token is generated. Once a value has been cleared from the backup token, it can
no longer be used to authenticate to the Web Services REST API server.
Before you can set up request authentication, you will need to know the Web Services REST API
token that has been assigned to your MCC user account. You can view this token value from the
My Settings page in the MCC. You will then need to set the Authorization request header to this
token value. When setting the Authorization request header, you will need to prepend "TOK:" to
your token value. Sample values for the Authorization request header are shown below.
TOK:12345678-1234-1234-1234-1234567890ab
tok:12345678-1234-1234-1234-1234567890AB
Note: As you can tell from the above samples, the term "TOK:" and the token value are not case-
sensitive.
Note: If an invalid token value is included in your request, then a "403 Forbidden" HTTP status
code will be returned. The response body will indicate that an invalid user was specified. For
• HTTP method
• Request URL
HTTP Method
HTTP method is a critical component of a request to our REST API service as it determines the
type of action being requested.
Warning: A 405 Method Not Allowed response will be served when the HTTP method submitted
with a request to our REST API service is unsupported.
Request URL
The URL for a request to a REST API service follows the basic pattern defined below:
https://api.edgecast.com/v2/service/path/resource?parameters
Sample request:
https://api.edgecast.com/v2/mcc/customers/0001/edge/purge
https://api.edgecast.com/v2/reporting/customers/0001/bytestransferred?begindate=2015
-06-01&enddate=2015-07-01
Request headers provide information about your request to our Web Services REST API server.
This information allows our server to authenticate your request and provides information that
allows it to receive and translate the request body.
Important: The use of a Byte Order Mark (BOM) in a request to the REST API is not supported.
Keep in mind that some user agents are configured to automatically include a BOM. Please
either configure the user agent to exclude the BOM or use a different user agent.
Accept This header should indicate the format in which the response will be
returned. Valid values for JSON and XML are listed below.
• JSON: Application/JSON
• XML: Application/XML
Content-Type This header should indicate the format of the request body. Valid values
for JSON and XML are listed below.
• JSON: Application/JSON
• XML: Application/XML
Note: If an endpoint does not have request parameters, then this header
can be omitted.
Host This header, which is set by the user agent, indicates the following host
name:
api.edgecast.com
Content-Length This header, which is set by the user agent, indicates the number of bytes
contained in the request body.
PUT and POST requests typically require request body parameters that describe the action that
will take place. These request body parameters are case-sensitive.
Response Headers
Response headers provide information about the response to your request to our Web Services
REST API server. A brief description is provided for the response headers that are returned by
most endpoints. Standard HTTP response headers are typically returned along with these
common response headers.
Error Reporting
The format for error reporting varies by whether the endpoint pertains to the Defend product.
Note: XML schema errors are automatically rejected by the Web Services REST API server. As a
result, a generic error message is returned as the response body instead of the "Message"
response element.
{"Message":"Access Denied"}
<Error xmlns="http://www.whitecdn.com/schemas/apiservices/"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<Message>Access Denied</Message>
</Error>
https://api.edgecast.com/v2/mcc/customers/0001/waf
https:// api.edgecast.com /v2/mcc/customers/0001/defend
The response body for an error contains the following response elements:
Note: Certain types of errors (e.g., 405 Method Not Allowed) may return a web page describing
the error message (e.g., Method not allowed.) instead of the response described above.
{
"errors" : [{
"message" : "Invalid date range, beginning date too old: 2014-
11-08 00:00:00 < 2015-05-04 20:37:53",
"code" : 400
}
]
}
As previously mentioned, a 200 OK status code indicates that the operation was successfully
carried out. This means that the operation was processed by our servers and the proper
response was returned. However, the proper response may be an empty response body. For
example, updating an object (i.e, PUT request) will typically return an empty response body.
Note: If the request URI for an endpoint requires the identification of a customer, then an
invalid account number or custom ID will result in a 400 Bad Request.
Note: GET requests set to an invalid object ID will either return a 200 OK with an empty object
or a 400 Bad Request.
Error Messages
A list of common errors and their corresponding HTTP status codes is provided below.
Account Status
A customer's account status determines the type of operations that can be performed on it.
There are four different types of customer account statuses, which are active, inactive,
suspended, and trial. The type of operations that can be performed for each customer account
status is described below.
Note: Your account status is determined by your CDN account manager. If you suspect that your
account has been mistakenly been suspended or marked as inactive, please contact your CDN
account manager.
Name Description
Bold Text Non-bulleted bold text indicates a reference to a section or chapter
heading.
• Bold text: The significance of bulleted bold text depends on the context in which it
appears. The most common usages are listed below.
• Identifies a term in the request URI.
• Identifies a valid value for a request parameter.
• Identifies a return value for a response parameter.
Italic Text Italic text identifies a term that should be replaced with a valid value.
Typically, this type of term appears in the request URI.
Parameter Purple bold font is used to indicate that a request parameter is required.
A valid value must be specified for a required request parameter.
Parameter Gray bold font is used to indicate that a request URI, a request
parameter, or a return parameter has been designated as legacy. It is
highly recommended to avoid using a legacy URI, request parameter, or
return parameter.
Field A sample request or response is indicated by a gray block of text.
Overview
CDN management endpoints allow you to perform basic tasks that affect how users access your
content.
Cache Management
An asset can be cached or purged from all of our POPs. These tasks can be performed through
the Load Content and the Purge Content endpoints.
Submits a bulk load that defines the content that will be loaded. Loading content caches an
asset on our edge servers. This allows that content to be served directly from the edge of our
network to your users.
Key information:
• There is a default limit of 50 concurrent load requests at any given time. Exceeding this
limit will generate a 400 Bad Request.
All outstanding load requests count towards this concurrent load request limit. This
includes load requests submitted via the MCC, the Load Content endpoint, or the Bulk
Load Content endpoint.
Note: With regards to bulk loads, each specified URL counts as a separate load request.
For example, each element defined in the MediaPath array of the Bulk Load Content
endpoint counts as a separate load request.
• An asset should only be loaded a single time per unique combination of platform and
protocol.
Note: If a load request is limited to a specific region, then an asset should be loaded a
single time per unique combination of platform, protocol, and region.
Request
A request for a bulk load is described below. When submitting this request, you will need to
define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Name Description
EdgeNodeRegionIds An array that defines the set of regions to which the bulk load request
will be applied. Set this parameter to the desired region ID(s). Use a
comma to delimit multiple regions.
Sample value (JSON):
• EdgeNodeRegionIds: [3,4],
Omitting this parameter will apply the load request to the entire
network (i.e., all regions).
A list of platform-specific regions and their corresponding system-
defined IDs can be retrieved through the Get Load/Purge Regions
method.
Important: Although the response for the Get Load/Purge Regions
method includes the POPs (i.e., edge nodes) associated with each
region and their system-defined IDs, the EdgeNodeRegionIds request
parameter only accepts the system-defined IDs for load/purge regions.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Id A string that reports the unique ID assigned to the bulk load request.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 33
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
{
"Id": " 170fe3a9d4c54d012f680f2a"
}
Submits a bulk purge that defines the content that will be purged. Purging content invalidates
the cached version of an asset from our edge servers. By default, the CDN will forward the next
request for that content to the origin server.
Key information:
• There is a default limit of 50 concurrent purge requests at any given time. Exceeding this
limit will generate a 400 Bad Request.
All outstanding purge requests count towards this concurrent purge request limit. This
includes purge requests submitted via the MCC, the Purge Content endpoint, or the Bulk
Purge Content endpoint.
Note: With regards to bulk purges, each specified URL counts as a separate purge
request. For example, each element defined in the MediaPath array of the Bulk Purge
Content endpoint counts as a separate purge request.
• An asset only needs to be purged a single time per platform. The asset will be purged for
all CDN and edge CNAME URLs that point to the purge location, regardless of the
protocol (i.e., http or https) used to reach it.
Note: If the purge request is limited to a specific region, then an asset should be purged
a single time per unique combination of platform and region.
Request
A request for a bulk purge is described below. When submitting this request, you will need to
define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Name Description
EdgeNodeRegionIds An array that defines the set of regions to which the bulk purge request
will be applied. Set this parameter to the desired region ID(s). Use a
comma to delimit multiple regions.
Sample value (JSON):
• EdgeNodeRegionIds: [3,4],
Omitting this parameter will apply the purge request to the entire
network (i.e., all regions).
A list of platform-specific regions and their corresponding system-
defined IDs can be retrieved through the Get Load/Purge Regions
method.
Important: Although the response for the Get Load/Purge Regions
method includes the POPs (i.e., edge nodes) associated with each
region and their system-defined IDs, the EdgeNodeRegionIds request
parameter only accepts the system-defined IDs for load/purge regions.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Id A string that reports the unique ID assigned to the bulk purge request.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 33
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
{
"Id": " 170fe3a9d4c54d012f680f2a"
}
Request
A request to retrieve a bulk load request is described below. When submitting this request, you
will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• BulkLoadID: Replace this term with an integer that identifies a bulk load request by its
ID. This ID is returned by the Bulk Load Content endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
Status_Details An object that provides information about the bulk load request.
Count An integer that indicates the number of load requests defined in
the bulk load request. Each element defined in the MediaPath array
of the Bulk Load Content endpoint counts as a separate load
request.
Status A string that indicates the status for the load requests defined in
the bulk load request.
Valid values are:
in-progress: Indicates that one or more load requests have
not been completed.
done: Indicates that all load requests have been
completed.
Created_at A string that indicates the date and time at which the bulk load
request was submitted.
Format:
MM\/DD\/YYYY hh:mm:ss AM|PM
Batch_id A string that identifies a bulk load request by its unique ID.
Progress A string that identifies the percentage of load requests that have
been completed.
Completed An integer that indicates the number of load requests that have
been completed.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/edge/bulkload/522e0c33e5671c06c14235e
8 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 227
{
"Status_Details": {
"Count": 50,
"Status": "in-progress",
"Created_at": "10\/20\/2017 8:33:25 PM",
"Completed_at": null,
"Batch_id": "522e0c33e5671c06c14235e8",
"Progress": "0.0",
"Completed": 0
}
}
Request
A request to retrieve a bulk purge request is described below. When submitting this request,
you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• BulkPurgeID: Replace this term with an integer that identifies a bulk purge request by
its ID. This ID is returned by the Bulk Purge Content endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Batch_id A string that identifies a bulk purge request by its unique ID.
Progress A string that identifies the percentage of purge requests that have
been completed.
Completed An integer that indicates the number of purge requests that have
been completed.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/edge/bulkpurge/59ea2a63f4992206a8bfae
28 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 234
{
"Status_Details": {
"Count": 30,
"Status": "in-progress",
"Created_at": "10\/20\/2017 4:54:59 PM",
"Completed_at": null,
"Batch_id": " 59ea2a63f4992206a8bfae28",
"Progress": "0.0",
"Completed": 0
}
}
This method retrieves a list of platform-specific load/purge regions. Load/purge regions may be
used to selectively apply a load or purge request to specific region(s).
The set of available regions varies by platform. This method will respond with all regions that
apply to at least one of the platforms defined in the request.
Request
A request to retrieve a list of load/purge regions is described below. When submitting this
request, you will need to define the following term:
• PlatformIDs: Replace this variable with the ID of each platform for which regions will be
returned. Use a comma to delimit multiple platforms.If multiple platforms are specified,
then the response will include all regions that apply to at least one specified platform.
Valid values are:
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 4091
[{
Request
A request to retrieve a load request is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• LoadID: Replace this term with an integer that identifies a load request by its ID. This ID
is returned by the Load Content endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/edge/load/522e0c33e5671c06c14224d7
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 234
{
"AccountNumber" : "0001",
"CompleteDate" : null,
"Id" : "522e0c33e5671c06c14224d7",
"InDate" : "2016-04-14 19:08",
"MediaPath" : "http:\/\/wpc.0001.edgecastcdn.net\/000001\/WebPage.htm",
"MediaTypeId" : 3,
"Regions" : []
}
Request
A request to retrieve a purge request is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• PurgeID: Replace this term with an integer that identifies a purge request by its ID. This
ID is returned by the Purge Content endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
AccountNumber A string that indicates the CDN account number associated with the
purge request.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/edge/purge/522e0c33e5671c06c14224d7
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 234
{
"AccountNumber" : "0001",
"CompleteDate" : null,
"Id" : "522e0c33e5671c06c14224d7",
"InDate" : "2015-05-08 19:08",
"MediaPath" : "http:\/\/wpc.0001.edgecastcdn.net\/000001\/folder1\/*",
"MediaTypeId" : 3,
"Regions" : []
}
• There is a default limit of 50 concurrent load requests at any given time. Exceeding this
limit will generate a 400 Bad Request.
All outstanding load requests count towards this concurrent load request limit. This
includes load requests submitted via the MCC, the Load Content endpoint, or the Bulk
Load Content endpoint.
Note: With regards to bulk loads, each specified URL counts as a separate load request.
For example, each element defined in the MediaPath array of the Bulk Load Content
endpoint counts as a separate load request.
• An asset should only be loaded a single time per unique combination of platform and
protocol.
Note: If a load request is limited to a specific region, then an asset should be loaded a
single time per unique combination of platform, protocol, and region.
• A short period of time may elapse before an asset is cached across our entire network.
However, a successful request will immediately return an ID in the response. Find out
the current status of your load request(s) by passing this ID to:
Loading via Load Content Endpoint: Get Load Request endpoint
Loading via Bulk Load Content Endpoint: Get Bulk Load Request endpoint
Request
A request to load an asset is described below. When submitting this request, you will need to
define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
MediaPath Required. A string that indicates the CDN or edge CNAME URL for the
asset that will be loaded to our edge servers. Make sure to include the
proper protocol (e.g., http:// or rtmp://).
MediaType Required. An integer that indicates the service for which an asset will
be loaded. It should be replaced with the ID associated with the desired
service. Valid values are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"MediaPath":"http:\/\/wpc.0001.edgecastcdn.net\/000001\/WebPage.htm",
"MediaType":3
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 33
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
{
"Id" : "170fe3a9d4c54d012f680e3c"
}
Purges (i.e., delete) the cached version of an asset from our edge servers.
Key information:
• There is a default limit of 50 concurrent purge requests at any given time. Exceeding this
limit will generate a 400 Bad Request.
All outstanding purge requests count towards this concurrent purge request limit. This
includes purge requests submitted via the MCC, the Purge Content endpoint, or the Bulk
Purge Content endpoint.
Note: With regards to bulk purges, each specified URL counts as a separate purge
request. For example, each element defined in the MediaPath array of the Bulk Purge
Content endpoint counts as a separate purge request.
• An asset only needs to be purged a single time per platform. The asset will be purged for
all CDN and edge CNAME URLs that point to the purge location, regardless of the
protocol (i.e., http or https) used to reach it.
Note: If the purge request is limited to a specific region, then an asset should be purged
a single time per unique combination of platform and region.
• A short period of time may elapse before an asset is cached across our entire network.
However, a successful request will immediately return an ID in the response. Find out
the current status of your purge request(s) by passing this ID to:
Purging via Purge Content Endpoint: Get Purge Request endpoint
Purging via Bulk Purge Content Endpoint: Get Bulk Purge Request endpoint
Request
A request to purge an asset is described below. When submitting this request, you will need to
define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
MediaPath Required. A string that indicates the CDN or edge CNAME URL for the
asset or the location that will be purged from our edge servers. Make
sure to include the proper protocol (i.e., http:// or rtmp://). For
information on how to set the scope of the purge action, please refer
to the Purge Syntax section in Appendix A.
Note: For the purpose of this endpoint, the http:// and https://
protocols are interchangeable.
MediaType Required. An integer that indicates the service for which an asset will
be purged. It should be replaced with the ID associated with the
desired service. Valid values are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Id A string that reports the unique number assigned to the purge
request.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"MediaPath":"http:\/\/wpc.0001.edgecastcdn.net\/000001\/WebPage.htm",
"MediaType":3
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 39
{
"Id" : "522e0c33e5671c06c14224d7"
}
Provides compression setting information for all HTTP platforms. This means that it allows you
to find out the current status of the Compression option and the file types that will be
compressed.
Request
A request to find out compression setting information is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
MediaTypeId An integer that indicates the platform for which compression
setting information will be reported. Valid values for this response
element are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
Status An integer that indicates whether compression has been enabled.
Valid values for this response element are:
• 0: Indicates that compression has been disabled on the
specified platform.
• 1: Indicates that compression has been enabled on the
specified platform.
ContentTypes If the Compression setting has been enabled, then this response
element will contain the set of content types on which compression
will be applied.
a:string A string that indicates a content type on which compression will be
applied.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 231
[{
"MediaTypeId" : 3,
"Status" : 1,
"ContentTypes" : ["text\/plain", "text\/html", "text\/css",
"application\/x-javascript", "text\/javascript"]
}, {
"MediaTypeId" : 8,
"Status" : 0,
"ContentTypes" : [""]
}
]
Returns the value assigned to the Query-String Caching option for all HTTP platforms.
Request
A request to find out query string caching setting information is described below. When
submitting this request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
MediaTypeId An integer that indicates the platform for which query string
caching information is being reported. Valid values for this
response element are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
QueryStringCaching A string that indicates the value associated with the query string
caching setting on the specified platform. Valid values for this
response element are:
• standard-cache: This mode ignores query strings in the URL
when caching assets.
• no-cache: This mode prevents requests containing query
strings from being cached.
• unique-cache: This mode caches an asset for each request
made with a unique URL.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 85
[{
"MediaTypeId" : 3,
"QueryStringCaching" : "unique-cache"
}, {
"MediaTypeId" : 8,
"QueryStringCaching" : "unique-cache"
}
]
Returns the value assigned to the Query-String Logging option for all HTTP platforms.
Request
A request to find out query string logging information is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
MediaTypeId An integer that indicates the platform for which query string
logging information was reported. Valid values for this response
element are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
QueryStringLogging A string that indicates the value associated with the query string
logging setting on the specified platform. Valid values for this
response element are:
• no-log: This mode excludes a URL's query string when
recording CDN activity in a raw log file.
• log: This mode includes a URL's query string when
recording CDN activity in a raw log file.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 85
Provides compression setting information for the specified HTTP platform. This means that it
allows you to find out the current status of the Compression option and the file types that will
be compressed.
Request
A request to find out compression setting information is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• MediaTypeID: This term should be replaced by the ID associated with the desired
platform. Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
MediaTypeId An integer that indicates the platform for which compression
setting information will be reported. Valid values for this response
element are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
Status An integer that indicates whether compression has been enabled.
Valid values for this response element are:
• 0: Indicates that compression has been disabled on the
specified platform.
• 1: Indicates that compression has been enabled on the
specified platform.
ContentTypes If the Compression setting has been enabled, then this response
element will contain the set of content types on which compression
will be applied.
a:string A string that indicates a content type on which compression will be
applied.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/compression?mediatypeid=3
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 149
{
"MediaTypeId" : 3,
"Status" : 1,
"ContentTypes" : ["text\/plain", "text\/html", "text\/css", "application\/x-
javascript", "text\/javascript"]
}
Returns the value assigned to the Query-String Caching option for the specified HTTP platform.
Request
A request to find out query string caching setting information is described below. When
submitting this request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• MediaTypeID: This term should be replaced by the ID associated with the desired
platform. Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
MediaTypeId An integer that indicates the platform for which query string
caching information was reported. Valid values for this response
element are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/querystringcaching?mediatypeid=3
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 85
{
"MediaTypeId" : 3,
"QueryStringCaching" : "unique-cache"
}
Returns the value assigned to the Query-String Logging option for the specified HTTP platform.
Request
A request to find out query string logging information is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• MediaTypeID: This term should be replaced by the ID associated with the desired
platform. Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/querystringlogging?mediatypeid=3
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 85
Updates compression setting information for the specified HTTP platform. This means that it
allows you to set the current status of the Compression option and the file types that will be
compressed.
Request
A request to set compression setting information is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Required and optional parameters are described below.
Name Description
ContentTypes Required. This response element can contain the set of content types on
which compression will be applied.
string A string that indicates a specific content type (e.g., text/plain) on which
compression will be applied.
Note: If you plan on using XML, then you will need to include the following
XML namespace when specifying each content type:
http://schemas.microsoft.com/2003/10/Serialization/Arrays (e.g., <string
xmlns=" http://schemas.microsoft.com/2003/10/Serialization/Arrays ">).
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"ContentTypes" : ["text\/plain", "text\/html", "text\/css", "application\/x-
javascript", "text\/javascript"],
"MediaTypeId" : 3,
"Status" : 1
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Sets the Query-String Caching option for the specified HTTP platform.
Request
A request to set the query string caching setting is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
Name Description
MediaTypeId Required. An integer that determines the platform on which the
query string caching setting will be set. Valid values for this request
parameter are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
QueryStringCaching Required. A case-sensitive string that determines the value that will
be assigned to the query string caching setting on the specified
platform. Valid values for this response element are:
• standard-cache: This mode ignores query strings in the URL
when caching assets.
• no-cache: This mode prevents requests containing query
strings from being cached.
• unique-cache: This mode caches an asset for each request
made with a unique URL.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Sets the Query-String Logging option for the specified HTTP platform.
Request
A request to set the query string logging setting is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
Name Description
MediaTypeId Required. An integer that determines the platform on which the
query string logging setting will be set. Valid values for this request
parameter are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
QueryStringLogging Required. A case-sensitive string that determines the value that will
be assigned to the query string logging setting on the specified
platform. Valid values for this response element are:
• no-log: This mode excludes a URL's query string when
recording CDN activity in a raw log file.
• log: This mode includes a URL's query string when
recording CDN activity in a raw log file.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"MediaTypeId" : 8,
"QueryStringLogging" : "log"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Request
A request to create a customer origin is described below. When submitting this request, you will
need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
Note: The indented parameters indicate that they are a property of the request parameter
directly above it. When submitting a request, you will need to use the proper syntax to indicate
this relationship. Please refer to the parent request parameter for more information.
Note: Hostnames are associated with a customer origin configuration according to the request
type (i.e., HTTP or HTTPS) that they will handle. Although you may choose to define a set of
hostnames for each request type, you are only required to specify a single hostname and load
balancing method for either request type. If you choose to define one or more hostnames, then
you will also need to define the load balancing method for that request type.
Name Description
DirectoryName Required. An alphanumeric string that identifies your customer
origin configuration. It is appended to the end of the base CDN URL
that points to your customer origin server (e.g.,
http://adn.0001.edgecastcdn.net/800001/CustomerOrigin).
FollowRedirects A Boolean that determines whether our edge servers will respect a
URL redirect when validating the set of optimal ADN gateway servers
for your customer origin configuration.
Default value: False
HttpHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTP
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Name Required. A string that determines the hostname/IP address of the
origin server that will be associated with the customer origin
configuration being created.
Use one of the following formats to identify an origin server:
• protocol://hostname:port (e.g.,
http://www.mydomain.com:80)
• protocol://IPv4Address:port (e.g., http://10.10.10.255:80)
• protocol://[IPv6Address]:port (e.g.,
http://[1:2:3:4:5:6:7:8]:80)
HttpsHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTPS
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Important: This request parameter is only available for customers
that have purchased an SSL certificate or the HTTPS feature.
HttpsLoadBalancing Required. A string that determines how HTTPS requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
configuration, then either of the following load balancing methods
will serve requests through that web server.
Valid values for this request parameter are described below.
• PF: This value indicates that "Primary and Failover" mode
will be used to load balance requests for this customer
origin. In this mode, the specified hostnames form an
ordered failover list. All requests will first be sent to the first
hostname in the list. If that server is unavailable (i.e., TCP
connection is refused or a timeout occurs), then the request
will be sent to the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In this
mode, our servers will send a balanced numbers of requests
to each hostname.
Note: The load balancing mode specified for your customer origin
configuration is independent from any load balancing configuration
that may exist at the origin server.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirectoryName" : "MyWebServer",
"HostHeader" : "webapp.mydomain.com:80",
"HttpHostnames" :
[{
"Name" : "http:\/\/webapp1.mydomain.com:80"
}, {
"Name" : "http:\/\/webapp2.mydomain.com:80"
}
],
"HttpLoadBalancing" : "RR",
"HttpsHostnames" :
[{
"Name" : "https:\/\/webapp.mydomain.com:443"
}
],
"HttpsLoadBalancing" : "PF",
"ValidationURL":"http:\/\/webapp.mydomain.com:80\/images\/PerformanceTestObje
ct_5k.gif"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 25
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"CustomerOriginId" : 123456
}
Request
A request to create a customer origin configuration is described below.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Note: The indented parameters indicate that they are a property of the request parameter
directly above it. When submitting a request, you will need to use the proper syntax to indicate
this relationship. Please refer to the parent request parameter for more information.
Note: Hostnames are associated with a customer origin configuration according to the request
type (i.e., HTTP or HTTPS) that they will handle. Although you may choose to define a set of
hostnames for each request type, you are only required to specify a single hostname and load
balancing method for either request type. If you choose to define one or more hostnames, then
you will also need to define the load balancing method for that request type.
HttpHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames/IP addresses. Keep in
mind the following formatting information:
• XML: Each hostname/IP address must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames/IP addresses must be
contained within a set of square brackets. Additionally, each
one (i.e., Name request parameter) must be contained with a
set of curly braces.
Name Required. A string that determines the hostname/IP address of the
origin server that will be associated with the customer origin
configuration being created.
Use one of the following formats to identify an origin server:
• protocol://hostname:port (e.g.,
http://www.mydomain.com:80)
• protocol://IPv4Address:port (e.g., http://10.10.10.255:80)
• protocol://[IPv6Address]:port (e.g.,
http://[1:2:3:4:5:6:7:8]:80)
HttpLoadBalancing Required. A string that determines how HTTP requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
configuration, then either of the following load balancing methods
will serve requests through that web server.
Valid values for this request parameter are described below.
• PF: This value indicates that "Primary and Failover" mode will
be used to load balance requests for this customer origin. In
this mode, the specified hostnames form an ordered failover
HttpsHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames/IP addresses for handling
HTTPS requests. Keep in mind the following formatting information:
• XML: Each hostname/IP address must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames/IP addresses must be
contained within a set of square brackets. Additionally, each
one (i.e., Name request parameter) must be contained with a
set of curly braces.
Important: This request parameter is only available for customers
that have purchased an SSL certificate or the HTTPS feature.
HttpsLoadBalancing Required. A string that determines how HTTPS requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
ShieldPOPs The Origin Shield feature, which must be purchased separately, can
be used to reduce the number of requests that must be handled by
your customer origin server. If you choose to protect your customer
origin with this feature, then you will need to specify each point-of-
presence (POP) location where Origin Shield servers will be used to
provide an intermediate cache layer between our edge servers and
your customer origin.
Specify each desired Origin Shield location as an object containing
the following key-value pair:
'POPCode': "{Origin Shield Location}"
Tip: If you would like to configure the Origin Shield feature to
produce an optimal reduction in requests to your customer origin
server, then you should only specify a single location. The specified
location should be the POP closest to your customer origin server.
Tip: A list of locations can be retrieved through the Get Origin Shield
POPs - HTTP Large endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpHostnames" :
[{
"Name" : "http:\/\/images1.mydomain.com:80"
}, {
"Name" : "http:\/\/images2.mydomain.com:80"
}
],
"HttpLoadBalancing" : "RR",
"HttpsHostnames" :
[{
"Name" : "https:\/\/images.mydomain.com:443"
}
],
"HttpsLoadBalancing" : "PF",
"ShieldPOPs" :
[{
"POPCode" : "LAA"
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 25
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"CustomerOriginId" : 1234
}
Request
A request to create a customer origin is described below. When submitting this request, you will
need to define the following terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Note: The indented parameters indicate that they are a property of the request parameter
directly above it. When submitting a request, you will need to use the proper syntax to indicate
this relationship. Please refer to the parent request parameter for more information.
Note: Hostnames are associated with a customer origin configuration according to the request
type (i.e., HTTP or HTTPS) that they will handle. Although you may choose to define a set of
hostnames for each request type, you are only required to specify a single hostname and load
balancing method for either request type. If you choose to define one or more hostnames, then
you will also need to define the load balancing method for that request type.
HttpHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTP
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Name Required. A string that determines the hostname/IP address of the
origin server that will be associated with the customer origin
configuration being created.
Use one of the following formats to identify an origin server:
• protocol://hostname:port (e.g.,
http://www.mydomain.com:80)
• protocol://IPv4Address:port (e.g., http://10.10.10.255:80)
• protocol://[IPv6Address]:port (e.g.,
http://[1:2:3:4:5:6:7:8]:80)
HttpsHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTPS
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Important: This request parameter is only available for customers
that have purchased an SSL certificate or the HTTPS feature.
HttpsLoadBalancing Required. A string that determines how HTTPS requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
configuration, then either of the following load balancing methods
will serve requests through that web server.
Valid values for this request parameter are described below.
• PF: This value indicates that "Primary and Failover" mode will
be used to load balance requests for this customer origin. In
this mode, the specified hostnames form an ordered failover
list. All requests will first be sent to the first hostname in the
list. If that server is unavailable (i.e., TCP connection is
refused or a timeout occurs), then the request will be sent to
the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In this
mode, our servers will send a balanced numbers of requests
to each hostname.
Note: The load balancing mode specified for your customer origin
configuration is independent from any load balancing configuration
that may exist at the origin server.
Tip: A list of locations can be retrieved through the Get Origin Shield
POPs - HTTP Small endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
CustomerOriginId An integer that indicates the unique ID assigned to this customer
origin configuration.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpHostnames" :
[{
"Name" : "http:\/\/images1.mydomain.com:80"
}, {
"Name" : "http:\/\/images2.mydomain.com:80"
}
],
"HttpLoadBalancing" : "RR",
"HttpsHostnames" :
[{
"Name" : "https:\/\/images.mydomain.com:443"
}
],
"HttpsLoadBalancing" : "PF",
"ShieldPOPs" :
[{
"POPCode" : "OXR"
}
]
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 25
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"CustomerOriginId" : 1234
}
Important: The deletion of a customer origin takes place immediately. Additionally, once a
customer origin has been deleted, it cannot be recovered.
Request
A request to delete a customer origin is described below. When submitting this request, you will
need to define the following terms:
• CustomerOriginID: Replace this term with the ID of the customer origin configuration
that should be deleted.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
The response is identical for both JSON and XML. A sample response is provided below.
HTTP/1.1 200 OK
Cache-Control: private
Date: Mon, 10 Jan 2011 12:00:00 GMT
Request
A request to retrieve a list of the customer origins (ADN) associated with a customer's account is
described below. When submitting this request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
customer origin returned by this endpoint:
Name Description
FollowRedirects A Boolean that indicates whether our edge servers will respect a
URL redirect when validating the set of optimal ADN gateway
servers for your customer origin configuration.
HttpsFullUrl A string that indicates the CDN URL for HTTPS requests to this
customer origin server.
HttpsHostnames This response element contains the hostnames that will handle
HTTPS requests.
IsPrimary This response element indicates whether the current hostname is
the primary one for HTTPS requests. Valid values for this response
element are described below.
• 0: Indicates that the current hostname is not the primary
one. This value will always be reported for the Round-Robin
load balancing mode.
• 1: Indicates that the current hostname is the primary one.
Name This string reports the URL for the current hostname. This URL
consists of the protocol, hostname, and the port.
Ordinal This integer indicates the position in the ordered list for the current
hostname. This position is primarily used by "Primary and Failover"
load balancing mode to determine which hostname will take over
when a hostname higher on the list is unreachable.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 1100
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"FollowRedirects" : true,
"NetworkConfiguration" : 1,
"ValidationURL" :
"http:\/\/socialmedia.mydomain.com\/images\/PerformanceTestObject_5k.gif",
"DirectoryName" : "socialmedia",
"HostHeader" : "socialmedia.mydomain.com",
"HttpFullUrl" :
"http:\/\/adn.0001.edgecastcdn.net\/800001\/socialmedia",
"HttpHostnames" : [{
"IsPrimary" : 1,
"Name" : "http:\/\/socialmedia.mydomain.com:80",
"Ordinal" : 0
}
],
"HttpLoadBalancing" : "PF",
"HttpsFullUrl" : "",
"HttpsHostnames" : [],
"HttpsLoadBalancing" : "",
"Id" : 44764,
"MediaTypeId" : 14
}, {
"FollowRedirects" : true,
"NetworkConfiguration" : 1,
"ValidationURL" : "http:\/\/banking.mydomain.com\/asset.txt",
"DirectoryName" : "banking",
"HostHeader" : "banking.mydomain.com",
"HttpFullUrl" : "http:\/\/adn.0001.edgecastcdn.net\/800001\/banking",
"HttpHostnames" : [{
"IsPrimary" : 1,
"Name" : "http:\/\/banking.mydomain.com:80",
"Ordinal" : 0
Retrieves all customer origin configurations for the HTTP Large platform.
Request
A request to retrieve a list of customer origins (HTTP Large) is described below. When
submitting this request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
DirectoryName A string that indicates the unique identification for your customer
origin configuration. This name is appended to the end of the base
CDN URL that points to your customer origin server (e.g.,
http://wpc.0001.edgecastcdn.net/800001/CustomerOrigin).
HostHeader A string that identifies the IP address/hostname and port
associated with a request.
HttpFullUrl A string that indicates the CDN URL for HTTP requests to this
customer origin server.
HttpHostnames This response element contains the hostnames that will handle
HTTP requests.
IsPrimary This response element indicates whether the current hostname is
the primary one. Valid values for this response element are
described below.
• 0: Indicates that the current hostname is not the primary
one. This value will always be reported for the Round-Robin
load balancing mode.
• 1: Indicates that the current hostname is the primary one.
Name This string reports the URL for the current hostname. This URL
consists of the protocol, hostname, and the port.
Ordinal This integer indicates the position in the ordered list for the current
hostname. This position is primarily used by Primary Failover load
balancing mode to determine which hostname will take over when
a hostname higher on the list is unreachable.
HttpLoadBalancing A string that indicates how HTTP requests will be load balanced for
the specified hostnames. Valid values for this response element are
described below.
• PF: This value indicates that "Primary and Failover" mode
will be used to load balance requests for this customer
origin. In this mode, the specified hostnames form an
ordered failover list. All requests will first be sent to the
first hostname in the list. If that server is unavailable (i.e.,
TCP connection is refused or a timeout occurs), then the
request will be sent to the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In
this mode, our servers will send a balanced numbers of
requests to each hostname.
HttpsFullUrl A string that indicates the CDN URL for HTTPS requests to this
customer origin server.
HttpsHostnames This response element contains the hostnames that will handle
HTTPS requests.
IsPrimary This response element indicates whether the current hostname is
the primary one. Valid values for this response element are
described below.
• 0: Indicates that the current hostname is not the primary
one. This value will always be reported for the Round-Robin
load balancing mode.
• 1: Indicates that the current hostname is the primary one.
Name This string reports the URL for the current hostname. This URL
consists of the protocol, hostname, and the port.
Ordinal This integer indicates the position in the ordered list for the current
hostname. This position is primarily used by Primary Failover load
balancing mode to determine which hostname will take over when
a hostname higher on the list is unreachable.
HttpsLoadBalancing A string that indicates how HTTPS requests will be load balanced for
the specified hostnames. Valid values for this response element are
described below.
• PF: This value indicates that "Primary and Failover" mode
will be used to load balance requests for this customer
origin. In this mode, the specified hostnames form an
ordered failover list. All requests will first be sent to the
first hostname in the list. If that server is unavailable (i.e.,
TCP connection is refused or a timeout occurs), then the
request will be sent to the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In
this mode, our servers will send a balanced numbers of
requests to each hostname.
Note: The load balancing mode indicated for your customer origin
configuration is independent from any load balancing configuration
that may exist at the origin server.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 921
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpFullUrl" :
"http:\/\/wpc.0001.edgecastcdn.net\/800001\/MyCustomerOrigin",
"HttpHostnames" :
[{
"IsPrimary" : 0,
"Name" : "http:\/\/images1.mydomain.com:80",
"Ordinal" : 0
}, {
"IsPrimary" : 0,
"Name" : "http:\/\/images2.mydomain.com:80",
"Ordinal" : 1
}
],
"HttpLoadBalancing" : "RR",
"HttpsFullUrl" : null,
"HttpsHostnames" : [],
"HttpsLoadBalancing" : null,
"Id" : 1235,
"MediaTypeId" : 3,
"ShieldPOPs" : [],
"UseOriginShield" : 0,
"networkConfiguration" : 1
}, {
"DirectoryName" : "documents",
"HostHeader" : "documents.mydomain.com:80",
"HttpFullUrl" : "http:\/\/wpc.0001.edgecastcdn.net\/800001\/documents",
"HttpHostnames" :
[{
Retrieves all customer origin configurations associated with the HTTP Small platform.
Request
A request to retrieve a list of customer origins is described below. When submitting this request,
you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
customer origin returned by this endpoint:
Name Description
DirectoryName An alphanumeric string that identies your customer origin
configuration. This name is appended to the end of the base CDN
URL that points to your customer origin server (e.g.,
http://wac.0001.edgecastcdn.net/800001/CustomerOrigin).
HostHeader A string that identifies the IP address/hostname and port
associated with a request.
HttpFullUrl A string that indicates the CDN URL for HTTP requests to this
customer origin server.
HttpHostnames This response element contains the hostnames that will handle
HTTP requests.
HttpsFullUrl A string that indicates the CDN URL for HTTPS requests to this
customer origin server.
HttpsHostnames This response element contains the hostnames that will handle
HTTPS requests.
IsPrimary This response element indicates whether the current hostname is
the primary one. Valid values for this response element are
described below.
• 0: Indicates that the current hostname is not the primary
one. This value will always be reported for the Round-Robin
load balancing mode.
• 1: Indicates that the current hostname is the primary one.
Name This string reports the URL for the current hostname. This URL
consists of the protocol, hostname, and the port.
Ordinal This integer indicates the position in the ordered list for the current
hostname. This position is primarily used by Primary Failover load
balancing mode to determine which hostname will take over when
a hostname higher on the list is unreachable.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 921
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpFullUrl" :
"http:\/\/wac.0001.edgecastcdn.net\/800001\/MyCustomerOrigin",
"HttpHostnames" :
[{
"IsPrimary" : 0,
"Name" : "http:\/\/images1.mydomain.com:80",
"Ordinal" : 0
}, {
"IsPrimary" : 0,
"Name" : "http:\/\/images2.mydomain.com:80",
"Ordinal" : 1
}
],
"HttpLoadBalancing" : "RR",
"HttpsFullUrl" : null,
"HttpsHostnames" : [],
"HttpsLoadBalancing" : null,
"Id" : 1235,
"MediaTypeId" : 8,
"ShieldPOPs" : [],
"UseOriginShield" : 0,
"networkConfiguration" : 1
}, {
"DirectoryName" : "documents",
"HostHeader" : "documents.mydomain.com:80",
"HttpFullUrl" : "http:\/\/wac.0001.edgecastcdn.net\/800001\/documents",
"HttpHostnames" :
[{
Retrieve a list of IPv4 and IPv6 blocks used by our CDN service.
Tip: Ensure that our CDN may communicate with your web servers by whitelisting these
IP blocks on your firewall.
Request
A request to retrieve a listing of IP blocks is described below.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
SuperBlockIPv4 An array containing string values that identify the IPv4 blocks used
by our CDN service.
SuperBlockIPv6 An array containing string values that identify the IPv6 blocks used
by our CDN service.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 1255
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
Request
A request to retrieve customer origin information is described below. When submitting this
request, you will need to define the following terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
FollowRedirects A Boolean that indicates whether our edge servers will respect a
URL redirect when validating the set of optimal ADN gateway
servers for your customer origin configuration.
NetworkConfiguration An integer that indicates how hostnames associated with a
customer origin configuration will be resolved to an IP address.
Valid values are:
• 1: Default. Indicates that the IP preference for this
customer origin will be system-defined. Currently, this
configuration causes hostnames to be resolved to IPv4
only.
• 2: IPv6 Preferred over IPv4. Indicates that although
hostnames for this customer origin can be resolved to
either IP version, a preference will be given to IPv6.
• 3: IPv4 Preferred over IPv6. Indicates that although
hostnames for this customer origin can be resolved to
either IP version, a preference will be given to IPv4.
• 4: IPv4 Only. Indicates that hostnames for this customer
origin can only be resolved to IPv4.
• 5: IPv6 Only. Indicates that hostnames for this customer
origin can only be resolved to IPv6.
ValidationURL A string that indicates the URL to a sample asset. A set of optimal
ADN gateway servers for your customer origin server is determined
through the delivery of this sample asset.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 507
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"FollowRedirects" : true,
"NetworkConfiguration" : 1,
"ValidationURL" : "http:\/\/banking.mydomain.com\/asset.txt",
"DirectoryName" : "banking",
"HostHeader" : "banking.mydomain.com",
"HttpFullUrl" : "http:\/\/adn.0001.edgecastcdn.net\/800001\/banking",
"HttpHostnames" : [{
"IsPrimary" : 1,
"Name" : "http:\/\/banking.mydomain.com:80",
"Ordinal" : 0
}
],
"HttpLoadBalancing" : "PF",
"HttpsFullUrl" : "",
"HttpsHostnames" : [],
"HttpsLoadBalancing" : "",
"Id" : 123456,
"MediaTypeId" : 14
Request
A request to retrieve customer origin information is described below. When submitting this
request, you will need to define the following terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 453
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpFullUrl" :
"http:\/\/wpc.0001.edgecastcdn.net\/800001\/MyCustomerOrigin",
"HttpHostnames" :
[{
"IsPrimary" : 0,
"Name" : "http:\/\/images1.mydomain.com:80",
"Ordinal" : 0
}, {
"IsPrimary" : 0,
"Name" : "http:\/\/images2.mydomain.com:80",
"Ordinal" : 1
}
],
"HttpLoadBalancing" : "RR",
"HttpsFullUrl" : null,
"HttpsHostnames" : [],
"HttpsLoadBalancing" : null,
"Id" : 1211,
"MediaTypeId" : 3,
"ShieldPOPs" : [],
"UseOriginShield" : 0,
Request
A request to retrieve customer origin information is described below. When submitting this
request, you will need to define the following terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 453
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpFullUrl" :
"http:\/\/wac.0001.edgecastcdn.net\/800001\/MyCustomerOrigin",
"HttpHostnames" :
[{
"IsPrimary" : 0,
"Name" : "http:\/\/images1.mydomain.com:80",
"Ordinal" : 0
}, {
"IsPrimary" : 0,
"Name" : "http:\/\/images2.mydomain.com:80",
"Ordinal" : 1
}
],
"HttpLoadBalancing" : "RR",
"HttpsFullUrl" : null,
"HttpsHostnames" : [],
"HttpsLoadBalancing" : null,
"Id" : 1211,
"MediaTypeId" : 8,
"ShieldPOPs" : [],
"UseOriginShield" : 0,
Note: This endpoint may not be used to retrieve propagation status for customer origin
configurations that were last updated more than 7 days ago.
Request
A request to retrieve status information is described below. When submitting this request, you
will need to define the following terms:
• xxxx: Replace this term with the desired customer account number.
• CustomerOriginID: Replace this term with the system-defined ID for the desired
customer origin configuration.
Use a platform-specific Get All Customer Origins endpoint to retrieve the system-
defined ID for the desired customer origin.
Sample request for the HTTP Large platform:
https://api.edgecast.com/v2/mcc/customers/0001/origins/httplarge
Note: Please refer to the REST API Help Center for more detailed information on this
endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request varies according to the following factors:
• New / Update: The following response will be provided immediately after a customer
origin configuration is created or updated:
{"Status":"New","Percent_propagated":0}
• Existing Configurations: If the customer origin configuration is older than 7 days, then
this endpoint will return a 400 Bad Request with the following response body:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 7718
{
"Status": "propagating",
"Percent_propagated": 8.759656026818249,
"Pops": [{
"name": "South America : Valparaiso, Chile",
This endpoint returns a list of the available Origin Shield locations for the HTTP Large platform.
This list consists of the name, POP code, and region for each POP that can provide Origin Shield
protection to a customer origin server. These abbreviations can then be used to set or to
interpret Origin Shield settings for a customer origin.
Note: This endpoint does not return data for bypass region settings. For information on bypass
region settings, please refer to Appendix E: Origin Shield Locations and Settings.
Request
A request to find out the available Origin Shield locations (HTTP Large) is described below. When
submitting this request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
Origin Shield POP returned by this endpoint:
Name Description
Name A string that indicates the name of the POP location where Origin
Shield servers reside.
POPCode A string that indicates the three-letter abbreviation corresponding to
the POP location identified by the Name request parameter.
Region A string that indicates the region corresponding to the POP location
identified by the Name request parameter.
Tip: The region associated with a POP is relevant when configuring an
origin server to bypass Origin Shield protection on certain regions.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/origins/httplarge/shieldpops
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 1428
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"Name" : "Ashburn",
"POPCode" : "DCA",
"Region" : "US East"
}, {
...
}, {
"Name" : "San Jose",
"POPCode" : "SJC",
"Region" : "US West"
}, {
"Name" : "Osaka",
"POPCode" : "KIX",
"Region" : "Asia"
}
]
This endpoint returns a list of the available Origin Shield locations for the HTTP Small platform.
This list consists of the name, POP code, and region for each POP that can provide Origin Shield
protection to a customer origin server. These abbreviations can then be used to set or to
interpret Origin Shield settings for a customer origin.
Note: This endpoint does not return data for bypass region settings. For information on bypass
region settings, please refer to Appendix E: Origin Shield Locations and Settings.
Request
A request to find out the available Origin Shield locations (HTTP Small) is described below. When
submitting this request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
Origin Shield POP returned by this endpoint:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/origins/httpsmall/shieldpops
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 1428
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"Name" : "Ashburn",
"POPCode" : "DCA",
"Region" : "US East"
}, {
...
}, {
"Name" : "San Jose",
Reselects the set of ADN gateways that will be associated with a customer origin.
Request
A request to reselect ADN gateways is described below. When submitting this request, you will
need to define the following terms:
• CustomerOriginID: This term determines the customer origin that will be updated. It
should be replaced by the ID of the customer origin that you would like to update.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT https://api.edgecast.com/v2/mcc/customers/0001/origins/adn/123456/reselect
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 provided below.
HTTP/1.1 200 OK
Cache-Control: private
Date: Mon, 10 Jan 2011 12:00:00 GMT
Important: Updating a customer origin will overwrite the entire customer origin configuration.
This will occur regardless of whether a request parameter has been excluded from the request.
Note: This endpoint cannot be used to update the directory assigned to a customer origin
configuration that has been associated with an edge CNAME.
Request
A request to update the properties of a customer origin configuration is described below. When
submitting this request, you will need to define the following terms:
• CustomerOriginID: This term determines the customer origin that will be updated. It
should be replaced by the ID of the customer origin that you would like to update.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Note: The indented parameters indicate that they are a property of the request parameter
directly above it. When submitting a request, you will need to use the proper syntax to indicate
this relationship. Please refer to the parent request parameter for more information.
Note: Hostnames are associated with a customer origin configuration according to the request
type (i.e., HTTP or HTTPS) that they will handle. Although you may choose to define a set of
hostnames for each request type, you are only required to specify a single hostname and load
balancing method for either request type. If you choose to define one or more hostnames, then
you will also need to define the load balancing method for that request type.
Name Description
DirectoryName Required. An alphanumeric string that identifies your customer
origin configuration. It is appended to the end of the base CDN URL
that points to your customer origin server (e.g.,
http://adn.0001.edgecastcdn.net/800001/CustomerOrigin).
Important: This setting is read-only for a customer origin
configuration that has been associated with at least one edge
CNAME configuration. For this type of scenario, make sure that this
response element is set to the directory name currently assigned to
the customer origin configuration.
FollowRedirects A Boolean that determines whether our edge servers will respect a
URL redirect when validating the set of optimal ADN gateway servers
for your customer origin configuration.
Default value: False
HostHeader Required. A string that identifies the IP address/hostname and port
associated with a request. A host header is especially useful when
there are multiple virtual domains hosted on a single physical server
or load-balanced set of servers.
Note: A protocol should not be specified when setting this
parameter.
HttpsLoadBalancing Required. A string that determines how HTTPS requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
configuration, then either of the following load balancing methods
will serve requests through that web server.
Valid values for this request parameter are described below.
• PF: This value indicates that "Primary and Failover" mode
will be used to load balance requests for this customer
origin. In this mode, the specified hostnames form an
ordered failover list. All requests will first be sent to the first
hostname in the list. If that server is unavailable (i.e., TCP
connection is refused or a timeout occurs), then the request
will be sent to the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In this
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirectoryName" : "MyWebServer",
"HostHeader" : "webapp.mydomain.com:80",
"HttpHostnames" :
[{
"Name" : "http:\/\/webapp1.mydomain.com:80"
}, {
"Name" : "http:\/\/webapp2.mydomain.com:80"
}
],
"HttpLoadBalancing" : "RR",
"HttpsHostnames" :
[{
"Name" : "https:\/\/webapp.mydomain.com:443"
}
],
"HttpsLoadBalancing" : "PF",
"ValidationURL":"http:\/\/webapp.mydomain.com:443\/images\/PerformanceTestObj
ect_5k.gif"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 0
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
Sets the properties for a customer origin on the HTTP Large platform.
Important: Updating a customer origin will overwrite the entire customer origin configuration.
This will occur regardless of whether a request parameter has been excluded from the request.
Note: This endpoint cannot be used to update the directory assigned to a customer origin
configuration that has been associated with an edge CNAME.
Request
A request to update a customer origin configuration is described below. When submitting this
request, you will need to define the following terms:
• CustomerOriginID: This term determines the customer origin that will be updated. It
should be replaced by the ID of the customer origin that you would like to update.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Note: Indented parameters indicate that they are a property of the request parameter directly
above it. When submitting a request, you will need to use the proper syntax to indicate this
relationship. Please refer to the parent request parameter for more information.
Note: Hostnames are associated with a customer origin configuration according to the request
type (i.e., HTTP or HTTPS) that they will handle. Although you may choose to define a set of
hostnames for each request type, you are only required to specify a single hostname and load
Name Description
DirectoryName Required. An alphanumeric string that identifies your customer origin
configuration. It is appended to the end of the base CDN URL that
points to your customer origin server (e.g.,
http://wpc.0001.edgecastcdn.net/800001/CustomerOrigin).
Important: This setting is read-only for a customer origin
configuration that has been associated with at least one edge
CNAME configuration. For this type of scenario, make sure that this
response element is set to the directory name currently assigned to
the customer origin configuration.
HttpHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTP
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Name Required. A string that determines the hostname/IP address of the
origin server that will be associated with the customer origin
configuration being updated.
Use one of the following formats to identify an origin server:
• protocol://hostname:port (e.g.,
http://www.mydomain.com:80)
• protocol://IPv4Address:port (e.g., http://10.10.10.255:80)
• protocol://[IPv6Address]:port (e.g.,
http://[1:2:3:4:5:6:7:8]:80)
HttpLoadBalancing Required. A string that determines how HTTP requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
HttpsHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTPS
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Important: This request parameter is only available for customers
that have purchased an SSL certificate or the HTTPS feature.
HttpsLoadBalancing Required. A string that determines how HTTPS requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
configuration, then either of the following load balancing methods
will serve requests through that web server.
Valid values for this request parameter are described below.
• PF: This value indicates that "Primary and Failover" mode will
be used to load balance requests for this customer origin. In
this mode, the specified hostnames form an ordered failover
list. All requests will first be sent to the first hostname in the
list. If that server is unavailable (i.e., TCP connection is
refused or a timeout occurs), then the request will be sent to
the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In this
mode, our servers will send a balanced numbers of requests
to each hostname.
Note: The load balancing mode specified for your customer origin
configuration is independent from any load balancing configuration
that may exist at the origin server.
Tip: A list of locations can be retrieved through the Get Origin Shield
POPs - HTTP Large endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpHostnames" :
[{
"Name" : "http:\/\/images1.mydomain.com:80"
}, {
"Name" : "http:\/\/images2.mydomain.com:80"
}
],
"HttpLoadBalancing" : "RR",
"HttpsHostnames" :
[{
"Name" : "https:\/\/images.mydomain.com:443"
}
],
"HttpsLoadBalancing" : "PF",
"ShieldPOPs" :
[{
"POPCode" : "LAA"
}
]
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
Sets the properties for a customer origin on the HTTP Small platform.
Note: This endpoint cannot be used to update the directory assigned to a customer origin
configuration that has been associated with an edge CNAME.
Request
A request to update the properties of a customer origin configuration is described below. When
submitting this request, you will need to define the following terms:
• CustomerOriginID: This term determines the customer origin that will be updated. It
should be replaced by the ID of the customer origin that you would like to update.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Note: The indented parameters indicate that they are a property of the request parameter
directly above it. When submitting a request, you will need to use the proper syntax to indicate
this relationship. Please refer to the parent request parameter for more information.
Note: Hostnames are associated with a customer origin configuration according to the request
type (i.e., HTTP or HTTPS) that they will handle. Although you may choose to define a set of
hostnames for each request type, you are only required to specify a single hostname and load
balancing method for either request type. If you choose to define one or more hostnames, then
you will also need to define the load balancing method for that request type.
HttpHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTP
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Name Required. A string that determines the hostname/IP address of the
origin server that will be associated with the customer origin
configuration being updated.
Use one of the following formats to identify an origin server:
• protocol://hostname:port (e.g.,
http://www.mydomain.com:80)
• protocol://IPv4Address:port (e.g., http://10.10.10.255:80)
• protocol://[IPv6Address]:port (e.g.,
http://[1:2:3:4:5:6:7:8]:80)
HttpsHostnames Required. This response element is only used to indicate that you
plan on specifying one or more hostnames for handling HTTPS
requests. Keep in mind the following formatting information:
• XML: Each hostname must be contained within a
<Hostname> tag.
• JSON: The desired set of hostnames must be contained
within a set of square brackets. Additionally, each hostname
(i.e., Name request parameter) must be contained with a set
of curly braces.
Important: This request parameter is only available for customers
that have purchased an SSL certificate or the HTTPS feature.
HttpsLoadBalancing Required. A string that determines how HTTPS requests will be load
balanced for the specified hostnames. Our servers will use DNS to
resolve the specified hostnames into an ordered list of IP addresses.
If you have only specified a single web server for this origin server
configuration, then either of the following load balancing methods
will serve requests through that web server.
Valid values for this request parameter are described below.
• PF: This value indicates that "Primary and Failover" mode will
be used to load balance requests for this customer origin. In
this mode, the specified hostnames form an ordered failover
list. All requests will first be sent to the first hostname in the
list. If that server is unavailable (i.e., TCP connection is
refused or a timeout occurs), then the request will be sent to
the next hostname.
• RR: This value indicates that "Round Robin" mode will be
used to load balance requests for this customer origin. In this
mode, our servers will send a balanced numbers of requests
to each hostname.
Note: The load balancing mode specified for your customer origin
configuration is independent from any load balancing configuration
that may exist at the origin server.
Tip: A list of locations can be retrieved through the Get Origin Shield
POPs - HTTP Small endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirectoryName" : "MyCustomerOrigin",
"HostHeader" : "images.mydomain.com:80",
"HttpHostnames" :
[{
"Name" : "http:\/\/images1.mydomain.com:80"
}, {
"Name" : "http:\/\/images2.mydomain.com:80"
}
],
"HttpLoadBalancing" : "RR",
"HttpsHostnames" :
[{
"Name" : "https:\/\/images.mydomain.com:443"
}
],
"HttpsLoadBalancing" : "PF",
"ShieldPOPs" :
[{
"POPCode" : "OXR"
}
]
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 25
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
Note: Although Creates an edge CNAME, it will not add a CNAME record on a DNS server. This
step must be performed before content can be requested through the new edge CNAME.
Request
A request to create an edge CNAME is described below. When submitting this request, you will
need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Name Description
DirPath Required. A string that identifies a location on the origin server. This
string should specify the relative path from the root folder of the
origin server to the desired location.
Tip: Set this parameter to blank to point the edge CNAME to the
root folder of the origin server.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DirPath" : "",
"MediaTypeId" : 3,
"Name" : "images.mydomain.com",
"OriginId" : -1
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 19
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"CNameId" : 5
}
Important: 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.
Request
A request to delete an edge CNAME is described below. When submitting this request, you will
need to define the following terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
The response is identical for both JSON and XML. A sample response is provided below.
HTTP/1.1 200 OK
Cache-Control: private
Date: Mon, 10 Jan 2011 12:00:00 GMT
Request
A request to retrieve a list of the edge CNAMEs (ADN) associated with a customer's account is
described below. When submitting this request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
DirPath A string that indicates the relative location on the origin server to
which the edge CNAME is pointed. If this response element is set to
blank, then the edge CNAME points to the root folder of the origin
server.
EnableCustomReports An integer that indicates whether hits and data transferred statistics
are being tracked for this edge CNAME. Logged data can be viewed
through the Custom Reports module.
Valid values for this parameter are:
• 0: Disabled (Default Value).
• 1: Enabled. CDN activity on this edge CNAME is being
logged.
Id An integer that indicates the ID for the edge CNAME.
MediaTypeId An integer that indicates the platform on which the edge CNAME
configuration resides. This response element will always report "14,"
which is the value assigned to the ADN platform.
Name A string that indicates the name assigned to the edge CNAME.
OriginId An integer that indicates the origin server associated with the edge
CNAME. Valid return values are:
• -1: Indicates that the edge CNAME points to a CDN origin
server.
• CustomerOriginID: Identifies the customer origin server
associated with an edge CNAME by its ID.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 416
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
Request
A request to retrieve a list of the edge CNAMEs (HTTP Large) associated with a customer's
account is described below. When submitting this request, you will need to define the following
terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
edge CNAME returned by this endpoint:
Name Description
DirPath A string that indicates the relative location on the origin server to
which the edge CNAME is pointed. If this response element is set to
blank, then the edge CNAME points to the root folder of the origin
server.
EnableCustomReports An integer that indicates whether hits and data transferred statistics
are being tracked for this edge CNAME. Logged data can be viewed
through the Custom Reports module.
Valid values for this parameter are:
• 0: Disabled (Default Value).
• 1: Enabled. CDN activity on this edge CNAME is being
logged.
Id An integer that indicates the ID for the edge CNAME.
MediaTypeId An integer that indicates the platform on which the edge CNAME
configuration resides. This response element will always report "3,"
which is the value assigned to the HTTP Large platform.
Name A string that indicates the name assigned to the edge CNAME.
OriginId An integer that indicates the origin server associated with the edge
CNAME. Valid return values are:
• -1: Indicates that the edge CNAME points to a CDN origin
server.
• CustomerOriginID: Identifies the customer origin server
associated with an edge CNAME by its ID.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 386
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"DirPath" : "",
"EnableCustomReports" : 0,
Retrieves all edge CNAMEs for the HTTP Small platform associated with a particular customer.
Request
A request to retrieve a list of the edge CNAMEs (HTTP Small) associated with a customer's
account is described below. When submitting this request, you will need to define the following
term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
edge CNAME returned by this endpoint:
Name Description
DirPath A string that indicates the relative location on the origin server to
which the edge CNAME is pointed. If this response element is set to
blank, then the edge CNAME points to the root folder of the origin
server.
EnableCustomReports An integer that indicates whether hits and data transferred statistics
are being tracked for this edge CNAME. Logged data can be viewed
through the Custom Reports module.
Valid values for this parameter are:
• 0: Disabled (Default Value).
• 1: Enabled. CDN activity on this edge CNAME is being
logged.
Id An integer that indicates the ID for the edge CNAME.
MediaTypeId An integer that indicates the platform on which the edge CNAME
configuration resides. This response element will always report "8,"
which is the value assigned to the HTTP Small platform.
Name A string that indicates the name assigned to the edge CNAME.
OriginId An integer that indicates the origin server associated with the edge
CNAME. Valid return values are:
• -1: Indicates that the edge CNAME points to a CDN origin
server.
• CustomerOriginID: Identifies the customer origin server
associated with an edge CNAME by its ID.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 386
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"DirPath" : "",
"EnableCustomReports" : 0,
"Id" : 20101,
Note: If you would like to retrieve a list of edge CNAMEs by platform for a particular customer's
account, please refer to the section corresponding to the desired platform.
Request
A request to view the properties associated with an edge CNAME is described below. When
submitting this request, you will need to define the following terms:
• EdgeCNAMEID: This term should be replaced by the ID assigned to the edge CNAME
whose properties you would like to view. The ID associated with each edge CNAME is
returned by the platform-specific Returns called "Get All Edge CNAMEs."
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
DirPath A string that indicates a location on the origin server. This string
should specify the relative path from the root folder to the desired
location. A blank value indicates that the edge CNAME points to the
root folder of the origin server.
EnableCustomReports An integer that indicates whether hits and data transferred statistics
are being tracked for this edge CNAME. Logged data can be viewed
through the Custom Reports module.
Valid values for this parameter are:
• 0: Disabled (Default Value).
• 1: Enabled. CDN activity on this edge CNAME is being
logged.
Id An integer that indicates the ID assigned to the edge CNAME.
MediaTypeId An integer that indicates the platform associated with the edge
CNAME. A platform is identified by its ID. Valid return values are:
• 3: HTTP Large
• 8: HTTP Small
• 14: ADN
Name A string that indicates the name assigned to the edge CNAME.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 192
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"DirPath" : "\/RelativePath",
"EnableCustomReports" : 0,
"Id" : 123456,
"MediaTypeId" : 3,
"Name" : "images.mydomain.com",
"OriginId" : -1,
"OriginString" : "\/000001\/RelativePath"
}
Note: This endpoint may not be used to retrieve propagation status for edge CNAME
configurations that were last updated more than 7 days ago.
Request
A request to retrieve status information is described below. When submitting this request, you
will need to define the following terms:
• xxxx: Replace this term with the desired customer account number.
• EdgeCNAMEID: Replace this term with the system-defined ID for the desired edge
CNAME configuration.
Use a platform-specific Get All Edge CNAMEs endpoint to retrieve the system-defined ID
for the desired customer origin.
Sample request for the HTTP Large platform:
https://api.edgecast.com/v2/mcc/customers/0001/cnames/httplarge
Note: Please refer to the REST API Help Center for more detailed information on this
endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request varies according to the following factors:
• New / Update: The following response will be provided immediately after an edge
CNAME configuration is created or updated:
{"Status":"New","Percent_propagated":0}
• Existing Configurations: If the edge CNAME configuration is older than 7 days, then this
endpoint will return a 400 Bad Request with the following response body:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 7051
{
"Status": "propagated",
"Percent_propagated": 100,
"Pops": [{
"name": "South America : Valparaiso, Chile",
"percentage_propagated": 100
}, {
...
"name": "Europe : London",
"percentage_propagated": 91.20879120879121
}, {
"name": "North America : Atlanta",
"percentage_propagated": 100
}, {
"name": "North America : Miami",
"percentage_propagated": 100
}, {
"name": "Europe : London",
"percentage_propagated": 100
}
]
}
Note: Although this endpoint allows you to modify the hostname associated with an edge
CNAME configuration, it will not update the corresponding CNAME record on a DNS server.
Make sure to do so upon updating an edge CNAME's hostname.
Request
A request to update the properties associated with an edge CNAME configuration is described
below. When submitting this request, you will need to define the following terms:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Note: Omitting or setting an optional parameter to null will prevent it from being assigned a
value.
Name Description
DirPath A string that defines a location on the origin server to which the
edge CNAME configuration will be pointed. This string should specify
the relative path from the origin server's root folder to the desired
folder.
Tip: Set this parameter to blank to point the edge CNAME to the
root folder of the origin server.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
{
"DirPath" : "\/RelativePath",
"EnableCustomReports" : 0,
"Name" : "images.mydomain.com",
"OriginId" : -1
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 0
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
• Instances
Adds an encrypted HLS directory configuration that is only applicable for on-demand streaming
via Dynamic Cloud Packaging.
Note: The workflow for updating an encrypted HLS directory configuration is to delete the old
configuration and then create a new one through this endpoint.
Request
A request to create an encrypted HLS directory is described below. When submitting this
request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Data Type Description
Id Integer Identifies the newly created encrypted HLS directory
configuration by its system-defined ID.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
POST
https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/vod/ehlsdirectory
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
Content-Length: 68
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 23
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
[{
"Id": 6687
}
]
Add Instance
Creates an instance.
Request
A request to create an instance is described below. When submitting this request, you will need
to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Encrypted Boolean Indicates whether the live streams generated for this
instance will be secured with encrypted HLS.
EncryptedKeyRot Integer Indicates the interval, in seconds, at which the encryption
ation key generated for the live event will be rotated.
Note: Encryption key rotation may only take place at the
start of a new segment. Therefore, the live event's segment
size factors into when the encryption key will be rotated.
{
"InstanceName": "mythirdinstance",
"SegmentSize": 10
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 431
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"DvrDuration": null,
"Encrypted": false,
"EncryptedKeyRotation": null,
"HlsPlaybackUrl":
"http:\/\/wpc.0001.edgecastcdn.net\/240001\/myinstance\/<streamName>.m3u8",
"Id": 1317,
"InstanceName": "myinstance",
"MpegDashPlaybackUrl":
"http:\/\/wpc.0001.edgecastcdn.net\/240001\/myinstance\/<streamName>.mpd",
"PublishUrl": "\/200001\/myinstance\/<streamName>?<Live Authentication Key>",
"SegmentSize": 10,
"SsaEnabled": false
Adds a stream key that provides authorization for the Dynamic Cloud Packaging streaming
service.
Request
A request to create a stream key is described below. When submitting this request, you will
need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
Name Data Description
Type
DirPath String Identifies a stream by its relative path. The starting point for this
relative path is indicated in blue font below.
rtmp://fso.oxr.0001.edgecastcdn.net/200001/myinstance/mystream
Note: The stream identified by this parameter will be authorized by
the value defined in the Key parameter.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
POST https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/streamkeys
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
Content-Length: 69
{
"DirPath" : "myinstance\/livevideos",
"Key" : "abcdef123456"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 69
Content-Type: application/json; charset=utf-8
Date: Mon, 10 Jan 2011 12:00:00 GMT
{
"DirPath": "myinstance\/livevideos",
"Id": 193950,
"Key": "abcdef123456"
}
Important: The deletion of an encrypted HLS directory configuration takes place immediately.
Additionally, once it has been deleted, it cannot be recovered.
Request
A request to delete an encrypted HLS directory is described below. When submitting this
request, you will need to define the following terms:
• EHLSDirectoryID: Replace this variable with the system-defined ID of the encrypted HLS
directory configuration that will be deleted.
Tip: Use the Get Encrypted HLS Directories endpoint to retrieve a list of encrypted HLS
directory configurations and their system-defined IDs.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
DELETE
https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/vod/ehlsdirectory/1
010 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Date: Mon, 10 Jan 2011 12:00:00 GMT
Delete Instance
Deletes an instance.
Important: The deletion of an instance takes place immediately. Additionally, once an instance
has been deleted, it cannot be recovered.
Request
A request to delete an instance is described below. When submitting this request, you will need
to define the following terms:
• InstanceID: Replace this variable with the system-defined ID of the desired instance.
Tip: Retrieve a list of instances and their system-defined IDs through the Get All
Instances endpoint.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
DELETE https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/live/775
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Date: Mon, 10 Jan 2011 12:00:00 GMT
Deletes a stream key that authorizes a live stream on the Dynamic Cloud Packaging streaming
service.
Request
A request to delete a stream key is described below. When submitting this request, you will
need to define the following terms:
• KeyID: Replace this variable with the unique ID assigned to the stream key that will be
deleted.
Tip: Use the Get Stream Keys endpoint to retrieve a listing of stream keys and their IDs.
Replace this variable with the system-defined ID of the desired instance.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
DELETE
https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/streamkeys/193950
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Date: Mon, 10 Jan 2011 12:00:00 GMT
Request
A request to retrieve instances is described below. When submitting this request, you will need
to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Encrypted Boolean Indicates whether the live streams generated for this
instance will be secured with encrypted HLS.
EncryptedKeyRot Integer Indicates the interval, in seconds, at which the encryption
ation key generated for the live event will be rotated.
Note: Encryption key rotation may only take place at the
start of a new segment. Therefore, the live event's segment
size factors into when the encryption key will be rotated.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 944
[{
"DvrDuration": null,
"Encrypted": false,
"EncryptedKeyRotation": null,
"HlsPlaybackUrl":
"http:\/\/wpc.0001.edgecastcdn.net\/240001\/myfirstinstance\/<streamName>.m3u
8",
"Id": 752,
"InstanceName": "myfirstinstance",
"MpegDashPlaybackUrl":
"http:\/\/wpc.0001.edgecastcdn.net\/240001\/myfirstinstance\/<streamName>.mpd
",
"PublishUrl": "\/200001\/myfirstinstance\/<streamName>?<Live
Authentication Key>",
"SegmentSize": 10,
Retrieves a list of all encrypted HLS directories. This list may be filtered by ID or by origin type.
Request
A request to retrieve encrypted HLS directories is described below. When submitting this
request, you may need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• EHLSDirectoryID: Replace this variable with the system-defined ID for the desired
encrypted HLS directory. The response will be filtered to only return data for the
specified encrypted HLS directory.
Note: The id query string parameter should only be specified if you would like to filter
the response to a specific encrypted HLS directory. Return all encrypted HLS directories
by excluding query string parameters from the request.
Note: The originid query string parameter should only be specified if you would like to
filter the response by origin type. Return all encrypted HLS directories by excluding
query string parameters from the request.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response parameters for each
encrypted HLS directory returned by this endpoint:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/vod/ehlsdirectory
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 105
[{
"Id": 6375,
"OriginName": "CDN",
"OriginTypeId": 1,
"Path": "\/videos"
}
]
Retrieves the global key that provides authorization for the Dynamic Cloud Packaging streaming
service.
Request
A request to retrieve the global key is described below. When submitting this request, you will
need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Data Type Description
Key String Reports the value assigned to Dynamic Cloud
Packaging's global live authentication key.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/globalkey
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 34
{
"Key": "123457890abcdefghi"
}
Retrieves stream keys that provide authorization for the Dynamic Cloud Packaging streaming
service. The response may be filtered to only return a single stream key.
Request
A request to retrieve stream keys is described below. When submitting this request, you may
need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• StreamID: Replace this variable with the system-defined ID associated with the desired
stream key.
Note: The id query string parameter should only be specified to filter the response to
return a single stream key.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/streamkeys
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 294
[{
"DirPath": "myinstance\/mystream",
"Id": 192836,
"Key": "123457890abcdefghi"
}, {
"DirPath": "myinstance\/salesconference",
"Id": 192837,
"Key": "223457890abcdefghi"
}, {
"DirPath": "myinstance\/marketingevent",
"Id": 192873,
"Key": "323457890abcdefghi"
}
]
Updates the value assigned to the global key that provides authorization for the Dynamic Cloud
Packaging streaming service.
Request
A request to update the global key is described below. When submitting this request, you will
need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Name Data Type Description
Key String Identifies the global live authentication key that may be used
to authenticate any stream that is published to a location
that has not been secured by a stream key. This key must be
256 alphanumeric characters or less.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response parameter.
PUT https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/globalkey
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
Content-Length: 25
{
"Key" : "abcdef123456"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Update Instance
Request
A request to update an instance is described below. When submitting this request, you will need
to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• InstanceID: Replace this variable with the system-defined ID of the desired instance.
Note: Retrieve a list of instances and their system-defined IDs through the Get All
Instances endpoint.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Data Type Description
DvrDuration Integer Indicates the length, in minutes, of the DVR window. The
length of this DVR window may be set from 5 to 180 minutes
(i.e., 3 hours).
Note: If a DVR window was not specified in the request, then
this parameter will report a default duration of 1 minute.
Encrypted Boolean Indicates whether the live streams generated for this
instance will be secured with encrypted HLS.
EncryptedKeyRot Integer Indicates the interval, in seconds, at which the encryption
ation key generated for the live event will be rotated.
Note: Encryption key rotation may only take place at the
start of a new segment. Therefore, the live event's segment
size factors into when the encryption key will be rotated.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/live/750
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
Content-Length: 45
{
"DvrDuration": 15,
"SegmentSize": 10
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 431
{
"DvrDuration": 25,
"Encrypted": false,
"EncryptedKeyRotation": null,
"HlsPlaybackUrl":
"http:\/\/wpc.0001.edgecastcdn.net\/240001\/myinstance\/<streamName>.m3u8",
"Id": 750,
"InstanceName": "myinstance",
"MpegDashPlaybackUrl":
"http:\/\/wpc.0001.edgecastcdn.net\/240001\/myinstance\/<streamName>.mpd",
"PublishUrl": "\/200001\/myinstance\/<streamName>?<Live Authentication Key>",
"SegmentSize": 10,
"SsaEnabled": false
}
Updates the properties of an existing stream key that provides authorization for the Dynamic
Cloud Packaging streaming service.
Request
A request to update a stream key is described below. When submitting this request, you will
need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• KeyID: Replace this variable with the system-defined ID assigned to the stream key that
you would like to update.
Note: Use the Get Stream Keys endpoint to retrieve a listing of stream keys and their
IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
Key String Identifies the live authentication key that may be used to
authenticate streams published to the path specified by this stream
key configuration. This key must be 256 alphanumeric characters or
less.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request does not contain a response parameter.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT
https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/dcp/streamkeys/193950
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
Content-Length: 45
{
"DirPath" : "myinstance\/secure",
"Key" : "123456",
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Provides information describing your current log format configuration for all HTTP platforms.
The settings returned by this endpoint are:
• Date/time format
• Custom field
Request
A request to retrieve your current log format configuration is described below. When submitting
this request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
AN A string that indicates the customer account number whose
configuration will be returned. This customer account number
will always match the one specified in the request URI.
BaseFormat An integer that indicates the current base log file format. Valid
values for this response element are:
• 1: Indicates that log data will be stored using a default
log file format. This format is similar to an extended
W3C log file format.
• 2: Indicates that log data will be stored using the
combined log file format. This format is the default log
file format used by Apache web servers.
CustomFieldHeader A string that indicates the name of the custom log field header.
This response element will always be blank when the Add the
custom file to the log file option is cleared or the
ShowCustomField response element is set to 0.
DateTimeFormat An integer that indicates the format that will be used to report
the date/time field. Valid values for this response element are:
• 0: Indicates that the date/time field will be reported
using Unix time (a.k.a. POSIX time or Unix epoch).
• 1: Indicates that the date/time field will be reported
using a custom format. The format that will be used
depends on the base log file format. An example of
how the date/time field will be formatted is provided
for each type of log file format.
Default format: 2012-12-10 11:00:00
Combined format: 10/Dec/2012:11:00:00
+0000
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 158
Provides information describing your current log storage configuration for all platforms. The
settings returned by this endpoint are:
Request
A request to retrieve your current log storage configuration is described below. When
submitting this request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 277
{
"AN" : "0001",
"DaysToKeep" : -1,
"IsEnabled" : 1,
"MediaTypeStatuses" : [{
"IsEnabled" : 1,
"MediaTypeId" : 3
}, {
"IsEnabled" : 1,
"MediaTypeId" : 8
}, {
"IsEnabled" : 1,
"MediaTypeId" : 1
}, {
"IsEnabled" : 0,
"MediaTypeId" : 14
}
]
}
Defines the log format for all HTTP platforms. The settings defined by this endpoint are:
• Date/time format
• Custom field
Request
A request to define your log format configuration is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional parameters are described below.
Name Description
BaseFormat An integer that determines the base log file format. Valid
values for this parameter are:
• 1: Determines that log data will be stored using a
default log file format. This format is similar to an
extended W3C log file format.
• 2: Determines that log data will be stored using the
combined log file format. This format is the default log
file format used by Apache web servers.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"BaseFormat" : 1,
"CustomFieldHeader" : "x-ec_custom-1",
"DateTimeFormat" : 0,
"RemoveContentAccessPoint" : 0,
"ShowCustomField" : 1
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Defines your log storage configuration for each available platform. The settings defined by this
endpoint are:
Note: This endpoint can only be performed if the logging capability has been activated on the
desired platform. Attempting to configure log storage settings on a platform for which it has not
been activated will generate a 400 Bad Request. Please contact your CDN account manager to
activate logging.
Request
A request to set your log storage configuration is described below. When submitting this
request, you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional parameters are described below.
IsEnabled An integer that determines whether log files will be archived for a
particular platform. Valid values for this parameter are:
• 0: Log files for the platform indicated in the corresponding
MediaTypeId parameter will not be archived. This is the default
value for each specified MediaTypeId parameter.
• 1: Log files for the platform indicated in the corresponding
MediaTypeId parameter can be archived. The main IsEnabled
parameter (see above) determines whether log files will actually
be archived.
MediaTypeId An integer that identifies the platform for which log file archival will be
enabled or disabled. Valid values for this parameter are:
• 3: HTTP Large
• 8: HTTP Small
• 14: Application Delivery Network (ADN)
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"DaysToKeep" : -1,
"IsEnabled" : 1,
"MediaTypeStatuses" : [{
"IsEnabled" : 1,
"MediaTypeId" : 3
}, {
"IsEnabled" : 1,
"MediaTypeId" : 8
}, {
"IsEnabled" : 1,
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Route (DNS)
The endpoints covered in this section only apply to the Route (DNS) platform. Use these
endpoints to add, update, retrieve, copy, and delete zones.
Creates a primary zone. A new zone can contain any of the following items:
• Records
• Failover groups
Request
A request to create a zone is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
The required request parameters for this endpoint are described below.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
{
"Comment" : "",
"DomainName" : "myzone.com.",
"FailoverGroups" : [{
"Group" : {
"A" : [],
"AAAA" : [],
"CNAME" : [{
"HealthCheck" : null,
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1380
{
"Comment" : "",
"DomainName" : "myzone.com.",
"FailoverGroups" : [{
"Group" : {
"A" : [],
"AAAA" : [],
"CNAME" : [{
"HealthCheck" : null,
"IsPrimary" : false,
"Record" : {
"Name" : "web",
"Rdata" : "web01.myzone.com.",
"TTL" : 300
}
}, {
"HealthCheck" : null,
"IsPrimary" : true,
"Record" : {
"Name" : "web",
Creates a copy of a primary zone. The only difference between the original zone and its copy is
the name assigned to it.
Request
A request to copy a zone is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
The required request parameters for this endpoint are described below.
Name Description
FromDomainName A string that identifies the zone that will be copied by its name.
ToDomainName A string that defines the name that will be assigned to the new zone.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
{
"FromDomainName":"myzone.com",
"ToDomainName":"copyofmyzone.com"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
{
"Comment" : "",
"DomainName" : "copyofmyzone.com.",
"FailoverGroups" : [{
"Group" : {
"A" : [],
"AAAA" : [],
"CNAME" : [{
"HealthCheck" : null,
"IsPrimary" : false,
"Record" : {
"Name" : "web",
"Rdata" : "web01.myzone.com.",
"TTL" : 300
}
}, {
"HealthCheck" : null,
"IsPrimary" : true,
"Record" : {
"Name" : "web",
"Rdata" : "web02.myzone.com.",
"TTL" : 300
}
}
]
},
"GroupTypeId" : 3,
"Name" : "web"
}
],
"LoadBalancingGroups" : [{
"Group" : {
"A" : [],
"AAAA" : [],
"CNAME" : [{
Warning: The deletion of a primary zone takes place immediately and cannot be undone.
Request
A request to delete a primary zone is described below.
• ZoneID: Replace this term with the system-defined ID of the desired zone. Use the Get
All Zones endpoint to retrieve a list of zones and their system-defined IDs.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Date: Thu, 14 Apr 2016 12:00:00 GMT
This endpoint returns a list of primary zones. This list may be filtered by zone status.
Request
A request to retrieve zones is described below.
• StatusID: Replace this term with the ID for the desired zone status. The response will be
filtered by the specified status. If the response should not be filtered by status, then the
status query string parameter should not be included in the request URI.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Name Description
DomainName A string that identifies a zone by its name.
Status An integer that indicates a zone's status by its system-defined ID.
Use the Get Available Zone Statuses endpoint to retrieve a list of
zone statuses.
Version An integer that indicates a zone's version. This version number is
incremented whenever a change is applied to a zone.
ZoneId An integer that identifies a zone by its system-defined ID.
ZoneType An integer that indicates the type of zone being described.
Use the Get Available Zone Types endpoint to retrieve a list of zone
types.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 248
Returns a list of methods through which a server/domain can be reintegrated into a load
balancing or failover group.
Request
A request to retrieve reintegration methods is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Body
The response body for a successful request contains the following response elements for each
reintegration method returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to the
reintegration method.
Name A string that indicates the name of a reintegration method.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 87
[{
"Id" : 1,
"Name" : "Automatic"
}, {
"Id" : 2,
"Name" : "Manual"
}
]
Returns a list of the supported methods that may be used to probe a server/domain's health
status.
Request
A request to retrieve supported health check types is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for each
health check type returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to the
health check type.
Name A string that indicates the name of the health check type supported
by our DNS Health Checks module.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 166
[{
"Id" : 1,
"Name" : "HTTP"
}, {
"Id" : 2,
"Name" : "HTTPs"
}, {
"Id" : 3,
"Name" : "TCP Open"
}, {
"Id" : 4,
"Name" : "TCP SSL"
}
]
Returns a list of the HTTP methods supported by the DNS Health Checks module.
Request
A request to retrieve a list of HTTP methods is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for each
HTTP method returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to an HTTP
method.
Name A string that indicates the name of a supported HTTP method.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 79
[{
"Id" : 1,
"Name" : "GET"
}, {
"Id" : 2,
"Name" : "POST"
}
]
Returns the available set of IP versions supported by our DNS Health Checks module.
Request
A request to find out the supported set of IP versions is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for each IP
version returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to the
IP version.
Name A string that indicates the name of the IP version supported by our
DNS Health Checks module.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 80
Returns a list of the available types of load balancing and failover groups.
Request
A request to the available set of group types is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Name Description
Id An integer that indicates the system-defined ID assigned to the group type.
Name A string that indicates the load balancing/failover group type.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 125
[{
"Id" : 1,
"Name" : "CNAME"
}, {
"Id" : 2,
"Name" : "Subdomain"
}, {
"Id" : 3,
"Name" : "Zone"
}
]
Returns a list of the available types of records and their system-defined IDs.
Request
A request to retrieve record types is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for each
record type returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to the record type.
Name A string that indicates the name of the record type.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 306
[{
"Id" : 1,
"Name" : "A"
}, {
"Id" : 2,
"Name" : "AAAA"
}, {
"Id" : 3,
"Name" : "CNAME"
}, {
"Id" : 4,
"Name" : "MX"
}, {
"Id" : 5,
"Name" : "NS"
}, {
"Id" : 8,
"Name" : "SPF"
}, {
"Id" : 9,
"Name" : "SRV"
}, {
"Id" : 10,
"Name" : "TXT"
}
]
Request
A request to retrieve a list of zone statuses is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for each
zone status returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to a zone status.
Name A string that indicates the name of a zone status.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 86
[{
"Id" : 1,
"Name" : "Active"
}, {
"Id" : 2,
"Name" : "Inactive"
}
]
Request
A request to retrieve zone types is described below.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for each
zone type returned by this endpoint:
Name Description
Id An integer that indicates the system-defined ID assigned to the zone type.
Name A string that indicates the name of the zone type.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 88
Get Zone
Request
A request to retrieve a zone is described below.
• ZoneName: Replace this term with the name of the desired zone.
• DateTime: Optional. Retrieve the version of a zone at a given point in time. Replace this
term with the desired date/time. The format for this term is: YYYY-MM-DDThh:mm:ss.
Note: Either the id or the name query string parameter must be specified.
Note: Time (i.e., Thh:mm:ss) is optional. If time is not specified, then a default time (i.e.,
00:00:00) will be used.
Request Headers
This endpoint only takes advantage of common request headers.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed.
Response Headers
The response for this endpoint only includes standard HTTP response headers. View common
response headers.
Response Body
The response body for a successful request contains the following response elements for the
zone returned by this endpoint:
Name Description
Comment A string that indicates the comment associated
with a zone.
DomainName A string that indicates a zone's name.
FailoverGroups This response element contains the set of failover
groups associated with a zone.
Group This response element contains a failover group.
[A|AAAA|CNAME] Each group contains a section for each record
type. Records are returned in the following order.
• A
• AAAA
• CNAME
This response element contains the following
information about a record:
• Health check configuration
• Properties
• Primary status
Note: If the group does not contain a particular
type of record, then that section will remain
blank.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1668
{
"Comment" : "",
"DomainName" : "myzone.com.",
"FailoverGroups" : [{
"Group" : {
"A" : [],
"AAAA" : [],
"CNAME" : [{
"HealthCheck" : null,
"IsPrimary" : false,
"Record" : {
"Name" : "web",
"Rdata" : "web01.myzone.com.",
Updates an entire primary zone by overwriting the previous version with the submitted zone
data. All missing zone properties, records, groups, and health checks are treated as deletions.
The recommended method to update a zone is described below.
1. Use the Get Zone endpoint to retrieve the entire zone.
2. The response of the above endpoint should be modified as needed. For example, insert
or remove the desired records or load balancing/failover configurations.
3. Set the request body of this endpoint to the zone data updated in step 2.
Request
A request to update a zone is described below.
Request Body
The required request parameters for this endpoint are described below.
Name Description
Comment A string that assigns a comment to the zone.
DomainName A string that should be set to the current name
assigned to the zone.
Note: The name assigned to a zone cannot be
modified.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed.
Response Body
The response body for a successful request returns the properties of the updated zone.
Name Description
Comment A string that indicates the comment associated
with the updated zone.
DomainName A string that indicates the updated zone's name.
FailoverGroups This response element contains the set of failover
groups associated with the updated zone.
Group This response element contains a failover group.
[A|AAAA|CNAME] Each group contains a section for each record
type. Records are returned in the following order.
• A
• AAAA
• CNAME
This response element contains the following
information about a record:
• Health check configuration
• Properties
• Primary status
Note: If the group does not contain a particular
type of record, then that section will remain
blank.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. View common error messages.
{
"Comment" : "",
"DomainName" : "myzone.com.",
"FailoverGroups" : [{
"Group" : {
"A" : [],
"AAAA" : [],
"CNAME" : [{
"HealthCheck" : null,
"IsPrimary" : false,
"Record" : {
"Name" : "web",
"Rdata" : "web01.myzone.com.",
"TTL" : 300
}
}, {
"HealthCheck" : null,
"IsPrimary" : true,
"Record" : {
"Name" : "web",
"Rdata" : "web02.myzone.com.",
"TTL" : 300
}
}
]
},
"GroupTypeId" : 3,
"Name" : "web"
}
],
"LoadBalancingGroups" : [{
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1380
{
"Comment" : "",
Smooth Streaming
This section covers how you can add, delete, retrieve, update, and shut down Smooth Streaming
– Live Streaming publishing points.
Note: It may take up to 10 minutes before the creation of a publishing point takes effect.
Request
A request to add a publishing point is described below. When submitting this request, you will
need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Name Description
AuthKey Required. A string that defines a key required to authenticate an encoder to
our servers. This key must be specified in the publishing point URL.
DVRDuration Required. An integer that defines the length, in minutes, of the DVR
playback window. This parameter must be set to a value between 1 and 180.
Duration An integer that defines the estimated duration, in seconds, of the live
stream. A video player uses this information to calculate the seek bar.
Expiration Required. A string that defines the publishing point's expiration date using
the following format: YYYY-MM-DD.
Name Required. A string that defines the name associated with the publishing
point.
Title A string that defines the title that will be associated with all streams that
leverage this publishing point.
iOSStreaming An integer that determines the stream will be transmuxed to a format that is
supported by an HTTP Live Streaming (HLS) player.
• 0: Determines that this publishing point will only generate a stream
that is compatible with Silverlight players.
• 1: Determines that this publishing point will generate streams that
are compatible with Silverlight players and iOS devices.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Id An integer that indicates the unique ID assigned to the new publishing point.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
POST https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/livesmooth
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
Content-Length: 184
{
"AuthKey" : "123456789",
"DVRDuration" : 120,
"Duration" : 240,
"Expiration" : "2013-03-31",
"Name" : "event1",
"Title" : "My First Event",
"iOSStreaming" : 0
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 14
{
"Id":123
}
Request
A request to delete a publishing point is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
DELETE https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/livesmooth/15
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, 14 Apr 2016 12:00:00 GMT
Request
A request to retrieve all publishing points is described below. When submitting this request, you
will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
publishing point.
Name Description
AuthKey A string that indicates the key required to authenticate an encoder to our
servers.
DVRDuration An integer from 1 to 180 that indicates the length, in minutes, of the DVR
playback window.
Duration An integer that indicates the estimated duration, in seconds, of the live
stream.
Expiration A string that indicates the publishing point's expiration date/time (GMT).
Id An integer that indicates the unique system-defined ID corresponding to
the publishing point.
Name A string that indicates the name of the publishing point.
PlayerUrl A string that indicates the player URL through which video playback can be
performed.
PublishingPoints This parameter contains a list of publishing point URLs associated with this
publishing point and their corresponding region.
Region An integer that indicates the region associated with a publishing point URL.
Url A string that indicates a publishing point URL.
ShutDownDate A string that indicates the date and time (GMT) on which the publishing
point was last shutdown.
Title A string that indicates the title associated with all streams that leverage
this publishing point.
iOSStreaming A string that indicates whether the stream will be transmuxed to a format
that is supported by an HTTP Live Streaming (HLS) player.
• true: Indicates that this publishing point will generate streams that
are compatible with Silverlight players and iOS devices.
• false: Indicates that this publishing point will only generate a
stream that is compatible with Silverlight players.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1046
[{
"AuthKey" : "123456",
"DVRDuration" : 5,
"Duration" : 0,
"Expiration" : "2013-04-01",
"Id" : 15,
"Name" : "presentation",
"PlayerUrl" :
"http:\/\/wpc.0001.edgecastcdn.net\/210001\/presentation.isml\/Manifest",
"PublishingPoints" : [{
"Region" : "North America - Los Angeles",
"Url" :
"http:\/\/wsi.oxr.0001.edgecastcdn.net\/210001\/presentationET123456.isml"
}, {
"Region" : "North America - Ashburn",
"Url" :
"http:\/\/wsi.dca.0001.edgecastcdn.net\/210001\/presentationET123456.isml"
}, {
"Region" : "Europe - Amsterdam",
"Url" :
"http:\/\/wsi.ams.0001.edgecastcdn.net\/210001\/presentationET123456.isml"
Request
A request to retrieve a publishing point is described below. When submitting this request, you
will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements.
Name Description
AuthKey A string that indicates the key required to authenticate an encoder to our
servers.
DVRDuration An integer from 1 to 180 that indicates the length, in minutes, of the DVR
playback window.
Duration An integer that indicates the estimated duration, in seconds, of the live
stream.
Expiration A string that indicates the publishing point's expiration date/time (GMT).
Id An integer that indicates the unique system-defined ID corresponding to
the publishing point.
Name A string that indicates the name of the publishing point.
PlayerUrl A string that indicates the player URL through which video playback can be
performed.
PublishingPoints This parameter contains a list of publishing point URLs associated with this
publishing point and their corresponding region.
Region An integer that indicates the region associated with a publishing point URL.
Url A string that indicates a publishing point URL.
ShutDownDate A string that indicates the date and time (GMT) on which the publishing
point was last shutdown.
Title A string that indicates the title associated with all streams that leverage
this publishing point.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/livesmooth/15
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1014
{
"AuthKey" : "123456",
"DVRDuration" : 5,
"Duration" : 0,
"Expiration" : "2013-04-01",
"Id" : 15,
"Name" : "presentation",
"PlayerUrl" :
"http:\/\/wpc.0001.edgecastcdn.net\/210001\/presentation.isml\/Manifest",
"PublishingPoints" : [{
"Region" : "North America - Los Angeles",
Request
A request to shut down a publishing point is described below. When submitting this request,
you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT
https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/livesmooth/15/shutdown
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 0
Note: It may take up to 10 minutes before modification of a publishing point takes effect.
Request
A request to update a publishing point is described below. When submitting this request, you
will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Name Description
AuthKey Required. A string that defines a key required to authenticate an encoder to
our servers. This key must be specified in the publishing point URL.
DVRDuration Required. An integer that defines the length, in minutes, of the DVR
playback window. This parameter must be set to a value between 1 and 180.
Duration An integer that defines the estimated duration, in seconds, of the live
stream. A video player uses this information to calculate the seek bar.
Expiration Required. A string that defines the publishing point's expiration date using
the following format: YYYY-MM-DD.
Name Required. A string that defines the name associated with the publishing
point.
Title A string that defines the title that will be associated with all streams that
leverage this publishing point.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT https://api.edgecast.com/v2/mcc/customers/0001/httpstreaming/livesmooth/15
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
Content-Length: 128
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 0
Important: This endpoint has been deprecated. Please use the Add Token-Based Authentication
Directory endpoint instead.
This legacy endpoint is used to add a platform-specific authentication directory. The proper
syntax for requesting this legacy endpoint is provided below.
HTTP Request URI
Method
POST https://api.edgecast.com/v2/mcc/customers/AccountNumber/token/directory
Note: For additional information about this legacy endpoint, please refer to the REST API Help
Center.
Adds a platform-specific directory that will require authentication. Keep in mind that Token-
Based Authentication is applied recursively to each authentication directory.
Request
A request to add an authentication directory is described below. When submitting this request,
you will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Body
The required request parameters for this endpoint are described below.
Name Description
Directory Required. A string that indicates the relative path to the authentication
directory. The starting point for this relative path varies according to origin
server type.
• CDN Origin Server: The root folder for your CDN storage account
can be specified using a forward slash (i.e., /). If you would like to
specify a different folder, simply append the relative path to that
folder (e.g., /Presentations/2011).
• Customer Origin Server: The root folder for your customer origin
server can be specified by typing a forward slash, the name of your
customer origin server, and then another forward slash (e.g.,
/MyCustomerOrigin/). If you would like to specify a different folder,
simply append the relative path to that folder (e.g.,
/MyCustomerOrigin/Presentations/2011).
Reminder: This configuration will only secure the specified location for the
platform specified by the MediaType parameter. Please make sure to set up
Token-Based Authentication on other platforms to ensure that the content
in question requires authentication.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Id An integer that indicates the unique ID assigned to the new authentication
directory.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"Directory":"\/MyCustomerOrigin\/Presentations",
"MediaTypeId":3
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 14
{
"Id":123
}
Request
A request to delete an authentication directory is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
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, 14 Apr 2016 12:00:00 GMT
Important: You should upgrade to Token-Based Authentication 3.0. Learn more (CDN Help
Center).
Tip: Set the TokenVersion request body parameter to "V3" to generate tokens using encryption
version 3.0.
Encrypts data for use with Token-Based Authentication. This encryption process does not alter
the configuration of your customer account. It is only provided for your convenience. Leverage
this method to generate token values that may be used when linking to content that requires
authentication.
Request
A request to encrypt data as a token value is described below.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
TokenVersion A string that identifies the encryption version that will be used to generate
the token.
Valid values are:
• V3: Generates a token using encryption version 3.0. This is the
recommended value.
• V2: Generates a token using encryption version 2.0.
Default Behavior: The token will be encrypted using the specified key's
minimum encryption version. If the specified key doesn't exist, then the
token will be encrypted using version 2.0.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"Key" : "MyPrimaryKeyTBA",
"TokenParameter" :
"ec_expire=1356955200&ec_country_deny=CA&ec_country_allow=US,MX",
"TokenVersion" : "V3"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 174
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
{
"Token" :
"c17fe661298545b8c6c39808e4c6c32a87a215a1d3bfdb2ebd2ec06c9ce42538767ce212e8aa
17689f1511033fdd302f98a487abc821bf3726b845afeded843c79b82686f46d61da6a296e3b"
}
Request
A request to retrieve a list of authentication directories is described below. When submitting
this request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• MediaTypeID: This term should be replaced by the ID associated with the desired
platform. Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
directory returned by this endpoint:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/token/directories?mediatypeid=3
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 184
[{
"Id" : 123,
"Directory" : "\/MyCustomerOrigin\/Presentations",
"MediaTypeId" : 3
}, {
"Id" : 124,
"Directory" : "\/MyCustomerOrigin\/Documents",
"MediaTypeId" : 3
Request
A request to retrieve an authentication directory is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 88
{
"Id" : 123,
"Directory" : "\/MyCustomerOrigin\/Presentations",
"MediaTypeId" : 3
}
Important: You should upgrade to Token-Based Authentication 3.0. Learn more (CDN Help
Center).
Tip: Set the MinVersion request body parameter to "V3" to only allow the new key to
encrypt/decrypt tokens using version 3.0.
Updates the primary Token-Based Authentication key associated with the specified platform.
This key is used by our servers to encrypt and decrypt a token value.
Important: The update of a primary key may take up to an hour to take effect. However, a
response will be returned immediately.
Warning: This endpoint should be used with care. The safest method for updating your primary
key is to do so through the Token-Based Authentication page in the MCC. Continuous access to
your content cannot be guaranteed when a backup key is not used. For more information,
please refer to the Token-Based Authentication Administration Guide.
Request
A request to update a primary key is described below. When submitting this request, you will
need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
The required request parameters for this endpoint are described below.
Name Description
Key Required. A string that updates the value assigned to the primary
Token-Based Authentication key associated with the specified platform.
Only alphanumeric characters are supported by this string value.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"Key":"MyPrimaryKeyTBA",
"MediaType":3,
"MinVersion" : "V3"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Request
A request to update an authentication directory is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
A required request parameter for this endpoint is described below.
Name Description
Directory A string that determines the relative path to an authentication directory.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
{
"Directory" : "\/MyCustomerOrigin\/Presentations"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Endpoint Description
Add Instance Creates a WAF instance.
Add Profile Creates a WAF profile.
Add Profile by Template Creates a WAF profile based on a template.
Delete Instance Deletes a WAF instance.
Delete Profile Deletes a WAF profile.
Get All Instances Retrieves a list of WAF instances.
Get All Profiles Retrieves a list of WAF profiles.
Get Available Policies Retrieves a list of the policies associated with a rule set.
Get Available Rule Sets Retrieves a list of the rule sets that may be assigned to a profile.
Get Available Rules Retrieves a list of rules associated with a policy.
Get Available Templates Retrieves a list of templates that may be leveraged when
creating a WAF profile.
Get Instance by ID Retrieves a WAF instance by its ID.
Get Instances by Profile Retrieves a list of instances that have been associated with a
specific profile.
Get Profile by ID Retrieves a WAF profile by its ID.
Get Template Retrieves the configuration associated with a template.
Update Instance Updates a WAF instance.
Update Profile Updates a WAF profile.
Request
A request to create an instance is described below. When submitting this request, you will need
to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"name" : "Site F",
"prod_profile_id" : "23",
"prod_profile_enforcements" : [{
"name" : "Alert Only",
"type" : "nop"
}
]
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 27
{
"id" : "492",
"success" : true
}
Add Profile
Request
A request to create a profile is described below. When submitting this request, you will need to
define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Name Data Description
Type
access_settings Object Required. This request parameter contains
access control settings.
asn Object This request parameter contains access
controls for ASNs.
target String
Important: This parameter is required when
defining a target.
target_match String
Important: This parameter is required when
defining a target.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"access_settings": {
"country": {},
"ip": {},
"referer": {},
"url": {},
"user-agent": {}
},
"policies" : [
"modsecurity_crs_45_trojans.conf",
"modsecurity_crs_23_request_limits.conf",
"modsecurity_crs_30_http_policy.conf",
"modsecurity_crs_49_inbound_blocking.conf"
],
"general_settings": {
"allowed_http_methods": ["GET", "POST", "OPTIONS", "HEAD", "PUT",
"DELETE"],
"allowed_http_versions": ["HTTP\/0.9", "HTTP\/1.0", "HTTP\/1.1"],
"allowed_request_content_types": ["application\/x-www-form-
urlencoded", "multipart\/form-data", "application\/json"],
"anomaly_threshold": 10,
"arg_length": 0,
"arg_name_length": 0,
"combined_file_sizes": 0,
"engine": "anomaly",
"max_file_size": 0,
"max_num_args": 0,
"response_header_name": "X-CDN-Security-Audit",
"total_arg_length": 0
},
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 93
{
"id": "e032f437-6220-4bf7-a5ea-1a2bcd34e45f",
"status": "success",
"success": true
}
Tip: Use the Update Profile endpoint to fine-tune the configuration of a profile created through
this endpoint.
Request
A request to create a profile is described below. When submitting this request, you will need to
define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Data Type Description
id String Identifies the new WAF profile by its system-defined ID.
status String Returns "success" when a WAF profile is created.
success Boolean Indicates whether the WAF profile was created.
Valid values are:
• true
• false
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"name" : "Site C Profile",
"template_id" : "03_Trustwave_OWASP_Integrated.json"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 93
{
"id": "41abd111-2fcd-4333-8cfb-1a2bcd34e45f",
"status": "success",
"success": true
}
Request
A request to delete an instance is described below. When submitting this request, you will need
to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• InstanceID: Replace this variable with the system-defined ID of the desired instance.
Use the Get All Instances endpoint to retrieve a list of all available instances and their
system-defined IDs.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
DELETE https://api.edgecast.com/v2/mcc/customers/0001/waf/config/instances/487
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Date: Thu, 14 Apr 2016 12:00:00 GMT
Delete Profile
Request
A request to delete a profile is described below. When submitting this request, you will need to
define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• ProfileID: Replace this variable with the system-defined ID of the desired profile. Use
the Get All Profiles endpoint to retrieve a list of all available profiles and their system-
defined IDs.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request does not contain a response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
DELETE https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/720
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Date: Thu, 14 Apr 2016 12:00:00 GMT
Request
A request to retrieve all available WAF instances is described below. When submitting this
request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 143
[{
"id" : 147,
"name" : "Site A"
}, {
"id" : 487,
"name" : "Site B"
}, {
"id" : 488,
"name" : "Site B - Alternate"
}
]
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 450
[{
"ruleset_id": "Trustwave-OWASPIntegration-Application",
"ruleset_version": "2017-09-18",
"created_date": "10/13/2017 05:47:25 PM",
"id": "e032f437-6220-4bf7-a5ea-1a2bcd34e45f",
"name": "Site B Profile Test"
}, {
"ruleset_id": "Trustwave-OWASPIntegration-Application",
"ruleset_version": "2017-08-01",
"created_date": "09/28/2017 6:04:30 PM",
"id": "0b97746d-8e71-4f95-83bd-1a2bcd34e45f",
"name": "My Profile"
}
]
Retrieves a list of the available policies for the specified rule set.
Request
A request to retrieve policies is described below. When submitting this request, you will need to
define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• RuleSetID: Replace this variable with the system-defined ID of the rule set whose
policies will be retrieved.
Tip: Use either the Get Profile by ID or the Get Profile by Name endpoint to find out the
system-defined ID of the rule set associated with the desired profile. Alternatively, a list
of the available rule sets and their system-defined IDs may be retrieved through the Get
Available Rule Sets endpoint.
• RuleSetVersion: Replace this variable with the version of the rule set whose policies will
be retrieved.
Tip: Use either the Get Profile by ID or the Get Profile by Name endpoint to find out the
version of the rule set associated with the desired profile. Alternatively, a list of the
available rule sets and their supported versions may be retrieved through the Get
Available Rule Sets endpoint.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/rulesets/Trustwav
e-OWASPIntegration-Application/version/2017-09-18/policies HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 2187
[{
"id" : "modsecurity_slr_50_malware_detection.conf",
"name" : "Malware detection"
}, {
"id" : "modsecurity_crs_35_bad_robots.conf",
"name" : "Bad robots"
}, {
...
}, {
Note: The purpose of this endpoint is to identify each rule set/version combination (e.g.,
Trustwave-OWASPIntegration-Application version 2017-09-18) that may be assigned to a profile.
Note: The set of supported versions for a given rule set is subject to change as new versions are
made available. Although this doesn't affect existing profiles, it is always a best practice to
review and update profiles to use the latest version whenever possible.
Request
A request to retrieve rule sets is described below. When submitting this request, you will need
to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/rulesets
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 315
[{
"description": "NA",
"id": "OWASP-CRS-2.2.9",
"versions": [
"2017-08-01"
]
}, {
"description": "NA",
"id": "Trustwave-OWASPIntegration-Application",
"versions": [
"2017-08-01",
"2017-08-16",
"2017-09-18",
"2017-09-18"
]
}
]
Note: The set of rules associated with a policy may vary by a rule set's version.
Request
A request to retrieve rules is described below. When submitting this request, you will need to
define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• RuleSetID: Replace this variable with the system-defined ID of the rule set that contains
the policy whose rules will be retrieved.
Tip: Use either the Get Profile by ID or the Get Profile by Name endpoint to find out the
system-defined ID of the rule set associated with the desired profile. Alternatively, a list
of the available rule sets and their system-defined IDs may be retrieved through the Get
Available Rule Sets endpoint.
• RuleSetVersion: Replace this variable with the version of the rule set that contains the
policy whose rules will be retrieved.
Tip: Use either the Get Profile by ID or the Get Profile by Name endpoint to find out the
version of the rule set associated with the desired profile. Alternatively, a list of the
available rule sets and their supported versions may be retrieved through the Get
Available Rule Sets endpoint.
• PolicyID: Replace this variable with the system-defined ID of the policy whose rules will
be retrieved.
Tip: Use the Get Available Policies endpoint to retrieve a list of the available policies and
their system-defined IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/rulesets/Trustwav
e-OWASPIntegration-Application/version/2017-09-
18/policies/modsecurity_crs_35_bad_robots.conf/rules HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 274
Request
A request to retrieve templates is described below. When submitting this request, you will need
to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Data Type Description
id String Identifies a template by its system-defined ID.
name String Identifies a template by its name.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/templates
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 330
[{
"id": "03_Trustwave_OWASP_Integrated.json",
"name": "Trustwave OWASP Integrated Template"
}, {
"id": "02_OWASP.json",
"name": "OWASP Template"
Get Instance by ID
Request
A request to retrieve a WAF instance is described below. When submitting this request, you will
need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• InstanceID: Replace this variable with the system-defined ID of the desired instance.
Tip: Use the Get All Instances endpoint to retrieve a list of all available instances and
their system-defined IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response elements:
enabled_date String Indicates the date and time (GMT) at which the
instance was last modified.
Syntax:
m\/d\/YYYY HH:MM:SS AM|PM
prod_profile_enforcements Array This array contains objects that describe the
type of action that will be applied to threats
detected as a result of this instance
configuration.
Note: If this parameter reports an empty array,
then the deprecated prod_profile_action
parameter determines how detected threats
will be handled.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 246
{
"name" : "Site C",
"id" : "1234",
"prod_profile_id" : "23",
"prod_profile_name" : "Basic Profile",
"prod_profile_action" : "alert",
"audit_profile_id" : "0",
"audit_profile_name" : null,
"enabled_date" : "3\/6\/2016 6:45:19 PM",
"prod_profile_enforcements" : [{
"display_default_error_page" : true,
"name" : "Custom Response",
"response_headers" : {
"Profile" : "Basic"
},
"status" : 403,
"type" : "custom-response"
}
]
}
Important: This endpoint has been deprecated. Please use the Get Instance by ID endpoint
instead.
Note: For additional information about this legacy endpoint, please refer to the REST API Help
Center.
Tip: A profile cannot be deleted while in use by an instance. This endpoint allows the discovery
of the relevant instances.
Request
A request to retrieve instances is described below. When submitting this request, you will need
to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• ProfileID: Replace this variable with the system-defined ID of the desired profile.
Tip: Use the Get All Profiles endpoint to retrieve a list of profiles and their system-
defined IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/123/instances
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 90
[{
"id" : 147,
"name" : "Site A"
}, {
"id" : 488,
"name" : "Site B - Alternate"
}
]
Request
A request to retrieve a WAF profile is described below. When submitting this request, you will
need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• ProfileID: Replace this variable with the system-defined ID of the desired profile.
Tip: Use the Get All Profiles endpoint to retrieve a list of all available profiles and their
system-defined IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/0b97746d-
8e71-4f95-83bd-1a2bcd34e45f HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1729
{
"access_settings" : {
"country" : {
"blacklist" : [],
"whitelist" : []
},
"ignore_cookie" : [],
"ip" : {
"blacklist" : [],
"whitelist" : []
},
"referer" : {
"blacklist" : [],
"whitelist" : []
Important: This endpoint has been deprecated. Please use the Get Profile by ID endpoint
instead.
Note: For additional information about this legacy endpoint, please refer to the REST API Help
Center.
Get Template
Request
A request to retrieve a template is described below. When submitting this request, you will
need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• TemplateID: Replace this variable with the system-defined ID of the desired template.
Tip: Use the Get Available Templates endpoint to retrieve a list of all available templates
and their system-defined IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
GET
https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/templates/01_samp
le_2.json HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 4551
{
"access_settings": {
"country": {
"blacklist": [],
"whitelist": []
},
"ip": {
"blacklist": [],
"whitelist": [
"127.0.0.1"
]
},
"referrer": {
"blacklist": [],
"whitelist": []
},
"url": {
"blacklist": [],
"whitelist": []
Update Instance
Request
A request to update a WAF instance is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• InstanceID: Replace this variable with the system-defined ID of the desired instance.
Tip: Use the Get All Instances endpoint to retrieve a list of all available instances and
their system-defined IDs.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Optional and required request parameters for this endpoint are described below.
Note: Certain request parameters, as designated below, are always ignored. A request may
safely include these parameters, since they will not affect your configuration. This behavior
allows a script to update an instance by retrieving it, modifying a value, and then using this
endpoint to submit an update.
prod_profile_name String
Note: This request body parameter is always
ignored.
prod_profile_action String
Note: This parameter has been deprecated in
favor of the prod_profile_enforcements
parameter.
audit_profile_name String
Note: This request body parameter is always
ignored.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT https://api.edgecast.com/v2/mcc/customers/0001/waf/config/instances/1234
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
Content-Length: 479
{
"name" : "Site C",
"id" : "1234",
"prod_profile_id" : "23",
"prod_profile_name" : "Basic Profile",
"prod_profile_action" : "alert",
"audit_profile_id" : "0",
"audit_profile_name" : null,
"enabled_date" : "9\/7\/2016 6:45:19 PM",
"prod_profile_enforcements" : [{
"display_default_error_page" : true,
"name" : "Custom Response",
"response_headers" : {
"Profile" : "Basic"
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 28
{
"id" : "1234",
"success" : true
}
Update Profile
Request
A request to update a profile is described below. When submitting this request, you will need to
define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• ProfileID: Replace this variable with the system-defined ID of the desired profile.
Tip: Use the Get All Profiles endpoint to retrieve a list of all available profiles and their
system-defined IDs.
Request Body
Optional and required request parameters for this endpoint are described below.
target String
Important: This parameter is required when
defining a target.
target_match String
Important: This parameter is required when
defining a target.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
PUT https://api.edgecast.com/v2/mcc/customers/0001/waf/config/profiles/e032f437-
6220-4bf7-a5ea-1a2bcd34e45f HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Content-Type: application/json
Host: api.edgecast.com
Content-Length: 838
{
"access_settings": {
"country": {},
"ip": {},
"referer": {},
"url": {},
"user-agent": {}
},
"policies" : [
"modsecurity_crs_45_trojans.conf",
"modsecurity_crs_23_request_limits.conf",
"modsecurity_crs_30_http_policy.conf",
"modsecurity_crs_49_inbound_blocking.conf"
],
"general_settings": {
"allowed_http_methods": ["GET", "POST", "OPTIONS", "HEAD", "PUT",
"DELETE"],
"allowed_http_versions": ["HTTP\/0.9", "HTTP\/1.0", "HTTP\/1.1"],
"allowed_request_content_types": ["application\/x-www-form-
urlencoded", "multipart\/form-data", "application\/json"],
"anomaly_threshold": 10,
"arg_length": 0,
"arg_name_length": 0,
"combined_file_sizes": 0,
"engine": "anomaly",
"max_file_size": 0,
"max_num_args": 0,
"response_header_name": "X-CDN-Security-Audit",
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 93
{
"id": "e032f437-6220-4bf7-a5ea-1a2bcd34e45f",
"status": "success",
"success": true
}
This method provides a list of the available event log fields and their definitions.
Request
A request to retrieve event log fields is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 2475
{
"fields" : [{
"name" : "Timestamp",
"data_type" : "date",
"description" : "timestamp of log entry as UTC timestamp"
}, {
...
"name" : "id",
"data_type" : "string",
"description" : "ID of WAF event"
}
]
}
This method returns the total number of events that occurred during the specified time period.
Request
A request to find out the total number of events for a specified time period is described below.
When submitting this request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• StartDateTime: Required. Replace this variable with the start date/time for the report.
Only activity that took place after the specified date/time will be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• EndDateTime: Required. Replace this variable with the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/waf/eventlogs/count?start_time=2014-
10-20&end_time=2014-10-31 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 24
{
"count" : 3335091
}
This method returns paginated event log data. This data can be filtered by:
• Time Period
• Field values
Note: A request for event log entries may return information on thousands of requests. Due to
the amount of time that it would take to transmit this data, the response for this method has
been split up into pages. Retrieve all events that match the specified criteria by requesting each
page. Use the page_of response element in your script to cycle through each page.
Request
A request to retrieve event log data is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Important: A valid request must either include or exclude both date/time parameters
(i.e., start_time and end_time).
Note: Omitting both date/time parameters (i.e., start_time and end_time) will return
data for 24 hours prior to the time when the request was submitted.
• EndDateTime: Replace this variable with the end date/time for the report. Activity that
took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• PageNumber: Replace this variable with the page number that will be returned. This
method will only include log events corresponding to that page in the response.
Note: Omitting the page query string parameter in the request will return the first page.
• ItemsPerPage: Replace this variable with the number of log events that may be included
on each page. The number of items per page determines the number of pages that may
be returned.
Note: Omitting the page_size query string parameter in the request will return a
maximum of 100 log events per page.
Note: Time (i.e., Thh:mm:ss) is optional. If time is not specified, then a default time (i.e.,
00:00:00) will be used.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request reports:
• Basic Event Information: Each element in the events array describes the request and
the client that committed the violation(s).
• Sub Events: Specific information about each rule violation will be reported under the
Sub Events parameter.
Note: This endpoint only returns event fields (e.g., Epoch Time or Matched On) that contain
data. Therefore, the set of event fields returned by this endpoint may vary by event.
Epoch Time Number Indicates the Unix time, in seconds, at which the
violation took place.
(floating-
point) Syntax: Seconds.Microseconds
Matched On String Signature Detection Mode Only
Deprecated. Indicates the variable that identifies
where the violation was found.
Profile Type String Indicates whether the request was screened as a
result of an instance’s production or audit profile.
Valid values are:
• PRODUCTION
• AUDIT
Rule Severity Integer Signature Detection Mode Only
Deprecated. Indicates the severity of the violation.
This value may range from -1 to 6 where 6 represents
the lowest severity level.
Sub Events Object This response parameter contains a list of fields that
describe each sub event associated with the current
event. A sub event is reported for each rule violation
incurred by a request.
Matched On String Indicates the variable that identifies where the
violation was found.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 2676
{
"page_of" : 100,
"time_to" : 1473638400.0,
"time_from" : 1472688000.0,
"events" : [{
"Epoch Time" : 1473207640.345809,
"Profile Type" : "PRODUCTION",
"Client IP" : "192.12.22.25",
"Rule Message" : "Inbound Anomaly Score Exceeded (Total Score:
5, SQLi=3, XSS=0): Last Matched Message: 981255-Detects MSSQL code execution
and information gathering attempts",
"Sub Event Count" : 1,
"Timestamp" : "2016-09-07T00:20:40.345809Z",
"URL" : "http://www.mydomain.com/mywebpage.html",
"Country Code" : "US",
"Rule Policy" : "Inbound blocking",
"Action Type" : "CUSTOM_RESPONSE",
"Host" : "www.mydomain.com",
"Instance Name" : "My Instance",
"Profile Name" : "My Profile",
"Rule Tags" : "OWASP_CRS/ANOMALY/EXCEEDED",
"Rule ID" : 981176,
"Sub Events" : [{
"Matched On" : "ARGS:a",
"Rule Message" : "Detects MSSQL code execution
and information gathering attempts",
"Matched Data" : "'select *",
"Total Anomaly Score" : 5,
"Rule ID" : 981255,
"Rule Severity" : 2,
Request
A request to retrieve an event log entry is described below. When submitting this request, you
will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Tip: Use the Get Event Log Entries endpoint to retrieve a list of event log entries
and their system-assigned IDs.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request reports:
• Basic Event Information: Each element in the events array describes the request and
the client that committed the violation(s).
• Sub Events: Specific information about each rule violation will be reported under the
Sub Events parameter.
Note: This endpoint only returns event fields (e.g., Epoch Time or Matched On) that contain
data. Therefore, the set of event fields returned by this endpoint may vary by event.
Epoch Time Number Indicates the Unix time, in seconds, at which the
violation took place.
(floating-
point) Syntax: Seconds.Microseconds
Sub Event Count Integer Indicates the total number of sub events.
Client IP String Identifies the IP address of the client from which the
violation originated.
Matched On String Signature Detection Mode Only
Deprecated. Indicates the variable that identifies
where the violation was found.
Profile Type String Indicates whether the request was screened as a
result of an instance’s production or audit profile.
Valid values are:
• PRODUCTION
• AUDIT
Sub Events Array This response parameter contains a list of fields that
describe each sub event associated with the current
event. A sub event is reported for each rule violation
incurred by a request.
Matched On String Indicates the variable that identifies where the
violation was found.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/waf/eventlogs/ZG5cuvyo_poJuwGPzlcRJMc
w5qkW6DWLWtIrXFuYC1uQ6YJEN4mw1-imyLMl08TNYci2e5OaonfD7rw== HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1240
{
"event" : {
"Epoch Time" : 1473207640.345809,
"Profile Type" : "PRODUCTION",
"Sub Event Count" : 1,
"Client IP" : "192.12.22.25",
"Rule Tags" : [
"OWASP_CRS/ANOMALY/EXCEEDED"
],
"Timestamp" : "2016-09-07T00:20:40.345809Z",
"Rule Message" : "Inbound Anomaly Score Exceeded (Total Score: 5,
SQLi=3, XSS=0): Last Matched Message: 981255-Detects MSSQL code execution and
information gathering attempts",
"URL" : "http://www.mydomain.com/mywebpage.html",
"Country Code" : "US",
"Action Type" : "CUSTOM_RESPONSE",
"Host" : "www.mydomain.com",
"Instance Name" : "My Instance",
"Profile Name" : "My Profile",
"Rule ID" : 981176,
"Sub Events" : [{
"Matched On" : "ARGS:a",
"Rule Message" : "Detects MSSQL code execution and
information gathering attempts",
"Matched Data" : "'select *",
"Total Anomaly Score" : 5,
"Rule ID" : 981255,
"Rule Severity" : 2,
"Matched Value" : "'select * from site'"
}
],
"User Agent" : "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36",
This method identifies up to the top 10 events for a particular event log field. It returns a list of
these events stored in descending order of frequency.
Request
A request to retrieve a list of the most frequent events is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• Field: Required. Replace this variable with the name of the desired field. Use the Get
Available Event Log Fields (WAF) method to retrieve a list of the available fields.
• StartDateTime: Required. Replace this variable with the start date/time for the report.
Only activity that took place after the specified date/time will be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• EndDateTime: Required. Replace this variable with the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• ItemsPerPage: Replace this variable with the number of log events that may be included
on each page.
Note: Omitting the page_size query string parameter in the request will return a
maximum of 10 log events per page.
Note: Time (i.e., Thh:mm:ss) is optional. If time is not specified, then a default time (i.e.,
00:00:00) will be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/waf/eventlogs/top?field=Host&start_ti
me=2014-10-20&end_time=2014-10-21 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 382
{
"total" : 15112,
"signature" : [{
"count" : 15111,
"term" : "www.mydomain.com"
}, {
"count" : 1,
"term" : "www.mydomain.com:443"
}
The endpoints described in this section are designed to assist with the configuration of a rate
limiting policy. A brief description for each available endpoint is provided below.
Imporant: If you have not already updated your scripts and applications to leverage the
following endpoints, then we strongly encourage you to do so immediately.
Name Description
Get Configuration (Version Retrieves your Rate Limiting configuration.
1.0)
Update Configuration Updates your Rate Limiting configuration.
(Version 1.0)
Name Description
Get Action (Rate Limiting) - Indicates the type of action that will be taken when rate
Legacy limiting is applied to a request for a specific rule.
Get Available Action Types Indicates the available type of actions that may be applied to
(Rate Limiting) - Deprecated rate limited requests.
Get Available Group Types Indicates the available criteria for identifying unique
(Rate Limiting) – Deprecated requests.
Important: If you have not already updated your scripts and applications to leverage the Get
Configuration (Version 1.0) and Update Configuration (Version 1.0) endpoints, then we strongly
encourage you to do so immediately. The legacy endpoints will be discontinued on 12/16/2019.
Important: WAF Essential cannot be configured via our APIs. However, you may use our APIs to
retrieve event log data. Please contact your account manager to upgrade to the full version of
WAF and Rate Limiting.
Request
A request to retrieve the current rate limiting configuration is described below. When
submitting this request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1220
{
"customer_id": "0001",
"enabled_date": "2019-11-01T21:17:06.316715Z",
"id": "l56kgWVG",
"last_modified_date": "2019-11-01T21:17:06.316850Z",
"limits": [{
"action": {
"duration_sec": 10,
"id": "JMctNQKw",
"name": "action",
"type": "drop-request"
},
"condition_groups": [{
"conditions": [{
"op": {
"type": "EM",
"values": [
".aspx"
]
},
Important: If you have not already updated your scripts and applications to leverage the Get
Configuration (Version 1.0) and Update Configuration (Version 1.0) endpoints, then we strongly
encourage you to do so immediately. The legacy endpoints will be discontinued on 12/16/2019.
Important: WAF Essential cannot be configured via our APIs. However, you may use our APIs to
retrieve event log data. Please contact your account manager to upgrade to the full version of
WAF and Rate Limiting.
Request
A request to update the rate limiting configuration is described below. When submitting this
request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Pass the following request body parameters:
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"name": "Rate Limiting",
"limits": [{
"action": {
"type": "drop-request"
},
"disabled": false,
"duration_sec": 5,
"num": 30000,
"name": "Drop Requests",
"condition_groups": [{
"conditions": [{
"op": {
"type": "EM",
"values": [
".aspx"
]
},
"target": {
"type": "FILE_EXT"
}
}
]
}
]
}
]
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 70
{
"id": "0001",
"status": "success",
"success": true
}
Important: This deprecated endpoint has been discontinued. If you have not already updated
your scripts and applications to leverage the Get Configuration (Version 1.0) and Update
Configuration (Version 1.0) endpoints, then we strongly encourage you to do so immediately.
This endpoint indicates the action that will be applied to a request on which rate limiting will be
enforced.
HTTP Method Request URI
GET https://api.edgecast.com/v2/mcc/customers/AccountNumber/defend/
rate_limiting/config/enforcement/ActionTypeID
Note: For additional information about this legacy endpoint, please refer to the REST API Help
Center.
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
This endpoint describes each available action type. An action type determines the type of action
that will take place on rate limited requests.
Request
A request to retrieve the set of available action types is described below. When submitting this
request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/config_options/e
nforcements HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1591
[{
"friendly_name" : "Redirect (HTTP 302)",
"type" : "redirect-302",
"help" : "Sends the client an HTTP 302 redirect to the given URL.",
"parameters" : [{
"type" : "string",
"required" : true,
"friendly_name" : "URL",
"name" : "url",
"help" : "The URL to redirect to."
}
]
}, {
"friendly_name" : "Custom Response",
"type" : "custom-response",
"help" : "Sends the client a custom response.",
"parameters" : [{
"name" : "response_body_base64",
"base64_encoded" : true,
"required" : true,
"friendly_name" : "Response",
"type" : "string",
"help" : "The response to send the client."
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
This endpoint provides a list of the available criteria that may be used to group similar requests.
The rate limiting policy may be applied independently to each group identified by the system.
Request
A request to retrieve group types is described below. When submitting this request, you will
need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/config_options/d
imensions HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 297
[{
"friendly_name" : "IP Address",
"name" : "IP",
"help" : "The IP address of the client making a request."
}, {
"friendly_name" : "User Agent",
"name" : "USER_AGENT",
"help" : "The User Agent of the client making a request."
}
]
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
Indicates the available methods for defining a match between a match condition and a match
value.
Request
A request to retrieve match types is described below. When submitting this request, you will
need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/config_options/r
ules/operators HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 125
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
This endpoint retrieves a list of the available types of conditions for identifying a request that
should be rate limited.
Request
A request to retrieve a list of the available match conditions types is described below. When
submitting this request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
available match condition:
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/config_options/r
ules/variables HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 980
[{
"friendly_name": "IP Addresses",
"type": "REMOTE_ADDR",
"help": "The IP(s) of the client(s) who make a request."
}, {
"friendly_name": "Request URL",
"type": "REQUEST_URI",
"help": "The URL the client requested (/services/security)."
}, {
"help": "The headers provided by the client.",
"friendly_name": "Request Headers",
"valid_values": [{
"friendly_name": "Host",
"help": "The Host header.",
"value": "Host"
}, {
"friendly_name": "User-Agent",
"help": "The User-Agent header.",
"value": "User-Agent"
Important: This deprecated endpoint has been discontinued. If you have not already updated
your scripts and applications to leverage the Get Configuration (Version 1.0) and Update
Configuration (Version 1.0) endpoints, then we strongly encourage you to do so immediately.
This endpoint retrieves the settings associated with a specific condition group. This type of
group defines one or more match conditions that identify requests that are eligible for rate
limiting.
Note: For additional information about this legacy endpoint, please refer to the REST API Help
Center.
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
Indicates the current status of a configuration update submitted via the Update Configuration
(Rate Limiting) endpoint.
Request
A request to retrieve status information is described below. When submitting this request, you
will need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• JobID: Replace this variable with the job ID (job_id) provided in the response for the
Update Configuration (Rate Limiting) endpoint.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/job/503785d1-
d027-4066-ad42-86980cd996c518786 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 161
{
"desc" : "POST instance job",
"id" : "503785d1-d027-4066-ad42-86980cd996c518786",
"message" : "0001.json",
"options" : "na",
"status" : "success"
}
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
Request
A request to retrieve the current rate limiting configuration is described below. When
submitting this request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
status Integer Indicates the HTTP status code for the custom
response sent to rate limited requests.
Note: This response element is only included in
the response when the type property is set to
"custom-response."
path Object Contains URL path criteria that defines the set
of requests eligible for rate limiting by the
current rule.
is_negated Boolean Indicates whether this scope condition will be
satisfied when the request's URL path matches
or does not match the value defined by the
value|values parameter.
Valid values are:
• True: Does not match
• False: Matches
GET https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/config
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1229
{
"customer_id": "0001",
"enabled_date": "2018-04-03T23:52:24.590818Z",
"id": "e0fa44b4-ede1-4056-8bfe-5daa481a26c10001",
"name": "name",
"tuples": [{
"dimensions": [
"IP",
"USER_AGENT"
],
"disabled": true,
"duration_sec": 60,
"enforcements": [{
"duration_sec": 60,
"id": "de7cd68c-b41e-4305-9202-
3443515df8190001",
"name": "Rate Limiting Action",
"type": "redirect-302",
"url": "http://sec.example.com/unavailable.html"
}
"http://cdn.example.com/index.php"
]
},
"variable": [{
"type": "REQUEST_URI"
}
]
}
],
"scope": {
"host": {
"is_negated": false,
"type": "EM",
"values": [
"www.example.com"
]
},
"path": {
"is_negated": false,
"type": "GLOB",
"value": "*"
}
}
}
],
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
Request
A request to update the rate limiting configuration is described below. When submitting this
request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
value String
Important: This parameter is required when
the type parameter is set to one of the
following values: GLOB or REGEX. Otherwise, it
should not be included.
value String
Important: This parameter is required when
the type parameter is set to one of the
following values: GLOB or REGEX. Otherwise, it
should not be included.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Data Type Description
success Boolean Indicates whether the Rate Limiting configuration was updated.
Valid values are:
• true: Indicates that the configuration was updated.
• false: Indicates that an error took place.
job_id String Indicates the system-defined ID assigned to the rate limiting
configuration update.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
POST https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/config
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
Content-Length: 1229
{
"customer_id": "0001",
"enabled_date": "2018-04-03T23:52:24.590818Z",
"id": "e0fa44b4-ede1-4056-8bfe-5daa481a26c10001",
"name": "name",
"tuples": [{
"dimensions": [
"IP",
"USER_AGENT"
],
"disabled": true,
"duration_sec": 60,
"enforcements": [{
"duration_sec": 60,
"id": "de7cd68c-b41e-4305-9202-
3443515df8190001",
"name": "Rate Limiting Action",
"type": "redirect-302",
"url": "http://sec.example.com/unavailable.html"
}
],
"id": "1824dd0f-7791-41f7-86de-80817760f4240001",
"limit": 100,
"name": "Rate Limiting Rule",
"rules": [{
"chained_rule": [],
"id": "31385b47-5f5a-41d7-90ab-
d891b28a8ca80001",
"name": "Condition Group",
"operator": {
"http://cdn.example.com/index.php"
]
},
"variable": [{
"type": "REQUEST_URI"
}
]
}
],
"scope": {
"host": {
"is_negated": false,
"type": "EM",
"values": [
"www.example.com"
]
},
"path": {
"is_negated": false,
"type": "GLOB",
"value": "*"
}
}
}
],
"type": "ddos-coordinator"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 80
{
"success" : true,
"job_id" : "62723a12-4194-4ec7-9490-38382031d2a018D7C"
}
Important: This deprecated endpoint will be discontinued on 12/16/2019. If you have not
already updated your scripts and applications to leverage the Get Configuration (Version 1.0)
and Update Configuration (Version 1.0) endpoints, then we strongly encourage you to do so
immediately.
This endpoint validates a rate limiting configuration. This verification process may be performed
prior to submitting it via the Update Configuration (Rate Limiting) endpoint.
Request
A request to validate a rate limiting configuration is described below. When submitting this
request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
The request parameters for this endpoint are described below.
value String
Important: This parameter is required when
the type parameter is set to one of the
following values: GLOB or REGEX. Otherwise, it
should not be included.
value String
Important: This parameter is required when
the type parameter is set to one of the
following values: GLOB or REGEX. Otherwise, it
should not be included.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Data Type Description
success Boolean Indicates whether the submitted Rate Limiting configuration is
valid.
Valid values are:
• true: Indicates that the configuration is valid.
• false: Indicates that the configuration is invalid.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"customer_id": "0001",
"enabled_date": "2018-04-03T23:52:24.590818Z",
"id": "e0fa44b4-ede1-4056-8bfe-5daa481a26c10001",
"name": "name",
"tuples": [{
"dimensions": [
"IP",
"USER_AGENT"
],
"disabled": true,
"duration_sec": 60,
"enforcements": [{
"duration_sec": 60,
"id": "de7cd68c-b41e-4305-9202-
3443515df8190001",
"name": "Rate Limiting Action",
"type": "redirect-302",
"url": "http://sec.example.com/unavailable.html"
}
],
"id": "1824dd0f-7791-41f7-86de-80817760f4240001",
"limit": 100,
"name": "Rate Limiting Rule",
"rules": [{
"chained_rule": [],
"id": "31385b47-5f5a-41d7-90ab-
d891b28a8ca80001",
"name": "Condition Group",
"operator": {
"is_negated": false,
"type": "EM",
"http://cdn.example.com/index.php"
]
},
"variable": [{
"type": "REQUEST_URI"
}
]
}
],
"scope": {
"host": {
"is_negated": false,
"type": "EM",
"values": [
"www.example.com"
]
},
"path": {
"is_negated": false,
"type": "GLOB",
"value": "*"
}
}
}
],
"type": "ddos-coordinator"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 80
{
"success" : true
}
Name Description
Get Available Event Log Fields Retrieves a list of the available event log fields.
(Rate Limiting)
Get Event Log Entries (Rate Retrieves event log information for a set of rate limited
Limiting) requests.
Get Event Log Entry (Rate Retrieves event log information for a specific rate limited
Limiting) request.
Get Event Log Entry Count Indicates the total number of rate limited requests that meet
(Rate Limiting) the specified criteria.
Get Top Event Log Entries Indicates the type of records that are most frequently rate
(Rate Limiting) limited.
Request
A request to retrieve a listing of fields is described below. When submitting this request, you will
need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/eventlogs/fields
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 2196
{
"fields" : [{
"name" : "id",
"data_type" : "string",
"description" : "ID of event"
}, {
...
}, {
"name" : "Country Code",
"data_type" : "string",
"description" : "Two letter country code"
}
]
}
This endpoint returns paginated event log data. This data can be filtered by:
• Time Period
• Field values
Note: A request for event log entries may return information on thousands of requests. Due to
the amount of time that it would take to transmit this data, the response for this endpoint has
been split up into pages. Retrieve all events that match the specified criteria by requesting each
page. Use the page_of response element in your script to cycle through each page.
Request
A request to retrieve event log data is described below. When submitting this request, you will
need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• StartDateTime: Replace this variable with the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report.
Format: YYYY-MM-DDThh:mm:ss
Important: A valid request must either include or exclude both date/time parameters
(i.e., start_time and end_time).
Note: Omitting both date/time parameters (i.e., start_time and end_time) will return
data for 24 hours prior to the time when the request was submitted.
• EndDateTime: Replace this variable with the end date/time for the report. Activity that
took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• ItemsPerPage: Replace this variable with the number of events that may be included on
each page. The number of items per page determines the number of pages that may be
returned.
The maximum value for this variable is 1000.
Omitting the per_page query string parameter in the request will return a
maximum of 10 entries per page.
Note: Omitting a start date/time will return the events that took place within the last 24 hours.
Note: Time (i.e., Thh:mm:ss) is optional when defining a start and end date/time. If time is not
specified, then a default time (i.e., 00:00:00) will be used. For more information on date/time
format, please refer to Appendix B: Report Date/Time Format.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Data Type Description
page_of Integer Indicates the total number of pages in the
report.
Reminder: This value is determined by the total
number of eligible event log entries divided by
the maximum number of entries per page.
Both of these factors are defined in the request
URL.
Status String Identifies by name the HTTP status code for the
response to a rate limited request.
Format: HTTP_STATUS_Name
Example: HTTP_STATUS_FOUND
In the above sample value, the HTTP status
code describing the response for a rate limited
request was a 302 Found.
Epoch Time Number Indicates the Unix time, in seconds, at which
the request was processed.
(floating-
point) Syntax: Seconds.Microseconds
Rate Limiting Enforcement String This field is reserved for future use.
Rule ID
@fields.COMMON_Header Object This field is reserved for future use.
Country Code String Identifies the country from which the request
originated by its ISO 3166 country code.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/eventlogs?start_
time=2015-06-30T20:00:00&end_time=2015-06-30T21:00:00&page=1 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 9091
{
"page_of" : 1,
"time_to" : 1473638400.0,
"time_from" : 1472688000.0,
"events" : [{
"Status" : "HTTP_STATUS_SERVICE_NOT_AVAILABLE",
"Epoch Time" : 1473470411.2213371,
"Host" : "cdn.mydomain.com",
"Client IP" : "192.12.16.24",
"URL" : "http://cdn.mydomain.com/000001/mywebpage.html",
"Timestamp" : "2016-09-10T01:20:11.221337Z",
"Rate Limiting Enforcement Rule ID" : "XXXNAXXX@ddos.RULE_ID",
"@fields.COMMON_HEADER" : {},
"Country Code" : "US",
"Rate Limiting Enforcement Tuple ID" : "2c85167d-865d-4701-
9a9a-11410327f8610001",
"Rate Limiting Enforcement Type" : "DROP_REQUEST",
"Referer" : "XXXNAXXX@fields.REFERER",
"Rate Limiting Enforcement Start Epoch" : 1473470411000,
"Request Method" : "HTTP_METHOD_GET",
"Rate Limiting Enforcement Percentage" : 96.97,
"Rate Limiting Enforcement Duration" : 280,
"User Agent" : "Server Load Tester",
"id" : "z-dgB40S7zgoqT8Nh_-
zTyhxxLprMULRXpQLDCOwjOC_D1RvHs9qFCL4i88CPJ7SW6ssFBGPsmQ9GqiO_A_LMw=="
}, {
...
}, {
"Status" : "HTTP_STATUS_SERVICE_NOT_AVAILABLE",
"Epoch Time" : 1473470402.730159,
"Host" : "cdn.mydomain.com",
"Client IP" : "192.12.16.24",
This endpoint retrieves a specific event log entry by its system-defined ID.
Request
A request to retrieve an event log entry is described below. When submitting this request, you
will need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• EventID: Replace this variable with the encoded ID of the desired event log entry. Use
the Get Event Log Entries (Rate Limiting) endpoint to retrieve a list of event log entries
and an encoded version of their system-assigned IDs.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 932
{
"event" : {
"Status" : "HTTP_STATUS_SERVICE_NOT_AVAILABLE",
"Epoch Time" : 1473470411.2213371,
"Rate Limiting Enforcement Rule ID" : "XXXNAXXX@ddos.RULE_ID",
"Client IP" : "192.12.16.24",
"URL" : "http://cdn.mydomain.com/000001/mywebpage.html",
"Timestamp" : "2016-09-10T01:20:11.221337Z",
"Rate Limiting Enforcement Duration" : 280,
"Country Code" : "US",
"@fields.COMMON_HEADER" : {},
"Rate Limiting Enforcement Tuple ID" : "2c85167d-865d-4701-9a9a-
11410327f86114631",
"Rate Limiting Enforcement Type" : "DROP_REQUEST",
"Referer" : "XXXNAXXX@fields.REFERER",
"Rate Limiting Enforcement Start Epoch" : 1473470411000,
"Request Method" : "HTTP_METHOD_GET",
"Rate Limiting Enforcement Percentage" : 96.97,
"Host" : "cdn.mydomain.com",
"User Agent" : "Server Load Tester",
"id" : "z-dgB40S7zgoqT8Nh_-
zTyhxxLprMULRXpQLDCOwjOC_D1RvHs9qFCL4i88CPJ7SW6ssFBGPsmQ9GqiO_A_LMw=="
}
}
This endpoint indicates the total number of event log entries that occurred within a specified
time period.
Request
A request to retrieve a sum of event log entries is described below. When submitting this
request, you will need to define the following variables:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• StartDateTime: Required. Replace this variable with the start date/time for the report.
Only activity that took place after the specified date/time will be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• EndDateTime: Required. Replace this variable with the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
Note: Time (i.e., Thh:mm:ss) is optional when defining a start and end date/time. If time is not
specified, then a default time (i.e., 00:00:00) will be used. For more information on date/time
format, please refer to Appendix B: Report Date/Time Format.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/eventlogs/count?
start_time=2015-06-30&end_time=2015-07-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 22
{
"count" : 43061
}
This endpoint provides the top events over a given time period.
Request
A request to retrieve the top occurring event log entries is described below. When submitting
this request, you will need to define the following variables:
• AccountNumber: Required. Replace this variable with your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• Field: Required. Replace this variable with the name of the desired field. Use the Get
Event Log Fields (Rate Limiting) endpoint to retrieve a list of the available fields.
• StartDateTime: Required. Replace this variable with the start date/time for the report.
Only activity that took place after the specified date/time will be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• EndDateTime: Required. Replace this variable with the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• ItemsPerPage: Replace this variable with the number of log events that may be included
on each page.
Note: Omitting the page_size query string parameter in the request will return a
maximum of 10 log events per page.
Note: Time (i.e., Thh:mm:ss) is optional when defining a start and end date/time. If time is not
specified, then a default time (i.e., 00:00:00) will be used. For more information on date/time
format, please refer to Appendix B: Report Date/Time Format.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
available action type:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/mcc/customers/0001/defend/rate_limiting/eventlogs/top?fi
eld=Referrer&start_time=2015-10-28&end_time=2015-11-05 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 262
{
"time_to" : 1446681600.0,
"total" : 13100,
"time_from" : 1445990400.0,
"results" : [{
"count" : 8700,
"term" : "www.exampledomain1.com"
}, {
"count" : 4400,
"term" : "www.exampledomain2.com"
}
]
}
Retrieves the propagation status for a deploy request to the production environment.
Important: This endpoint does not support the retrieval of propagation status for deploy
requests submitted to the staging environment.
Request
A request to retrieve status information is described below. When submitting this request, you
will need to define the following terms:
• xxxx: Replace this term with the desired customer account number.
• DeployRequestID: Replace this term with the system-defined ID for the desired deploy
request.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
Staging Environment Deploy Requests
Requesting propagation status for a deploy request submitted to the Staging environment will
return a 500 Internal Server Error with the following response body:
{
"Message": "Operation Error. Contact Administrator"
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 7255
{
"Status": "propagating",
"Percent_propagated": 2.666083916083916,
"Pops": [{
"name": "South America : Valparaiso, Chile",
"percentage_propagated": 5.263157894736842
}, {
...
"name": "South America : Lima, Peru",
"percentage_propagated": 10.0
}, {
"name": "North America : San Jose",
"percentage_propagated": 4.0
}, {
"name": "Australia : Auckland",
"percentage_propagated": 3.7037037037037033
}
]
}
This endpoint retrieves a comprehensive list of edge nodes (i.e., POPs). This list includes
metadata describing each edge node, such as its location and IP blocks.
Request
A request to retrieve a list of edge nodes is described below. When submitting this request, you
will need to define the following term:
• xxxx: This term should be replaced by the account number associated with the desired
customer account.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
Code A string that identifies an edge node by its three letter abbreviation.
Continent A string that indicates the continent on which the edge node is
located.
City A string that indicates the city where the edge node is located.
V4 Lists each public IP block (IPv4) associated with an edge node.
IPAddressRange This tag represents a single IP block (IPv4) associated with an edge
node.
StartIp A string that indicates the start IP address of the IP block (IPv4)
associated with an edge node.
EndIp A string that indicates the end IP address of the IP block (IPv4)
associated with an edge node.
SubnetMask A string that indicates the edge node's IPv4 subnet mask. A routing
prefix is used to identify a subnet mask.
V6 Lists each public IP block (IPv6) associated with an edge node.
IPAddressRange This tag represents a single IP block (IPv6) associated with an edge
node.
StartIp A string that indicates the start IP address of the IP block (IPv6)
associated with an edge node.
EndIp A string that indicates the end IP address of the IP block (IPv6)
associated with an edge node.
SubnetMask A string that indicates the edge node's IPv6 subnet mask. A routing
prefix is used to identify a subnet mask.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1130
[{
"Code" : "OXR",
"Continent" : "North America",
"City" : "Los Angeles",
"V4" : [{
"StartIp" : "46.22.69.0",
"EndIp" : "46.22.69.255",
"SubnetMask" : "24"
}, {
"StartIp" : "68.232.40.0",
"EndIp" : "68.232.40.255",
"SubnetMask" : "24"
}, {
"StartIp" : "72.21.84.0",
"EndIp" : "72.21.84.255",
"SubnetMask" : "24"
}, {
"StartIp" : "72.21.94.0",
"EndIp" : "72.21.94.255",
"SubnetMask" : "24"
}, {
"StartIp" : "93.184.218.0",
Note: For additional information about these legacy endpoints, please refer to the REST API
Help Center.
The following endpoints, which automate CDN Object Storage administration, have been
discontinued:
Name Description
Add Buckets - Discontinued Adds one or more buckets to a CDN Object Storage location.
Delete Bucket – Discontinued Deletes a bucket.
Delete Key Pair – Discontinued Deletes an access and secret key pair.
Get All Buckets – Discontinued Retrieves all available buckets.
Get All CDN Object Storage Retrieves a list of CDN Object Storage locations.
Locations – Discontinued
Get Buckets by CDN Object Retrieves a list of buckets associated with a CDN Object
Storage Location – Storage location.
Discontinued
Get CDN Object Storage Retrieves a CDN Object Storage location.
Location - Discontinued
Get CDN Object Storage Retrieves information about a CDN Object Storage location.
Location Information –
Discontinued
Get Hostname – Discontinued Retrieves the hostname associated with a CDN Object
Storage location.
Get Key Pairs – Discontinued Retrieves the key pairs associated with a CDN Object
Storage location.
Update Key Pair - Discontinued Updates a key pair associated with a CDN Object Storage
location.
Overview
Reporting endpoints allow you to generate reports based on CDN activity for your account.
Billing
This section describes billing-related endpoints.
Retrieves a list of billing regions. A billing region must be specified when retrieving billing
statistics for a particular month through the Get Traffic Usage endpoint.
Request
A request to retrieve a list of billing regions is described below.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
Code A string that identifies the abbreviation associated with the billing
region.
Description A string that provides a description for the billing region.
Id An integer that defines the ID associated with the billing region.
Name A string that provides the name of the billing region.
Status An integer that provides status information for the billing region. Return
values for this parameter are:
• 0: Indicates that the billing region is inactive.
• 1: indicates that the billing region is active.
EdgeNodes This response element contains a listing of POPs associated with the
current billing region.
EdgeNodeId An integer that identifies an edge node (POP) by its system-defined ID.
Code A string that identifies an edge node by its three letter abbreviation.
Continent A string that indicates the continent on which the edge node is located.
City A string that indicates the city where the edge node is located.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 20889
[{
"Code" : "GL",
"Description" : "Global",
"Id" : -1,
"Name" : "Global",
"Status" : 1,
"EdgeNodes" : [{
"EdgeNodeId" : 2142,
"Code" : "AMS",
"Continent" : "Europe",
"City" : "Amsterdam"
}, {
...
}, {
"EdgeNodeId" : 3017,
"Code" : "PVU",
"Continent" : "North America",
"City" : "Provo (upLynk Utah Office)"
}, {
"EdgeNodeId" : 3018,
"Code" : "VEN",
"Continent" : "Europe",
"City" : "Venlo"
}
]
}, {
"Code" : "NE",
"Description" : "North America & Europe",
"Id" : 0,
"Name" : "North America & Europe",
"Status" : 1,
"EdgeNodes" : [{
Returns billing usage data for the specified month. This data may be filtered by one of the
following criteria:
• Billing Region
• Country
• POP(s)
Request
A request to retrieve billing usage data is described below. When submitting this request, you
will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
3: HTTP Large
7: HTTP Large (SSL Traffic Only)
8: HTTP Small
9: HTTP Small (SSL Traffic Only)
14: Application Delivery Network (ADN)
15: Application Delivery Network (ADN) – (SSL Traffic Only)
• BillingMonth: Replace this variable with the 1st of the month for which billing
information will be returned.
Syntax: YYYY-MM-01
• RegionID: Replace this variable with the ID of the billing region for which billing
information will be returned.
Note: The region, country, and pops query string parameters are optional and mutually
exclusive. A request to this endpoint may include up to one of these filters. The region
query string parameter (e.g., ®ion=0) should only be defined when billing data
should be restricted to the specified billing region.
• CountryCode: Replace this variable with the ISO 3166 code corresponding to the
country for which billing information will be returned.
Tip: A list of country codes is available from the Country Codes (ISO 3166) article in the
CDN Help Center.
• POPs: Optional. Limit report data to one or more POPs by replacing this variable with a
comma-delimited list of the desired POPs.
Tip: Use the Get All Edge Nodes endpoint to retrieve a list of POPs and their codes.
Note: The region, country, and pops query string parameters are optional and mutually
exclusive. A request to this endpoint may include up to one of these filters. The pops
query string parameter (e.g., oxr,dca,mia) should only be defined when billing data
should be restricted to the specified POP(s).
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response elements for each
billing region returned by this endpoint:
RegionId Integer Indicates the ID of the region for which billing data was
provided. This ID will always match the value defined in
the request's region query string parameter.
Note: This response parameter is only returned when
the region query string parameter is defined in the
request.
StartDate String Indicates the month for which billing information was
reported.
Syntax: YYYY-MM-01
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/14/units/0/billingtraffic
?begindate=2018-01-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 248
[{
"AccountNumber": "0001",
"MediaTypeId": 14,
"Pops": "all",
"UsageUnits": 0,
"Data": [{
"Bandwidth": 1484302.2916001333,
"DataTransferred": 191320916.11106589,
"StartDate": "01\/1\/2018 12:00:00 AM"
}
]
}
]
Request
A request to retrieve a customer's account number is described below. When submitting this
request, you will need to define the following term:
• CustomID: This term should be replaced by the custom ID associated with the desired
customer account.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/accountnumber?customercustomid=CID01
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 245
{
"AccountNumber" : "0001"
}
Request
A request to retrieve a customer's name is described below. When submitting this request, you
will need to define the following term:
• xxxx: This term should be replaced by the account number associated with the desired
customer account.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
AccountName A string that identifies the name associated with the specified
customer account number.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 34
{
"AccountName" : "My Company"
}
Note: Core Reporting endpoints can only generate reports for CDN activity within the last 18
months.
This platform-independent endpoint retrieves the total amount of data transferred (bytes) for
your CDN account over a specific time period.
Note: This endpoint does not include data for transactions that did not complete during the
requested time period, even if the transaction started before or during the time period covered
by the report.
Request
A request to retrieve data transferred is described below. When submitting this request, you will
need to define the following terms:
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
• POPs: Optional. You can choose to limit report data to one or more POPs.
All POPs: If you would like to generate report data for all POPs, then you should
not include "&pops=POPs " parameter in the request.
POP-Specific Report: Replace the term POPs with a comma-delimited list of the
desired POPs (e.g., oxr,dca,mia). Each POP's code is reported by the Code
response element in the Get All Edge Nodes endpoint.
• RegionID: Optional. You can choose to limit report data by region. Use the Get Billing
Regions endpoint to retrieve a listing of regions and their IDs. If the regionid parameter
is not specified, then report data for all regions will be returned.
Important: Returns data in 5 minute intervals (e.g., 00:00:00, 00:05:00, 00:10:00, etc.).
Specifying a time that falls in between a 5 minute interval (e.g., 00:02:59) will include all data
associated with that 5 minute interval (e.g., 00:00:00 – 00:04:59).
Note: The time portion (i.e., hh:mm:ss) of the StartDateTime and EndDateTime request
parameters is optional. If a specific time is not specified, then a default time (i.e., 00:00:00) will
be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Bytes An integer that indicates the number of bytes transferred over the given
time period. This statistic includes CDN activity for all platforms.
Note: Keep in mind that the pops request element determines whether
Returns the amount of data transferred for the entire CDN network or if it
will be limited to specific POP locations.
GET
https://api.edgecast.com/v2/reporting/customers/0001/bytestransferred?begindate=2012
-11-01&enddate=2012-12-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 43
{
"Bytes" : 257764320845815459845511324
}
Retrieves the total amount of hits over a given time period for each cache status on a specified
platform.
Request
A request to retrieve cache status statistics is described below. When submitting this request,
you will need to define the following terms:
• Platform: This term should be replaced by an integer that indicates the platform for
which a report will be generated. Valid values for this term are:
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
Important: Returns data in 1 hour intervals (e.g., 00:00:00, 01:00:00, 02:00:00, etc.). Specifying a
time that falls in between a 1 hour interval (e.g., 00:50:05) will include all data associated with
that hour (e.g., 00:00:00 – 00:59:59).
Note: The time portion (i.e., hh:mm:ss) of the StartDateTime and EndDateTime request
parameters is optional. If a specific time is not specified, then a default time (i.e., 00:00:00) will
be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
cache status returned by this endpoint:
Name Description
Hits An integer that indicates the total number of hits for the cache status
identified by the Name return parameter.
Name A string that identifies a cache status by its name. Valid return values are
defined below.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/cachestats?begindate=20
11-06-01&enddate=2011-07-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 142
[{
"Hits" : 87619673,
"Name" : "TCP_HIT"
}, {
"Hits" : 22725,
"Name" : "TCP_MISS"
}, {
"Hits" : 8750,
Important: This endpoint has been deprecated and support for it will slowly be phased out. Data
collection for this endpoint stopped as of 11/1/2012. However, for the purpose of viewing
historical data, this endpoint will remain available for a reasonable time period.
Retrieves the total amount of hits and data transferred over a given time period for each
CNAME on a specified platform. For the purpose of this endpoint, a CNAME consists of all edge
CNAMEs and the system-defined hostname (e.g., wpc.0001.edgecastcdn.net) assigned to your
customer account.
Note: This endpoint does not include hits/data for transactions that did not complete during the
requested time period, even if the transaction started before or during the time period covered
by the report.
Request
A request to retrieve CNAME statistics is described below. When submitting this request, you
will need to define the following terms:
• Platform: This term should be replaced by an integer that indicates the platform for
which a report will be generated. Valid values for this term are:
2: Flash Media Streaming
3: HTTP Large
8: HTTP Small
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
Important: Returns data in 1 hour intervals (e.g., 00:00:00, 01:00:00, 02:00:00, etc.). Specifying a
time that falls in between a 1 hour interval (e.g., 00:50:05) will include all data associated with
that hour (e.g., 00:00:00 – 00:59:59).
Note: The time portion (i.e., hh:mm:ss) of the StartDateTime and EndDateTime request
parameters is optional. If a specific time is not specified, then a default time (i.e., 00:00:00) will
be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
CNAME returned by this endpoint:
Name Description
Bytes An integer that indicates the total number of data transferred (bytes) for a
particular CNAME.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/cnames?begindate=2011-
06-01&enddate=2011-07-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 216
[{
"Bytes" : 26182770916,
"Hits" : 228445,
"Name" : "wpc.0001.edgecastcdn.net"
}, {
"Bytes" : 6958089484,
"Hits" : 16646983,
"Name" : "gp1.wpc.edgecastcdn.net"
}, {
"Bytes" : 36890,
"Hits" : 97,
"Name" : "images.hostname.org"
}
]
Returns the current amount of storage space being used on a CDN origin server.
Request
A request to retrieve current storage space usage is described below. When submitting this
request, you will need to define the following term:
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
UsageResult A number (floating-point) that indicates the current amount of disk space
usage (GB) on a CDN origin server.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 20
{
"UsageResult" : 85.5
}
Retrieves the total amount of data transferred over the specified platform in a given time
period.
Request
A request to retrieve data transferred information by platform is described below. When
submitting this request, you will need to define the following terms:
• Platform: This term should be replaced by an integer that indicates the platform for
which a report will be generated. Valid values for this term are:
2: Flash Media Streaming
3: HTTP Large
7: HTTP Large (SSL Traffic Only)
8: HTTP Small
9: HTTP Small (SSL Traffic Only)
14: Application Delivery Network (ADN)
15: Application Delivery Network (ADN) – (SSL Traffic Only)
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
• POPs: Optional. You can choose to filter report data to one or more POPs as indicated
below.
All POPs: If you would like to generate report data for all POPs, then you should
not include "&pops=POPs " parameter in the request.
POP-Specific Report: Replace the term POPs with a comma-delimited list of the
desired POPs (e.g., oxr,dca,mia). Each POP's code is reported by the Code
response element in the Get All Edge Nodes endpoint.
Important: Returns data in 5 minute intervals (e.g., 00:00:00, 00:05:00, 00:10:00, etc.).
Specifying a time that falls in between a 5 minute interval (e.g., 00:02:59) will include all data
associated with that 5 minute interval (e.g., 00:00:00 – 00:04:59).
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Bytes An integer that indicates the total number of bytes that were transferred
on the specified platform over a given time period.
Note: Keep in mind that the pops request parameter determines whether
Returns the amount of data transferred for the entire CDN network or if it
will be limited to specific POP locations.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/bytestransferred?begind
ate=2012-11-01&enddate=2012-12-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 21
{
"Bytes" : 64457041333
}
Retrieves the amount of data transferred (bytes) for your CDN account. The data returned by
this report can be filtered to only include CDN traffic that meets the following criteria:
• Date range
• Platform
• POP locations
• Region
Additionally, you can define the time interval that will be used to report the amount of data
transferred.
Note: This endpoint does not include data for transactions that did not complete during the
requested time period, even if the transaction started before or during the time period covered
by the report.
Request
A request to retrieve data transferred information by time interval is described below. When
submitting this request, you will need to define the following terms:
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that completed after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that completed after the specified date/time will be excluded from the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
• Platform: Optional. This term should be replaced by an integer that indicates the
platform for which a report will be generated. If the mediatypeid parameter is not
specified, then report data for all platforms will be returned. Valid values for this term
are:
2: Flash Media Streaming
3: HTTP Large
7: HTTP Large (SSL Traffic Only)
8: HTTP Small
9: HTTP Small (SSL Traffic Only)
14: Application Delivery Network (ADN)
15: Application Delivery Network (ADN) – (SSL Traffic Only)
• POPs: Optional. You can choose to limit report data to one or more POPs.
All POPs: If you would like to generate report data for all POPs, then you should
not include "&pops=POPs " parameter in the request.
POP-Specific Report: Replace the term POPs with a comma-delimited list of the
desired POPs (e.g., oxr,dca,mia). Each POP's code is reported by the Code
response element in the Get All Edge Nodes endpoint.
• RegionID: Optional. You can choose to limit report data by region. Use the Get Billing
Regions endpoint to retrieve a listing of regions and their IDs. If the regionid parameter
is not specified, then report data for all regions will be returned.
Important: Specifying a time that falls in between the time interval specified for this endpoint
(e.g., 00:04:59) will retrieve all data associated with that time interval (e.g., 00:00:00 –
00:04:59).
Important: The pops and regionid parameters are mutually exclusive. Specifying both
parameters will result in an error.
Note: The time portion (i.e., hh:mm:ss) of the StartDateTime and EndDateTime request
parameters is optional. If a specific time is not specified, then a default time (i.e., 00:00:00) will
be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements.
Name Description
AN A string that identifies a customer by its system-defined account
number.
MediaTypeId An integer that identifies the platform for which statistics are being
reported. Valid values for this parameter are:
• 2: Flash Media Streaming
• 3: HTTP Large
• 7: HTTP Large (SSL Traffic Only)
• 8: HTTP Small
• 9: HTTP Small (SSL Traffic Only)
• 14: Application Delivery Network (ADN)
• 15: Application Delivery Network (ADN) – (SSL Traffic Only)
DataTransferred Encapsulates the report data returned for a specific platform and
time interval.
Note: In JSON, this response element is indicated as "{ … }."
Note: This response element is repeated until the entire time period
indicated in the request URI has been covered.
DateTimeSlice A string that identifies a time slice by its start date and time. This
response element indicates this start date and time using the
following format: YYYY-MM-DD hh:mm.
Bytes An integer that indicates the number of bytes that were transferred
during a specific time slice for the specified platform. This value only
includes traffic that met the criteria specified in the GET request.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/bytestransferred/interval?begin
date=2012-10-01&enddate=2012-10-01T05:00:00&mediatypeid=3&intervalid=2 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 512
[{
"AN" : "0001",
"MediaTypeId" : 3,
"Data" : [{
"DateTimeSlice" : "2012-10-01 00:00",
"Bytes" : 516514354
}, {
"DateTimeSlice" : "2012-10-01 01:00",
"Bytes" : 465465452
}, {
"DateTimeSlice" : "2012-10-01 02:00",
"Bytes" : 688465452
}, {
"DateTimeSlice" : "2012-10-01 03:00",
"Bytes" : 789456321
}, {
"DateTimeSlice" : "2012-10-01 04:00",
"Bytes" : 623845975
}, {
"DateTimeSlice" : "2012-10-01 05:00",
"Bytes" : 689746521
}
]
}
]
Retrieves the hit statistics for each status code returned for content delivered over our CDN. The
data returned by this report can be filtered to only include CDN traffic that meets the following
criteria:
• Platform
• Date range
Request
A request to retrieve hit statistics is described below. When submitting this request, you will
need to define the following terms:
• Platform: This term should be replaced by an integer that indicates the platform for
which a report will be generated. Valid values for this term are:
0: All Platforms
2: Flash Media Streaming
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that completed after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that completed after the specified date/time will be excluded from the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
Important: Specifying a time that falls in between a one hour time interval (e.g., 00:00:01) will
retrieve all data associated with that time interval (e.g., 00:00:00 – 00:59:59).
Note: The time portion (i.e., hh:mm:ss) of the StartDateTime and EndDateTime request
parameters is optional. If a specific time is not specified, then a default time (i.e., 00:00:00) will
be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
status code.
Name Description
Description A string that identifies a status code by its description (e.g., OK,
Forbidden, Not Found, etc.)
HitPercentage A number (floating-point) that indicates the percentage of requests
that resulted in the specified status code over the given time period
& platform.
Hits An integer that indicates the number of requests that resulted in the
specified status code over the given time period & platform.
StatusCode An integer that identifies a status code (200, 403, 404, etc.).
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/hits?begindate=2013-06-
01&enddate=2013-07-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 487
[{
"Description" : "",
"HitPercentage" : 57.96,
"Hits" : 638045,
"StatusCode" : 200
}, {
"Description" : "",
"HitPercentage" : 41.36,
"Hits" : 455247,
"StatusCode" : 304
}, {
"Description" : "",
"HitPercentage" : 0.43,
"Hits" : 4698,
"StatusCode" : 206
}, {
"Description" : "",
"HitPercentage" : 0.25,
"Hits" : 2799,
"StatusCode" : 404
}, {
"Description" : "",
Returns the maximum amount of storage space used on a CDN origin server during the given
time period.
Request
A request to retrieve maximum storage space usage is described below. When submitting this
request, you will need to define the following terms:
• StartDateTime: This term should be replaced by the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report. The
format for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date/time for the report.
Activity that took place after the specified date/time will not be included in the report.
The format for this term is: YYYY-MM-DDThh:mm:ss.
Note: Keep in mind that time is optional. If time is not specified, then a default time (i.e.,
00:00:00) will be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
UsageResult A number (floating-point) that indicates the highest level of disk space
usage (GB) over the given time period.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/maxstorageusage?begindate=2011-
06-01&enddate=2011-07-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 20
Retrieves the total number of DNS queries over a given time period for either of the following:
Request
A request to retrieve DNS query summary information is described below. When submitting this
request, you will need to define the following terms:
• ZoneName: Replace this variable with the name of the desired zone.
• StartDateTime: Replace this variable with the start date/time for the report. Only
activity that took place after the specified date/time will be included in the report.
Format: YYYY-MM-DDThh:mm:ss
• EndDateTime: Replace this variable with the end date/time for the report. Activity that
took place after the specified date/time will not be included in the report.
Format: YYYY-MM-DDThh:mm:ss
Note: Time (i.e., Thh:mm:ss) is optional. If time is not specified, then a default time (i.e.,
00:00:00) will be used.
Tip: Omit the zoneid and zonename query string parameters to retrieve statistics for all primary
and secondary zones.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/routesummary?begindate=2016-03-
15&enddate=2016-03-17 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 161
[{
"Zone" : "mydomain.net.",
"Id" : 4528,
"QueryCount" : "1234"
}, {
"Zone" : "myexample.com.",
"Id" : 4566,
"QueryCount" : "1235"
}
]
Provides traffic usage statistics corresponding to the combination of a particular platform and
billing region. The type of billing information returned by this endpoint, which can either be
Data Transferred or Bandwidth Usage, is determined by the Units request parameter. Please
choose the billing method that corresponds to the one specified in your contract.
Note: For the purposes of billing, report data is closed on the 3rd of the month. This means that
report data for the current month is incomplete until after the third of the next month.
Bandwidth Usage
Bandwidth usage information for the specified platform and billing region over the specified
month can be viewed by setting the Units request parameter to 1. This setting will cause this
endpoint to report the amount of data (Megabits) transferred per second during peak usage.
This information is useful for viewing whether 95% usage of the bandwidth specified in your
contract has been exceeded.
Data Transferred
The total amount of data transferred (GB) for the specified platform and billing region over the
specified month can be viewed by setting the Units request parameter to 2.
Request
A request to retrieve billing statistics is described below. When submitting this request, you will
need to define the following terms:
• Platform: This term should be replaced by an integer that indicates the platform for
which a report will be generated. Valid values for this term are:
2: Flash Media Streaming
3: HTTP Large
7: HTTP Large (SSL Traffic Only)
8: HTTP Small
9: HTTP Small (SSL Traffic Only)
14: Application Delivery Network (ADN)
15: Application Delivery Network (ADN) – (SSL Traffic Only)
• Region: This term should be replaced by an integer that indicates the billing region for
which a report will be generated. Valid values for this term are defined by the Id return
value of the Get Billing Regions endpoint.
• BillingMonth: This term indicates the month for which billing information will be
returned. When specifying this option, you must specify the 1st of the desired month
(e.g., 2011-06-01). The format for this term is: YYYY-MM-DD.
Important: If you specify a date other than the 1st of the month, then the return value will not
reflect the usage information for that month.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/region/0/units/1/traffi
cusage?begindate=2011-06-01 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 21
{
"UsageResult" : 85.5
}
Name Description
Get Edge CNAME Report - Data Transferred Retrieves total data transferred or total hits
or Hits statistics for all custom report codes.
Get Data Transferred and Hits by Custom Retrieves CDN activity statistics for each
Report Codes custom report code.
Get Group Codes Retrieves a list of the available group codes.
Get Metric Codes Retrieves a list of the available metric codes.
Get Report Codes Retrieves a list of custom report codes.
Note: These endpoints may only generate reports for CDN activity within the last 18 months.
This endpoint retrieves total data transferred or total hits statistics for each edge CNAME for
which custom reports has been activated. Additionally, these statistics will be broken down by
either cache status code or HTTP status code.
Request
A request to retrieve a custom report is described below. When submitting this request, you will
need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
2: Flash Media Streaming
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
• StartDate: This term should be replaced by the start date for the report. Only activity
that took place after the specified date will be included in the report. The format for this
term is: YYYY-MM-DD.
• EndDate: This term should be replaced by the end date for the report. Activity that took
place after the specified date will not be included in the report. The format for this term
is: YYYY-MM-DD.
• MetricCode: Replace this variable with the metric code that identifies the type of report
to generate. By default, a "hits" report will be generated. Use the Get Metric Codes
endpoint to retrieve a list of metric codes.
• GroupCode: Replace this variable with the group code that identifies the type of
statistics that will be included in the report. By default, report statistics will be broken
down by HTTP status codes. Use the Get Group Codes endpoint to retrieve a list of
group codes.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Name Description
MetricCode A string that identifies the type of report that was generated by
its metric code.
Description A string that describes the type of report that was generated.
Data An array that describes the report.
GroupCode A string that identifies the type of statistics included in the report
by its metric code.
Description A string that describes the type of statistics included in the
report.
Data An array that contains report data.
Description A string that describes the report code (e.g., edge CNAME) for
which report data is reported.
TotalCount A string that indicates either of the following:
• Total Hits
• Total Data Transferred in Megabytes
The value reported in this response element is determined by the
metric code reported by the MetricCode response element.
Count A string that indicates either of the following for the type of
statistic defined by the KeyCode response element:
• Hits
• Data Transferred in Megabytes
The value reported in this response element is determined by the
metric code reported by the MetricCode response element.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/customreport?begindate=
2015-07-01&enddate=2015-07-29 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1808
[{
"MetricCode" : "Hits",
Retrieves the number of hits and the total amount of data transferred for each custom report
code.
Note: A unique custom report code is associated with each edge CNAME for which the custom
report capability has been enabled.
Request
A request to retrieve CDN activity for each custom report code is described below. When
submitting this request, you will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
2: Flash Media Streaming
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
• StartDateTime: This term should be replaced by the start date for the report. Only
activity that took place after the specified date will be included in the report. The format
for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date for the report. Activity that
took place after the specified date will not be included in the report. The format for this
term is: YYYY-MM-DDThh:mm:ss.
Important: Returns data in 1 hour intervals (e.g., 00:00:00, 01:00:00, 02:00:00, etc.). Specifying a
time that falls in between a 1 hour interval (e.g., 00:50:05) will include all data associated with
that hour (e.g., 00:00:00 – 00:59:59).
Note: The time portion (i.e., hh:mm:ss) of the StartDateTime and EndDateTime request
parameters is optional. If a specific time is not specified, then a default time (i.e., 00:00:00) will
be used.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
report code returned by this endpoint:
Name Description
Bytes An integer that indicates the total amount of data transferred (in
bytes) for the specified report code.
Keep in mind that this data is filtered by time period and platform.
Description A string that provides a description for a report code. The provided
information varies according to report code type.
For example, if an edge CNAME has been associated with a report
code, then this response element will report the name of that edge
CNAME.
Hits An integer that indicates the total number of hits that occurred for
the specified report code.
Keep in mind that this data is filtered by time period and platform.
ReportCode An integer that identifies a report code by its system-defined ID.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/cnamereportcodes?begind
ate=2012-11-01&enddate=2012-11-15 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 248
[{
"Bytes" : 55515129610593,
"Description" : "www.edgecname1.com",
"Hits" : 21873348,
"ReportCode" : 10042
}, {
"Bytes" : 45792193956438,
"Description" : "www.edgecname2.com",
"Hits" : 34243537,
"ReportCode" : 10044
}
]
This endpoint retrieves a list of the available group codes. Group codes define the type of
statistics that will be returned by the Get Edge CNAME Report - Data Transferred or Hits
endpoint.
Request
A request to retrieve group codes is described below.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
group code returned by this endpoint.
Name Description
GroupCode A string that identifies a type of statistic by its group code.
Use this code when generating a report via the Get Edge CNAME
Report - Data Transferred or Hits endpoint.
Description A string that provides a description for the current group code.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 151
[{
"GroupCode" : "HTTP_STATUS",
"Description" : "HTTP Response Codes"
}, {
"GroupCode" : "LOG_TCP",
"Description" : "Cache Status"
}
]
This endpoint retrieves a list of the available metric codes. Metric codes define the type of
report that will be returned by the Get Edge CNAME Report - Data Transferred or Hits endpoint.
Request
A request to retrieve metric codes is described below.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
metric code returned by this endpoint.
Name Description
MetricCode A string that identifies a type of report by its metric code. Use this
code when generating a report via the Get Edge CNAME Report -
Data Transferred or Hits endpoint.
Description A string that provides a description for the current metric code.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 130
[{
"MetricCode" : "Hits",
"Description" : "Hits"
}, {
"MetricCode" : "DT",
"Description" : "Data Transferred"
}
]
Request
Two variations of this request are provided below. The first request retrieves a listing of all
report codes, while the second request only retrieves report codes associated with the specified
platform. When submitting this request, you will need to define the following terms:
• Platform: Optional. This term should be replaced by an integer that indicates the
platform for which a report will be generated. If the mediatypeid parameter is not
specified, then report data for all platforms will be returned. Valid values for this term
are:
2: Flash Media Streaming
3: HTTP Large
7: HTTP Large (SSL Traffic Only)
8: HTTP Small
9: HTTP Small (SSL Traffic Only)
14: Application Delivery Network (ADN)
15: Application Delivery Network (ADN) – (SSL Traffic Only)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
report code returned by this endpoint.
Name Description
Description A string that describes a report code.
Note: If the report code is for an edge CNAME, then this response
element will identify the corresponding domain.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 195
[{
"Description" : "secure.mydomain.com",
"MediaTypeid" : 3,
"ReportCode" : 10000
}, {
"Description" : "marketing.mydomain.com",
"MediaTypeid" : 3,
"ReportCode" : 10001
}
]
The reporting service contains the Get Current Edge CNAME Statistics endpoint that reports the
most recent statistics on a per edge CNAME basis.
• Platform-specific traffic for each edge CNAME that meets the following requirements:
The edge CNAME's Custom Reports option is set to "Enabled."
Traffic is being served through the edge CNAME.
Note: The response for this endpoint may be filtered to only return statistics for a single edge
CNAME.
Should I use Get Current Edge CNAME Statistics or Get Current Edge CNAME Statistics II?
The main difference in functionality between these two endpoints is that the Get Current Edge
CNAME Statistics II endpoint returns the timestamp at which real-time statistics were retrieved.
Note: Another difference between these two endpoints is the manner in which the response is
organized. However, this difference does not affect the provided feature set.
Request
A request to retrieve real-time statistics broken down by edge CNAME is described below. When
submitting this request, you will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
cache: HTTP Large
wac: HTTP Small
adn: Application Delivery Network
Note: Including the cname query string parameter when requesting this endpoint will
filter the response to only display statistics for the specified edge CNAME.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains response elements that report statistics for:
Note: POP locations that are not serving traffic for the relevant edge CNAMEs will be omitted
from the response.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/rts/cache?cname=cdn.mydomain.co
m HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 20123
• Platform-specific traffic for each edge CNAME that meets the following requirements:
The edge CNAME's Custom Reports option is set to "Enabled."
Traffic is being served through the edge CNAME.
Note: The response for this endpoint may be filtered to only return statistics for a single edge
CNAME.
Should I use Get Current Edge CNAME Statistics or Get Current Edge CNAME Statistics II?
The main difference in functionality between these two endpoints is that the Get Current Edge
CNAME Statistics II endpoint returns the timestamp at which real-time statistics were retrieved.
Note: Another difference between these two endpoints is the manner in which the response is
organized. However, this difference does not affect the provided feature set.
Request
A request to retrieve real-time statistics broken down by edge CNAME is described below. When
submitting this request, you will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
cache: HTTP Large
wac: HTTP Small
adn: Application Delivery Network
Note: Including the cname query string parameter when requesting this endpoint will
filter the response to only display statistics for the specified edge CNAME.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains response elements that report statistics for:
Note: POP locations that are not serving traffic for the relevant edge CNAMEs will be omitted
from the response.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/realtimestats/cache?cdn.mydomai
n.com HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 19180
Reports the following real-time statistics for traffic delivered over the specified platform:
Note: As indicated above, real-time statistics may be reported on a per edge CNAME basis. This
type of data is only reported for edge CNAME configurations where the Custom Reports option
has been enabled.
Request
A request to retrieve real-time statistics is described below. When submitting this request, you
will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
cache: HTTP Large
wac: HTTP Small
adn: Application Delivery Network
• EdgeCNAME: Replace this variable with the case-sensitive name of the desired edge
CNAME.
• CountryCode: Replace this variable with the ISO 3166 code corresponding to the
country for which real-time statistics will be returned.
Tip: A list of country codes is available from the Country Codes (ISO 3166) article in the
CDN Help Center.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request that does not filter data contains response
parameters that report statistics for:
Note: Countries or edge CNAMEs through which traffic is not being served will be omitted from
the response.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/countryrealtimestats/and?cname=
cdn.example.com&country=us om HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 942
{
"Timestamp": "01\/18\/2018 22:00:29",
"Countries": [{
"CountryCode": "US",
"Country": "United States",
"RTStats": [{
"ReportCode": "10012",
"CName": "cdn.example.com",
"BW": 57137424356.900772,
"CONN": 6256.201794999999,
"HITS": 103441.41254399999,
"CacheStats": [{
"Key": "cache.hit",
Note: Advanced Content Analytics endpoints can only generate reports for CDN activity within
the last 90 days.
Retrieves statistics for the top 250 requested assets over a specific time period.
Request
A request to retrieve statistics for the top 250 requested assets is described below. When
submitting this request, you will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
2: Flash Media Streaming
3: HTTP Large
14: Application Delivery Network (ADN)
• StartDateTime: This term should be replaced by the start date for the report. Only
activity that took place after the specified date will be included in the report. The format
for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date for the report. Activity that
took place after the specified date will not be included in the report. The format for this
term is: YYYY-MM-DDThh:mm:ss.
Important: Returns data in 1 day intervals. This means that this report will return data for the
specified time period including the specified start and end date. This will occur regardless of
whether a time value was specified. This means that time is optional and irrelevant for this
endpoint.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
asset returned by this endpoint:
Name Description
DataTransferred An integer that indicates the total amount of data transferred
(in bytes) for the specified asset over the specified time period.
DataTransferredPercentage A number (floating-point) value that indicates the data
transferred percentage for the specified asset. Keep in mind
that this percentage is calculated from the total amount of data
transferred for all assets included in this report over the
specified time period.
Duration A number (floating-point) value that indicates the average
amount of time, in seconds, that it took our CDN to serve an
asset to a client.
Hits An integer that indicates the total number of hits for the
specified asset over the specified time period.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/filestats?begindate=201
1-06-01&enddate=2011-06-02 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 654
[{
"DataTransferred" : 29731911100,
"DataTransferredPercentage" : 43.7475,
"Duration": 0.5021,
"Hits" : 70286037,
"HitsPercent" : 81.1283,
"Path" : "\/000001\/2011\/main.html"
}, {
"DataTransferred" : 7161857970,
"DataTransferredPercentage" : 10.5428,
Retrieves statistics for the top 250 requested directories over a specific time period.
Request
A request to retrieve directory statistics is described below. When submitting this request, you
will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
2: Flash Media Streaming
3: HTTP Large
14: Application Delivery Network (ADN)
• StartDateTime: This term should be replaced by the start date for the report. Only
activity that took place after the specified date will be included in the report. The format
for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date for the report. Activity that
took place after the specified date will not be included in the report. The format for this
term is: YYYY-MM-DDThh:mm:ss.
Important: Returns data in 1 day intervals. This means that this report will return data for the
specified time period including the specified start and end date. This will occur regardless of
whether a time value was specified. This means that time is optional and irrelevant for this
endpoint.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
directory returned by this endpoint:
Name Description
DataTransferred An integer that indicates the total amount of data transferred (in
bytes) for the specified directory over the specified time period.
DataTransferredPercent A number (floating-point) value that indicates the data transferred
percentage for the specified directory. Keep in mind that this
percentage is calculated from the total amount of data transferred
for all directories included in this report over the specified period
of time.
Duration A number (floating-point) value that indicates the average amount
of time, in seconds, that it took our CDN to serve an asset to a
client.
FullDirectoryPath A string that identifies the relative path to the directory for which
statistical information is returned. This path starts directly after the
hostname.
Hits An integer that indicates the total number of hits for the specified
directory over the specified time period.
HitsPercent A number (floating-point) value that indicates the hits percentage
for the specified directory. Keep in mind that this percentage is
calculated from the total hits for all directories included in this
report over the specified time period.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/directorystats?begindat
e=2011-06-01&enddate=2011-06-02 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 534
[{
"DataTransferred" : 66872640800,
"DataTransferredPercent" : 98.381,
"Duration" : 0.5012,
"FullDirectoryPath" : "\/000001\/HTML\/",
"Hits" : 86471638,
"HitsPercent" : 99.8107
}, {
"DataTransferred" : 955630223,
"DataTransferredPercent" : 1.4,
"Duration" : 0.5232,
"FullDirectoryPath" : "\/000001\/HTML\/Resources\/",
"Hits" : 83859,
"HitsPercent" : 0.0968
}, {
"DataTransferred" : 21474837,
"DataTransferredPercent" : 0.032,
"Duration" : 0.5235,
"FullDirectoryPath" : "\/000001\/HTML\/",
"Hits" : 53059,
"HitsPercent" : 0.0612
}
Retrieves download statistics for the top 250 downloaded assets over a specific time period.
Please keep in mind the following information when generating this report:
• This report only provides information for assets larger than 50 KB.
• Reports generated for accounts on which compression has been enabled may be
inaccurate, since the logged file size may be larger than the total bytes transferred.
• This report may not accurately represent streaming video downloads, since users may
seek to different parts of the video.
Request
A request to retrieve download statistics is described below. When submitting this request, you
will need to define the following terms:
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
2: Flash Media Streaming
3: HTTP Large
14: Application Delivery Network (ADN)
• StartDateTime: This term should be replaced by the start date for the report. Only
activity that took place after the specified date will be included in the report. The format
for this term is: YYYY-MM-DDThh:mm:ss.
• EndDateTime: This term should be replaced by the end date for the report. Activity that
took place after the specified date will not be included in the report. The format for this
term is: YYYY-MM-DDThh:mm:ss.
Important: Returns data in 1 day intervals. This means that this report will return data for the
specified time period including the specified start and end date. This will occur regardless of
whether a time value was specified. This means that time is optional and irrelevant for this
endpoint.
Note: For more information on date/time format, please refer to Appendix B: Report
Date/Time Format.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements for each
asset returned by this endpoint:
Name Description
CompleteDownloadPercent A number (floating-point) that indicates the percentage that
the entire asset was downloaded. A decimal value is not
reported for whole numbers (e.g., 100).
CompleteDownloads An integer that indicates the total number of times that the
entire asset was downloaded.
DownloadAttempts An integer that indicates the total number of attempts to
download the specified asset.
File A string that indicates the relative path to an asset. This path
starts directly after the hostname.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET
https://api.edgecast.com/v2/reporting/customers/0001/media/3/completedownloads?begin
date=2011-06-01&enddate=2011-06-02 HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 534
[{
"CompleteDownloadPercent" : 81.33,
"CompleteDownloads" : 4952436300,
"DownloadAttempts" : 4952436298,
"File" : "\/000001\/2011\/Main.html"
}, {
"CompleteDownloadPercent" : 18.33,
"CompleteDownloads" : 1116424040,
"DownloadAttempts" : 1116424040,
"File" : "\/000001\/Resources\/Video01.flv"
}, {
"CompleteDownloadPercent" : 0.16,
"CompleteDownloads" : 9525486,
"DownloadAttempts" : 9525474,
"File" : "\/000001\/Resources\/Border.gif"
}
]
Request
A request to define a log delivery profile is described below. When submitting this request, you
will need to define the following term:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Pass the following request body parameters:
Name Data Description
Type
profile_name String Assigns a unique name to the log delivery
profile. The maximum length for this property is
36 characters.
description String Determines the log delivery profile's
description. The maximum length for this
property is 100 characters.
log_format String Determines the format for log data. Valid values
are:
json | json_array | json_lines
Note: This property may only be defined when
delivery_method is set to http_post, aws_s3, or
azure_blob_storage.
Example:
"status_codes": ["2xx", "3xx"],
cnames Array Specify a string value for each edge CNAME for
which log data will be delivered. Omit this
parameter or define an empty array if log data
should not be filtered by edge CNAMEs.
Tip: Retrieve edge CNAMEs via the Name
response parameter from the Get All Edge
CNAMEs - ADN, Get All Edge CNAMEs - HTTP
Large, and/or Get All Edge CNAMEs - HTTP
Small endpoints.
Example:
"cnames": ["cdn1.example.com",
"cdn2.example.com"],
http_post Object
Note: Required when delivery_method is set to
http_post.
aws_s3 Object
Note: Required when delivery_method is set to
aws_s3.
splunk_enterprise Object
Note: Required when delivery_method is set to
splunk_enterprise.
access_key String
Note: Required when access_type is set to
access_key.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"delivery_method": "http_post",
"fields": ["user_agent", "rewritten_path", "path", "timestamp", "client_ip",
"client_ip_version", "status_code", "status", "cache_status", "bytes_out",
"write_time", "file_size", "server_ip", "server_port", "method", "host",
"query", "auth_user", "read_time"],
"platforms": [
"adn"
],
"http_post": {
"destination_endpoint": "https://logs.example.com/cdn/",
"authentication_type": "none",
"token": null,
"username": null,
"password": null
}
}
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 900
{
"@id": "/v2/mcc/customers/0001/rtld/settings",
"@type": "RtldSetting",
"id": 20,
"account_number": "0001",
"delivery_method": "http_post",
"enabled": false,
"downsampling_rate": null,
"fields": ["user_agent", "rewritten_path", "path", "timestamp", "client_ip",
"client_ip_version", "status_code", "status", "cache_status", "bytes_out",
"write_time", "file_size", "server_ip", "server_port", "method", "host",
"query", "auth_user", "read_time"],
"platforms": [
"adn"
],
"filters": {
"status_codes": null,
"cnames": null
},
"aws_s3": null,
"http_post": {
"destination_endpoint": "https://logs.example.com/cdn/",
"authentication_type": "none",
"token": null,
"username": null,
"password": null
},
"sumo_logic": null,
"splunk_enterprise": null,
"azure_blob_storage": null
}
Request
A request to retrieve your log delivery profiles is described below. When submitting this
request, you will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1013
{
"@id": "/v2/mcc/customers/0001/rtld/settings",
"@type": "Collection",
"items": [{
"@id": "/v2/mcc/customers/0001/rtld/settings/20",
"@type": "RtldSetting",
...
"http_post": {
"destination_endpoint":
"https://logs.example.com/cdn/",
"authentication_type": "none",
"token": null,
"username": null,
"password": null
},
}
],
"total_items": 1
}
Request
Retrieve AWS regions via the following request:
HTTP Method Request URI
GET https://api.edgecast.com/v2/mcc/rtld/aws-regions
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1060
{
"@id": "/v2/mcc/rtld/aws-regions",
"@type": "Collection",
"items": [{
"code": "ap-south-1",
"name": "Asia Pacific (Mumbai)"
}, {
...
}, {
"code": "us-west-2",
"name": "US West (Oregon)"
}
],
"total_items": 14
}
Request
Retrieve access types via the following request:
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 224
{
"@id": "/v2/mcc/rtld/azure-access-types",
"@type": "Collection",
"items": [{
"code": "sas_token",
"name": "SAS Token"
}, {
"code": "access_key",
"name": "Access Key"
}
],
"total_items": 2
}
Retrieves the available authentication methods when delivering log data via HTTP POST.
Request
Retrieve authentication methods via the following request:
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 304
Retrieves the available HTTP status codes for filtering log data.
Request
Retrieve HTTP status codes via the following request:
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 282
Request
Retrieve delivery methods via the following request:
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 421
Retrieves the available rates for downsampling the set of log data delivered to your destination.
Request
Retrieve downsampling rates via the following request:
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 115
{
"@id": "/v2/mcc/rtld/downsampling-rates",
"@type": "Collection",
"items": [0.1, 1.0],
"total_items": 2
}
Request
Retrieve log fields via the following request:
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1444
{
"@id": "/v2/mcc/rtld/fields",
"@type": "Collection",
"items": [{
"code": "user_agent",
"name": "User Agent"
}, {
...
}, {
"code": "referer",
"name": "Referrer"
}
],
"total_items": 22
}
Request
A request to retrieve your RTLD profile is described below. When submitting this request, you
will need to define the following variable:
• AccountNumber: Replace this variable with your CDN account number. This number can
be found in the upper-right hand corner of the MCC.
• SettingsID: Replace this variable with the system-defined ID assigned to your RTLD
profile.
Tip: Reference the items[0].id parameter from the Get All RTLD Profiles endpoint to find
out the ID assigned to your RTLD profile.
Request Headers
The response for this endpoint only includes standard HTTP request headers including those
described in the Request Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 835
Request
A request to update a RTLD profile is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• SettingsID: Replace this variable with the system-defined ID assigned to your RTLD
profile.
Tip: Reference the items[0].id parameter from the Get All RTLD Profiles endpoint to find
out the ID assigned to your RTLD profile.
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Pass the following request body parameters:
Example:
"status_codes": ["2xx", "3xx"],
cnames Array Specify a string value for each edge CNAME for
which log data will be delivered. Omit this
parameter or define an empty array if log data
should not be filtered by edge CNAMEs.
Tip: Retrieve edge CNAMEs via the Name
response parameter from the Get All Edge
CNAMEs - ADN, Get All Edge CNAMEs - HTTP
Large, and/or Get All Edge CNAMEs - HTTP Small
endpoints.
Example:
"cnames": ["cdn1.example.com",
"cdn2.example.com"],
http_post Object
Note: Required when delivery_method is set to
http_post.
destination_endpoint String
Note: Required when delivery_method is set to
http_post.
splunk_enterprise Object
Note: Required when delivery_method is set to
splunk_enterprise.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response elements:
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
{
"@id": "/v2/mcc/customers/0001/rtld/settings/20",
"@type": "RtldSetting",
"delivery_method": "http_post",
"enabled": true,
"downsampling_rate": null,
"fields": ["user_agent", "rewritten_path", "path", "timestamp", "client_ip",
"client_ip_version", "status_code", "cache_status", "bytes_out",
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/xml; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 1013
{
"@id": "/v2/mcc/customers/0001/rtld/settings/20",
"@type": "RtldSetting",
…
"platforms": ["adn"],
"filters": {
"status_codes": null,
"cnames": null
},
"aws_s3": null,
Request
A request for the current amount of bandwidth usage is described below. When submitting this
request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/realtimestats/customers/0001/media/3/bandwidth
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 31
{
"Result" : 8059050.365432
}
Provides a breakdown of the cache statuses currently being returned for requests to your CDN
account.
Request
A request for cache status statistics is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
CacheStatus A string that indicates the name of the cache status for which
statistical information will be returned.
Connections An integer that indicates the total number of requests per second
that resulted in the specified cache status.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/realtimestats/customers/0001/media/3/cachestatus
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 492
[{
"CacheStatus" : "TCP_HIT",
"Connections" : 3550
}, {
"CacheStatus" : "TCP_EXPIRED_HIT",
"Connections" : 1525
}, {
"CacheStatus" : "TCP_MISS",
"Connections" : 125
}, {
"CacheStatus" : "TCP_EXPIRED_MISS",
"Connections" : 0
}, {
"CacheStatus" : "TCP_CLIENT_REFRESH_MISS",
"Connections" : 0
}, {
"CacheStatus" : "NONE",
"Connections" : 0
}, {
"CacheStatus" : "CONFIG_NOCACHE",
"Connections" : 0
}, {
"CacheStatus" : "UNCACHEABLE",
"Connections" : 0
}
]
Provides a breakdown of the HTTP status codes currently being returned for requests to your
CDN account.
Request
A request for status codes statistics is described below. When submitting this request, you will
need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• Platform: This term should be replaced by the ID associated with the desired platform.
Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Status Code
A status code indicates whether the request was successfully performed. A list of common
status codes is provided in the Status Codes and Error Messages topic.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Name Description
Connections An integer that indicates the total number of requests per second
that resulted in the specified status code.
StatusCode A string that indicates the type of status code for which statistical
information will be returned.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 407
[{
"Connections" : 5600,
"StatusCode" : "2xx"
}, {
"Connections" : 0,
"StatusCode" : "304"
}, {
"Connections" : 0,
"StatusCode" : "3xx"
}, {
"Connections" : 0,
"StatusCode" : "403"
}, {
"Connections" : 0,
"StatusCode" : "404"
}, {
"Connections" : 0,
"StatusCode" : "4xx"
}, {
"Connections" : 0,
"StatusCode" : "5xx"
}, {
"Connections" : 0,
"StatusCode" : "other"
}
]
Returns the total new connections per second on the specified platform. For the purposes of
this endpoint, a connection is initiated when a user agent (e.g., web browser) requests content
through the CDN. After which, the user agent determines whether future requests within that
session will reuse that connection or whether new connections will be established.
How is this statistic calculated?
This statistic is calculated using the following two steps:
1. The average number of new connections per second on each edge server is calculated.
2. This data is collected from all edge servers and then summed.
Request
A request to find out the total number of new connections per second is described below.
When submitting this request, you will need to define the following terms:
• AccountNumber: This term should be replaced by your CDN account number. This
number can be found in the upper-right hand corner of the MCC.
• Platform: This term should be replaced by the ID associated with the desired delivery
platform. Valid values for this parameter are listed below.
3: HTTP Large
8: HTTP Small
14: Application Delivery Network (ADN)
Request Headers
This endpoint only takes advantage of the common request headers described in the Request
Headers section of the Request and Response Elements topic.
Request Body
Request body parameters are not required by this endpoint.
Response
The response to the above request includes an HTTP status code, response headers, and a
response body.
Response Headers
The response for this endpoint only returns standard HTTP response headers including those
described in the Response Headers section of the Request and Response Elements topic.
Response Body
The response body for a successful request contains the following response element:
Name Description
Result A number (floating-point) that indicates the total number of new connections per
second on the specified platform.
Errors
The response body for an unsuccessful request may contain an error element that provides
additional information. For a list of common error messages, please refer to the Status Codes
and Error Messages topic.
GET https://api.edgecast.com/v2/realtimestats/customers/0001/media/3/connections
HTTP/1.1
Authorization: TOK:12345678-1234-1234-1234-1234567890ab
Accept: application/json
Host: api.edgecast.com
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/json; charset=utf-8
Date: Thu, 14 Apr 2016 12:00:00 GMT
Content-Length: 35
{
"Result" : 21099.000994
}
Purge Syntax
Please refer to the CDN Help Center for information on purge syntax.
• Date: YYYY-MM-DD
• Date/Time: YYYY-MM-DDThh:mm:ss
The above "Date" format can be used by any Reporting endpoint that requires that you specify a
start or end date. The above "Date/Time" format can only be used by reports that specifically
indicate that time can be specified.
Note: Time (i.e., Thh:mm:ss) is optional. If time is not specified, then a default time (i.e.,
00:00:00) will be used.
The variables used for the date and the date/time formats are described below.
• YYYY: Represents a year in the Gregorian calendar using a four digit number (e.g., 2011).
• T: Indicates a delimiter between date and time. This delimiter is only required if you
would like to specify a time. Keep in mind that time must be specified using 24-hour
clock notation in UTC/GMT.
• hh: Represents a two digit hour between 00 (midnight) and 23 (11 p.m.).
• mm: Represents the number of minutes into the specified hour. Minutes should be
specified using two digits between 00 and 59.
• ss: Represents the number of seconds into the specified minute. Seconds should be
specified using two digits between 00 and 59.
• The amount of time covered by a chunk varies for each type of report. This time interval
can either be 5 minutes, 1 hour, 1 day, or 1 month.
• A report's time chunk should not be confused with the date/time range used to
generate the report. Please refer to the documentation provided for the desired
endpoint to find out the time chunk that it uses to report data.
• A start or end date/time cannot be specified for monthly reports (e.g., Get Traffic
Usage). The data returned for this type of endpoint will always be limited to the
specified month (e.g., 08-01-2012 00:00:00 – 08-31-2012 23:59:59 GMT).
It is important to know the following information when generating a report:
Legacy Endpoints
Please refer to the REST API Help Center for information on legacy endpoints.
POP Listing
A list of POPs, their corresponding abbreviation, and the region that they serve is available from
the CDN Help Center:
• POP Listing