Getting Started

Our REST-compliant web services facilitate the integration of our CDN service into your workflow(s), applications, or interfaces.

Learn more about our CDN service (CDN Help Center).

Learn basic information about our services:

• Protocol: HTTPS

  Communication (i.e., request-response) with our web services is only permitted via HTTPS. This ensures the privacy and integrity of your data.

• Authentication/Authorization: Authorization Header

  Our REST API services require authentication and authorization before a request to one of our endpointIdentifies a request's connection point to our REST API service.s will be honored.

  Authenticate and authorize your requests by passing the Authorization header with the following value:

  • api.edgecast.com

    TOK: REST API Token

  • API Gateway (api.vdms.io)

    Bearer OAuth 2.0 Token

  Learn more.

• Request-Response (Accept and Content-Type): JSON

  We strongly recommend that the request body be formatted using JavaScript Object Notation (JSON). Inform our web servers that the expected format for the request-response will be JSON through the Accept and Content-Type request headers.

  Learn more.

• Programming Language: Agnostic

  Our REST API services are designed to be programming language-agnostic. Feel free to use your preferred programming language (e.g., C#, C, PHP, Perl, etc.).

• Services

  Our REST API consists of the following services:

  • mcc: This service contains endpoints that revolve around CDN configuration and actions (e.g., purge and load).
  • reporting: This service contains endpoints that provide historical and real-time statistics on CDN usage.
  • realtimestats: This service contains the majority of the endpoints that return real-time statistics on CDN usage.
  • rules-engine: This service, which leverages our API gateway, contains all Rules Engine endpoints with the exception of Get Deploy Request Status.
  • report-builder: This service, which leverages our API gateway, contains Report Builder endpoints.
  • rtld: This service, which leverages our API gateway, contains RTLD WAF and RTLD Rate Limiting endpoints.

  Requests to services that leverage our API gateway are authorized via OAuth 2.0.
  Learn more about authorization.

More Information

• Frequently Asked Questions

• View tutorials on how to use our REST API:

  • With curl.
  • With Fiddler.
  • To purge content.
  • To update a zone.
• Authentication and Authorization
• Request and Response - Structure and Elements
• Status Codes and Error Messages