diff --git a/content/en/glossary/terms/api_key.md b/content/en/glossary/terms/api_key.md
index 82b569bb3e7..1f5758d193d 100644
--- a/content/en/glossary/terms/api_key.md
+++ b/content/en/glossary/terms/api_key.md
@@ -2,4 +2,4 @@
id: api_key
title: API key
---
-An API key is a token used to authenticate a user or an application. The Datadog Agent requires an API key to submit metrics and events to Datadog.
\ No newline at end of file
+An API key is unique to your organization. The Datadog Agent requires an API key to submit metrics, traces, and logs to Datadog. API keys do not authenticate users or applications. To access the Datadog API programmatically, use an application key instead. For more information, see the API and Application Keys documentation.
\ No newline at end of file
diff --git a/content/en/glossary/terms/application_key.md b/content/en/glossary/terms/application_key.md
new file mode 100644
index 00000000000..10ab1390d50
--- /dev/null
+++ b/content/en/glossary/terms/application_key.md
@@ -0,0 +1,5 @@
+---
+id: application_key
+title: application key
+---
+An application key, along with your organization's API key, gives users access to the Datadog API. Application keys are associated with the user who created them and, by default, have that user's permissions. For more information, see the API and Application Keys documentation.
diff --git a/content/en/glossary/terms/client_token.md b/content/en/glossary/terms/client_token.md
new file mode 100644
index 00000000000..0ca73cadb69
--- /dev/null
+++ b/content/en/glossary/terms/client_token.md
@@ -0,0 +1,7 @@
+---
+id: client_token
+title: client token
+synonyms:
+ - RUM client token
+---
+A client token authenticates data sent to Datadog from a browser, mobile, or TV app, such as Real User Monitoring events or browser logs. Client tokens are used instead of API keys because API keys would be exposed client-side. For more information, see the API and Application Keys documentation.