Skip to content

(AAA) clarify limit of API keys #38261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
OliviaShoup wants to merge 5 commits into
base: master
Choose a base branch
from
Open

(AAA) clarify limit of API keys #38261

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f7b1121
Add note about API key limit
OliviaShoup Jul 16, 2026
ee98811
Fix capitalization
OliviaShoup Jul 16, 2026
a5ffcf6
Refine note about managed API keys
OliviaShoup Jul 16, 2026
dbf0708
Shorten two sentences lol
OliviaShoup Jul 16, 2026
56f03da
Clarify key limit + add note to increase limit
OliviaShoup Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/en/account_management/api-app-keys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ To add a Datadog API key or client token:

**Notes:**

- Your org must have at least one API key and at most 50 API keys.
- Your org must have at least one API key, and up to 50 API keys by default. If you need more, [contact Support][19] to request a higher limit. Managed API keys, marked with a {{< ui >}}Managed{{< /ui >}} label in the Name column, are created and controlled by a Datadog integration or service rather than by you, and don't count toward this limit. You can view that a managed API key exists and revoke it, but you can't see its value or edit its name.
- Key names must be unique across your organization.

## Remove API keys or client tokens
Expand All @@ -101,11 +101,11 @@ To add a Datadog application key, navigate to [**Organization Settings** > **App
{{< img src="account_management/app-key.png" alt="Navigate to the Application Keys page for your organization in Datadog" style="width:80%;" >}}

{{< site-region region="ap2,gov,gov2" >}}
<div class="alert alert-danger">Make sure to securely store your application key immediately after creation, as the key secret cannot be retrieved later.</div>
<div class="alert alert-danger">Make sure to securely store your application key immediately after creation. The key secret cannot be retrieved later.</div>
{{< /site-region >}}

{{< site-region region="us,us3,us5,eu,ap1" >}}
<div class="alert alert-info">If your organization has One-Time Read (OTR) mode enabled, make sure to securely store your application key immediately after creation, as the key secret cannot be retrieved later.</div>
<div class="alert alert-info">If your organization has One-Time Read (OTR) mode enabled, make sure to securely store your application key immediately after creation. The key secret cannot be retrieved later.</div>
{{< /site-region >}}

Because API keys and application keys are long-lived and have no built-in expiration, store them in a secrets manager, such as AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault, instead of in source code or environment files. AWS Secrets Manager supports [managed rotation for Datadog API keys and application keys][24].
Expand Down
Loading