Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from DD_API_KEY is sent as the DD-API-KEY header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Find your Datadog site: Check the URL you use to access Datadog (e.g. app.datadoghq.com → site datadoghq.com, app.datadoghq.eu → datadoghq.eu). Requests go to api.<site> using the DD_SITE environment variable, which defaults to datadoghq.com.
  2. Create an API key: In Organization Settings → API Keys (https://app.datadoghq.com/organization-settings/api-keys), create a key and add it to your .env as DD_API_KEY.
  3. Create an application key: In Organization Settings → Application Keys, create a key and add it as DD_APP_KEY. Application keys inherit the permissions of the user who created them; read access to monitors, dashboards, metrics, and logs is required.
  4. Verify access: Run the Validate API Key tool, then List Monitors.

​
Provider notes

  • Datadog authenticates with two headers: DD-API-KEY and DD-APPLICATION-KEY, so both env vars are required
  • If your org is not on datadoghq.com, set your site (e.g. datadoghq.eu) as the DD_SITE environment variable
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as datadog__validate_api_key with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.