API Overview

CDN Connect API v1

CDN Connect's core structure is entirely API based and built by developers for developers, with the goal to make implementation as simple as possible. If you have any questions, feedback or ideas please feel free to contact us and we'll work with you to make sure it fits your needs.

All API access is over HTTPS, and accessed from the api.cdnconnect.com domain. The data response format can be either JSON or XML and include the same response structure.

The CDN Connect API uses the OAuth2 protocol for authentication and authorization. Not only can individual users create an API key to access their own data, but external applications can also hook into CDN Connect and access protected data when given approval by the CDN Connect app owner.

The API follows many of the best practices for a RESTful API. Requests to the API can be accessed directly, or you can use simple wrappers to get you connecting even faster.

CDN Connect Apps

A CDN Connect app is a CDN that falls under one host name. For example, demo.cdnconnect.com is an example of an app, and static.cdnconnect.com is another. Each app can have their own structure and files, and do not share any files.

However, an individual CDN Connect user can be an app user for multiple apps. Let's say you are working on three separate websites, each website can have its own CDN Connect app. And at the same time, each CDN Connect app can have multiple app users, each of whom can have different permissions. Read more about Team Collaboration and Management of Production Static Assets.

An API Key acts as an app user and has been given authorization to only one specific CDN Connect app. If you want to create a new app, you must use the webapp to do so, and after the app has been created you must create a new API Key for the newly created app.



Have questions or feedback? Contact us.