API keys
These endpoints allow you to manage Content Delivery API (CDA) and Content Preview API (CPA) keys. These tokens provide read-only access to one or more environments. For each environment you want to access with a given token, you need to include a link to this environment in the environments property when creating or updating. Only the environments specified in this property can be accessed using this token and any CDA or CPA request using this token to access content from an environment not specified here will result in a 404 error. If the environments key is not specified, the token will have access to the master environment by default.
We recommend using different access tokens for different environments in your development process. For example, use one for your production environment and another for staging or continuous integration. This allows you to revoke them individually in the future and manage your delivery channels independently.
Delivery API keys collection
This endpoint allows you to create a Delivery API key and its corresponding Preview API key.
Delivery API key
This endpoint returns details about an existing Delivery API key.
This endpoint allows you to update a Delivery API key and its corresponding Preview API key.
X-Contentful-Version.This endpoint allows you to delete a Delivery API key and its corresponding Preview API key.
Preview API keys collection
Even though they are accessed through a different endpoint, Preview API keys are handled together with Delivery API keys. This means that when you create a CDA key, the corresponding CPA key will be created. A Delivery API key object will contain a link to its corresponding CPA key, which will need to be resolved calling the appropriate endpoint. Preview API keys also cannot be deleted, as they will be deleted along with their Delivery API keys.
Preview API key
This endpoint returns details about an existing Preview API key.