Connect Datadog changedclaude-tag/admins/connections/datadog
Nearest release: v2.1.284, published 5 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 28 Sep 2026 22:53 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 23:07 UTC.
Upstream edited
Recorded here
Lines+12added
Lines−10removed
From line
20
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits6to this page, all time
The whole hunk
from line 20, old and new numbered
/
from line 20
2020
2121## Add the connection to a bundle
2222
23In the bundle, click **Connect** next to Datadog. The picker has three Datadog entries, one per site. Pick the one that matches your Datadog account's site.
23In the bundle, click **Connect** next to Datadog. The picker has one Datadog entry per Datadog site. Datadog has a separate API host per site, and a key only works against its own, so pick the entry that matches your Datadog account's site.
2424
25| Picker entry | Site |
25| Picker entry | Site and API host |
2626| :- | :- |
27| **Datadog** | US1 (`api.datadoghq.com`), the default site |
28| **Datadog (US5)** | US5 (`api.us5.datadoghq.com`) |
29| **Datadog (EU)** | EU (`api.datadoghq.eu`) |
27| **Datadog** | US1, `api.datadoghq.com`, Datadog's default site |
28| **Datadog (US3)** | US3, `api.us3.datadoghq.com` |
29| **Datadog (US5)** | US5, `api.us5.datadoghq.com` |
30| **Datadog (EU)** | EU, `api.datadoghq.eu` |
31| **Datadog (AP1)** | AP1, `api.ap1.datadoghq.com` |
32| **Datadog (AP2)** | AP2, `api.ap2.datadoghq.com` |
33| **Datadog (US1-FED)** | US1-FED, `api.ddog-gov.com` |
3034
31The form asks for the same fields in all three.
35The form asks for the same fields in every entry.
3236
3337| Field | Value |
3438| :- | :- |
3539| Claude's API key | The API key from Datadog |
3640| Claude's application key | The Application key from Datadog. Optional in the form; add it so Claude can read metrics, monitors, and dashboards |
37| Allowed websites | Prefilled by the preset; override for other sites (see below) |
41| Allowed websites | Prefilled with the entry's API host |
3842
39Datadog has a separate API host per site, and a key only works against its own. If your account is on a site without a picker entry, pick any Datadog entry and override the **Allowed websites** field with your site's API host: `api.us3.datadoghq.com`, `api.ap1.datadoghq.com`, or `api.ddog-gov.com`. To change the host later, open the **⋮** menu on this connection in the bundle's Credentials tab and choose **Edit**.
40
41If you override the **Allowed websites** field, replace the prefilled host with your site's API host rather than adding yours alongside it, so that **Test connection** checks your host instead of the prefilled one. You can save the connection even if the test fails, and the credential is sent only to the hosts in **Allowed websites**.
43The connection is created with path prefixes that cover Datadog's read and query routes: metric, log, trace, and RUM queries, monitors, downtimes, dashboards, SLOs, notebooks, events, hosts, service definitions, and incident search. It doesn't cover Datadog's key, user, integration, or log-configuration management routes, so Claude can't call those through it. To narrow the connection further, for example to `GET` only, or to allow another route, select **Edit** on the connection's row; see [Restrict by path or method](/docs/claude-tag/admins/add-connections#restrict-by-path-or-method).
4244
4345The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See [how Agent Proxy works](/docs/claude-tag/concepts/agent-identity#agent-proxy).
4446
No line in this hunk matches that.