API keys are unique to your organization. An API key is required by the Datadog Agent to submit metrics and events to Datadog.
Application keys, in conjunction with your organization’s API key, give users access to Datadog’s programmatic API. Application keys are associated with the user account that created them and by default have the permissions and scopes of the user who created them.
To better protect and secure your applications, you can specify authorization scopes for your application keys to define more granular permissions and minimize the access that applications have to your Datadog data. This gives you fine-grained access control over your applications and minimizes security vulnerabilities by limiting extraneous access. For example, an application that only reads dashboards does not need admin rights to manage users or delete any of your organization’s data.
The recommended best practice for scoping application keys is to grant your keys the minimal privileges and least permissions necessary for an application to function as intended. Scoped application keys are granted only the scopes specified by the user, and no other additional permissions. While you can modify the authorization scopes of your application keys anytime, consider how those changes may impact the existing functionality or access of your application.
- Users or service accounts with permissions to create or edit application keys can scope application keys. A user must have the
user_app_keys permission to scope their own application keys, or the
org_app_keys_write permission to scope application keys owned by any user in their organization. A user must have the
service_account_write permission to scope application keys for service accounts.
- Application owners cannot authorize an application if they are missing any required permissions, even if they scope an application key with authorization scopes that they do not have.
- Errors due to missing permissions when writing application keys or authorizing applications will display a
403 Forbidden error. More information about various error responses can be found in the Datadog API documentation.
- If a user’s role or permissions change, authorization scopes specified for their application keys remain unchanged.
For security reasons, API keys cannot be used to send data from a browser, mobile, or TV app, as they would be exposed client-side. Instead, end user facing applications use client tokens to send data to Datadog.
Several types of clients submit data that requires a client token, including the following examples:
Client tokens are unique to your organization. To manage your client tokens, go to Organization Settings, then click the Client Tokens tab.
Note: When a user who created a client token is deactivated, the client token remains active.
Add an API key or client token
To add a Datadog API key or client token:
- Navigate to Organization settings, then click the API keys or Client Tokens tab.
- Click the New Key or New Client Token button, depending on which you’re creating.
- Enter a name for your key or token.
- Click Create API key or Create Client Token.
- Your org must have at least one API key and at most 50 API keys.
- Key names must be unique across your organization.
Remove API keys or client tokens
To remove a Datadog API key or client token, navigate to the list of keys or tokens, and click the trash can icon with Revoke next to the key or token you want to remove.
Add application keys
To add a Datadog application key, navigate to Organization Settings > Application Keys. If you have the permission to create application keys, click New Key.
- Application key names cannot be blank.
Remove application keys
To remove a Datadog application key, navigate to Organization Settings > Application Keys. If you have the permission to create and manage application keys, you can see your own keys and click Revoke next to the key you want to revoke. If you have the permission to manage all org application keys, you can search for the key you want to revoke and click Revoke next to it.
Scope application keys
To specify authorization scopes for application keys, make a request to the Datadog API or the UI to create or edit an application key. Scopes can be specified for application keys owned by the current user or a service account. If this field is unspecified, application keys by default have all the same scopes and permissions as the user who created them.
- Scope names are case-sensitive.
Using multiple API keys
Consider setting up multiple API keys for your organization. For example, use different API keys for each of your various deployment methods: one for deploying an Agent on Kubernetes in AWS, one for deploying it on prem with Chef, one for Terraform scripts that automate your dashboards or monitors, and one for developers deploying locally.
Using multiple API keys lets you rotate keys as part of your security practice, or revoke a specific key if it’s inadvertently exposed or if you want to stop using the service it’s associated with.
If your organization needs more than the built-in limit of 50 API keys, contact Support to ask about increasing your limit.
Disabling a user account
If a user’s account is disabled, any application keys that the user created are revoked. Any API keys that were created by the disabled account are not deleted, and are still valid.
Due to security reasons, Datadog does not transfer application keys from one user to another. If you need to share an application key, use a service account.
What to do if an API or Application key was exposed
If a private key has been compromised or publicly exposed, steps should be taken as quickly as possible to ensure the security of your account. Removing the file containing the key from a public site such as GitHub does not guarantee it was not already accessed by another party.
Follow these steps to help safeguard your account:
Note: Revoking an active key may cause an impact to your services. If the scope of usage is large or undetermined, consider steps 2-5 before revoking the affected key.
- Revoke the affected key.
- Remove code containing the private key from any publicly accessible files:
- Publish the sanitized file to your public repository.
- Remove the sensitive data from your commit history.
- Create a new key.
- Update affected services with the new key.
- Review your account for any unapproved access:
- Users that have been recently added
- New resources
- Roles or permission changes
If any unusual activity is identified, or you need additional help securing your account, contact Datadog support.
Need help? Contact Datadog support.