Get published content from environments with secure access enabled. If secure access is disabled, your content is publicly accessible without an API key.
Preview the latest content from environments. You always need an API key to preview content.
Delivery API keys are shared between all project managers.Check the Delivery API reference for more details about Delivery API keys.
Management API keys
Use Management API keys and Personal API keys to manage your project environments and their content via Management API. For example, perform content migrations or integrate with third-party services.Whenever you make a content change via API, the change is tied to the specific API key and can be seen in the version history and audit log.
With Management API keys, you’ll see the API key’s name.
With Personal API keys, you’ll see the API key’s owner name.
The user who can manage an API key can view the API key value, change the API key settings, and revoke the API key.
Delivery API keys are managed by project managers. Project managers can specify additional users who can view the API key value.
Management API keys are managed by project managers. Project managers can specify additional users who can view the API key value.
Personal API keys are managed by their owners. These can be project managers and users with the Create a personal API keypermission. Project managers can revoke other users’ personal API keys, but cannot see the API key value.
Create Delivery API keys
You can use multiple Delivery API keys in your projects. For example, you can have a Delivery API key for previewing content and another for getting published content.The benefit of using multiple Delivery API keys is having integration-specific and application-specific keys. You can mitigate the impact of API key expiration or rotation by using dedicated Delivery API keys.To create a Delivery API key:
In Project settings > API keys > Delivery API keys, click Create Delivery API key.
(Optional) In Expirationdate, choose when you want the API key to expire. By default, the API key expires in one year.
In Name, type the name of the API key.
(Optional) In Users with access to this API key, allow specific users to view and copy the API key. By default, all project managers can view the API key.
In Delivery API access, specify the access granted by the API key.
For retrieving published content from environments with secure access enabled, select Secure access.
For previewing the latest and unpublished content, select Content preview.
In Limitations, adjust the API key scope to specific environments.
Click Save changes.
In API key, click to copy the API key value.
Create Management API keys
You can use multiple Management API keys in your projects. For example, you can use one Management API key to integrate a translation management system, and another API key for content migrations.To create a Management API key:
In Project settings > API keys > Management API keys, click Create Management API key.
(Optional) In Expirationdate, choose when you want the API key to expire. By default, the API key expires in six months.
In Name, type a human-friendly name describing the API key’s purpose. For example, Translation management or Team notifications.
(Optional) In Users with access to this API key, allow specific users to view and copy the API key. By default, only project managers can view the API key.
In Limitations, adjust the API key scope to specific environments.
In Permissions, select at least one permission for the API key.
Get information about environments and their cloning status.
Mark environments as production.
Rename environments.
Create Personal API keys
Project managers and users with the Create a personal API keypermission can create their own Personal API keys to use Management API. Each eligible user can have only a single personal API key.To create a Personal API key.
In Project settings > API keys > Management API keys, click Create Personal API key.
(Optional) In Expirationdate, choose when you want the API key to expire. By default, the API key expires in six months.
Click Save changes.
In API key, click to copy the API key value.
Set API key expiration
The default and recommended API key expiration lengths differ for Delivery API and Management API.
For Management API keys, the default expiration length is six months. The expiration length can vary from 1 minute to 2 years.
For Delivery API keys, the default expiration length is one year. The expiration length can vary from 1 minute to 5 years.
You suspect unauthorized API key usage, for example, after a user leaves your company. In such cases, switch to a new API key in your apps and regenerate your existing API key.
Users are removed from your project’s environment or subscription. Depending on the user’s access level, you might want to regenerate the shared Delivery API keys.
You receive a notification about an upcoming expiration of your API key.
When you regenerate your API key, the API key is revoked after a few minutes, and you get a new API key immediately.
InProject settings > API keys.
On either the Delivery API keys or Management API keys tab, choose an API key to view its details.
In API key, click .
Revoke API keys
If you no longer need an API key, you can revoke it to prevent further access. For example, when you stop using an integration and don’t plan on replacing it or its associated API key.When you revoke an API key, the API key becomes invalid and is removed from the list of API keys. The revocation process can take up to a couple of minutes. Any requests made with a revoked API key result in the 401 Unauthorized error.
In Project settings > API keys.
On either the Delivery API keys or Management API keys tab, choose an API key to view its details.
Management API keys with a static set of customizable permissions. Use unique Management API keys when integrating with third-party services or for continuous usage in production.
Personal API keys with a dynamic set of inherited permissions. The API key has the same permissions as its owner. Use personal API keys in your personal projects for testing. Don’t share your personal API keys with anyone else.
If the expiration date is less than a day apart from the API key's creation date, the email notification is sent immediately.
If the expiration date is between 1–7 days apart form the API key's creation date, the email notification is sent 1 day before the expiration date.
If the expiration date is more than a week apart from the API key's creation date, the email notification is sent 1 week before the expiration date.