Welcome! We are glad you value of the essential API building blocks as much as we do. We use them to support our self-service portal and are happy to support your autonomy to dream up use cases we may not have thought of. Here you will learn how to quickly onboard, discover, and consume CDN API endpoints. We are evolving our offers and think you will like the direction we are taking with our newest version 3.0 endpoints.
The authentication, authorization and API style is common across the full product set. Your API keys (credentials) can be used for one or all of our endpoints.
The API architecture is stateless and restful.
API requests are authorized by RFC 2104-compliant HMAC.
Getting and managing your API credentials (keys)
For existing customers who have access to the Media portal, your Media portal administrator (role = domain admin) can create and manage up to 5 API keys, or they can elevate your permission to do it yourself. There is no need to request credentials from Lumen. If you are not a Lumen customer, you’ll need to first activate your account.
API keys, like users, are tied to a specific scope. Below are the main components.
This is one part of the authorization header of API requests.
The scope of the key representing a collection of caching services it may operate on.
Determines the operations allowed. Each endpoint will specify if a specific role is required. In some cases write operations may be blocked a key is associated with a lower level role, such as reporting.
Versions, deprecation, and out of support
Our versions are apparent in th base URI and any considerations needed to use one or the other are noted in the specific content describing them. Whenever me make changes that could impact your code, we will create a new version in order not to disrupt your implementations.
Getting started with Media portal APIs
Follow these steps to prepare to use Media portal APIs:
Obtain your API credentials with the proper scope and permissions.
Decide which API(s) you wish to use and which identifiers are required in the base URI.