Datadog

Datadog Configuration API

The Configuration API from Datadog — 4 operation(s) for configuration.

GitHub OpenAPI

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

DELETE /api/v2/metrics/{metric_name}/tags Delete a metric's tag configuration · Datadog Delete a Tag Configuration #
Ask an LLM
“How do I remove the tag configuration from a metric?”
“What permission is needed to delete a metric's tag configuration?”
Tell an agent destructive · confirm first
Delete the tag configuration on metric {metric_name}.
Remove Metrics without Limits settings from {metric_name}.
GET /api/v2/metrics/{metric_name}/tags Get a metric's tag configuration · Datadog List Tag Configuration by Name #
Ask an LLM
“Which tag keys are queryable for a given metric?”
“Can I see the current Metrics without Limits configuration for one metric?”
Tell an agent
Show the tag configuration for metric {metric_name}.
List the queryable tag keys configured on {metric_name}.
PATCH /api/v2/metrics/{metric_name}/tags Update a metric's tag configuration · Datadog Update a Tag Configuration #
Ask an LLM
“Can I switch a metric's tag configuration to exclude tags instead of including them?”
“How do I change the custom aggregations on an existing count or gauge tag configuration?”
Tell an agent
Update the tag configuration of {metric_name} to {config}.
Change the existing queryable tags on metric {metric_name} with {config}.
POST /api/v2/metrics/{metric_name}/tags Create a tag configuration for a metric · Datadog Create a Tag Configuration #
Ask an LLM
“How do I limit which tags are queryable on a metric to cut custom metric costs?”
“Can I add percentile aggregations when configuring tags on a distribution metric?”
Tell an agent
Create a tag configuration on {metric_name} with {config}.
Define the queryable tags for metric {metric_name} as {config}.
POST /api/v2/monitor/policy Create a monitor configuration policy · Datadog Create a Monitor Configuration Policy #
Ask an LLM
“How do I require specific tags on every new monitor?”
“Can I enforce a tag policy for monitors across my organization?”
Tell an agent
Create a monitor configuration policy with {policy}.
Add a monitor tag policy defined as {policy}.
DELETE /api/v2/monitor/policy/{policy_id} Delete a monitor configuration policy · Datadog Delete a Monitor Configuration Policy #
Ask an LLM
“How do I stop enforcing a monitor tag policy?”
“Can I delete a monitor configuration policy I no longer need?”
Tell an agent destructive · confirm first
Delete monitor configuration policy {policy_id}.
Remove the monitor policy {policy_id}.
GET /api/v2/monitor/policy/{policy_id} Get a monitor configuration policy · Datadog Get a Monitor Configuration Policy #
Ask an LLM
“Which tag keys and values does a monitor configuration policy require?”
“Can I read one monitor config policy by its ID?”
Tell an agent
Get monitor configuration policy {policy_id}.
Show the rules in monitor policy {policy_id}.
PATCH /api/v2/monitor/policy/{policy_id} Edit a monitor configuration policy · Datadog Edit a Monitor Configuration Policy #
Ask an LLM
“How do I change the allowed tag values in an existing monitor policy?”
“Can I edit a monitor configuration policy without recreating it?”
Tell an agent
Edit monitor configuration policy {policy_id} with {changes}.
Update the required tags in monitor policy {policy_id} to {changes}.

Documentation

📖
Documentation
https://docs.datadoghq.com/api/latest/
📖
Authentication
https://docs.datadoghq.com/api/latest/authentication/
📖
Documentation
https://docs.datadoghq.com/api/latest/metrics/
📖
Documentation
https://docs.datadoghq.com/api/latest/logs/
📖
Documentation
https://docs.datadoghq.com/api/latest/events/
📖
Documentation
https://docs.datadoghq.com/api/latest/monitors/
📖
Documentation
https://docs.datadoghq.com/api/latest/incidents/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/openapi/datadog-configuration-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/json-schema/datadog-metric-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/json-schema/datadog-log-event-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/json-schema/datadog-event-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/json-schema/datadog-monitor-schema.json

Other Resources

🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/graphql/datadog-graphql.md
🔗
Reference
https://docs.datadoghq.com/metrics/
🔗
Reference
https://docs.datadoghq.com/logs/
🔗
Reference
https://docs.datadoghq.com/service_management/events/
🔗
Reference
https://docs.datadoghq.com/monitors/
🔗
Reference
https://docs.datadoghq.com/service_management/incident_management/

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/datadog:datadog-configuration-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

datadog-configuration-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  contact:
    email: support@datadoghq.com
    name: Datadog Support
    url: https://www.datadoghq.com/support/
  description: The Datadog API is an HTTP REST API. The API uses resource-oriented URLs to call the API, uses status codes to indicate the success or failure of requests, returns JSON from all requests, and uses standard HTTP response codes. Use the Datadog API to access the Datadog platform programmatically.
  title: Datadog Configuration API
  version: '1.0'
servers:
- url: https://{subdomain}.{site}
  variables:
    site:
      default: datadoghq.com
      description: The regional site for Datadog customers.
      enum:
      - datadoghq.com
      - us3.datadoghq.com
      - us5.datadoghq.com
      - ap1.datadoghq.com
      - datadoghq.eu
      - ddog-gov.com
    subdomain:
      default: api
      description: The subdomain where the API is deployed.
- url: '{protocol}://{name}'
  variables:
    name:
      default: api.datadoghq.com
      description: Full site DNS name.
    protocol:
      default: https
      description: The protocol for accessing the API.
- url: https://{subdomain}.{site}
  variables:
    site:
      default: datadoghq.com
      description: Any Datadog deployment.
    subdomain:
      default: api
      description: The subdomain where the API is deployed.
security:
- apiKeyAuth: []
  appKeyAuth: []
tags:


# --- truncated at 32 KB (37 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/datadog/refs/heads/main/openapi/datadog-configuration-api-openapi.yml