Datadog · OpenAPI Overlay 1.0.0
API Evangelist conversational phrasing for Datadog Configuration API
9 actions
9 updates
phrasing
extends
openapi/datadog-configuration-api-openapi.yml
Generated by API Evangelist
Written by API Evangelist tooling for Datadog's API. It is a proposal applied on top of the contract, not a document Datadog publishes.
What the actions change
x-apievangelist-phrasing
Targets 9
$.info
$.paths['/api/v2/metrics/{metric_name}/tags'].get
$.paths['/api/v2/metrics/{metric_name}/tags'].post
$.paths['/api/v2/metrics/{metric_name}/tags'].delete
$.paths['/api/v2/metrics/{metric_name}/tags'].patch
$.paths['/api/v2/monitor/policy'].post
$.paths['/api/v2/monitor/policy/{policy_id}'].get
$.paths['/api/v2/monitor/policy/{policy_id}'].delete
$.paths['/api/v2/monitor/policy/{policy_id}'].patch
OpenAPI Overlay
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Datadog Configuration API
version: 1.0.0
extends: openapi/datadog-configuration-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-10-01'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 8
- target: $.paths['/api/v2/metrics/{metric_name}/tags'].get
update:
x-apievangelist-phrasing:
intent: Get a metric's tag configuration
effect: read
questions:
- Which tag keys are queryable for a given metric?
- Can I see the current Metrics without Limits configuration for one metric?
instructions:
- text: Show the tag configuration for metric {metric_name}.
slots:
metric_name: path.metric_name
- text: List the queryable tag keys configured on {metric_name}.
slots:
metric_name: path.metric_name
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/metrics/{metric_name}/tags'].post
update:
x-apievangelist-phrasing:
intent: Create a tag configuration for a metric
effect: write
questions:
- 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?
instructions:
- text: Create a tag configuration on {metric_name} with {config}.
slots:
metric_name: path.metric_name
config: requestBody.data
- text: Define the queryable tags for metric {metric_name} as {config}.
slots:
metric_name: path.metric_name
config: requestBody.data
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/metrics/{metric_name}/tags'].delete
update:
x-apievangelist-phrasing:
intent: Delete a metric's tag configuration
effect: destructive
questions:
- How do I remove the tag configuration from a metric?
- What permission is needed to delete a metric's tag configuration?
instructions:
- text: Delete the tag configuration on metric {metric_name}.
slots:
metric_name: path.metric_name
- text: Remove Metrics without Limits settings from {metric_name}.
slots:
metric_name: path.metric_name
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/metrics/{metric_name}/tags'].patch
update:
x-apievangelist-phrasing:
intent: Update a metric's tag configuration
effect: write
questions:
- 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?
instructions:
- text: Update the tag configuration of {metric_name} to {config}.
slots:
metric_name: path.metric_name
config: requestBody.data
- text: Change the existing queryable tags on metric {metric_name} with {config}.
slots:
metric_name: path.metric_name
config: requestBody.data
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/monitor/policy'].post
update:
x-apievangelist-phrasing:
intent: Create a monitor configuration policy
effect: write
questions:
- How do I require specific tags on every new monitor?
- Can I enforce a tag policy for monitors across my organization?
instructions:
- text: Create a monitor configuration policy with {policy}.
slots:
policy: requestBody.data
- text: Add a monitor tag policy defined as {policy}.
slots:
policy: requestBody.data
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/monitor/policy/{policy_id}'].get
update:
x-apievangelist-phrasing:
intent: Get a monitor configuration policy
effect: read
questions:
- Which tag keys and values does a monitor configuration policy require?
- Can I read one monitor config policy by its ID?
instructions:
- text: Get monitor configuration policy {policy_id}.
slots:
policy_id: path.policy_id
- text: Show the rules in monitor policy {policy_id}.
slots:
policy_id: path.policy_id
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/monitor/policy/{policy_id}'].delete
update:
x-apievangelist-phrasing:
intent: Delete a monitor configuration policy
effect: destructive
questions:
- How do I stop enforcing a monitor tag policy?
- Can I delete a monitor configuration policy I no longer need?
instructions:
- text: Delete monitor configuration policy {policy_id}.
slots:
policy_id: path.policy_id
- text: Remove the monitor policy {policy_id}.
slots:
policy_id: path.policy_id
method: generated
generated: '2026-10-01'
- target: $.paths['/api/v2/monitor/policy/{policy_id}'].patch
update:
x-apievangelist-phrasing:
intent: Edit a monitor configuration policy
effect: write
questions:
- How do I change the allowed tag values in an existing monitor policy?
- Can I edit a monitor configuration policy without recreating it?
instructions:
- text: Edit monitor configuration policy {policy_id} with {changes}.
slots:
policy_id: path.policy_id
changes: requestBody.data
- text: Update the required tags in monitor policy {policy_id} to {changes}.
slots:
policy_id: path.policy_id
changes: requestBody.data
method: generated
generated: '2026-10-01'
Work with this as data
Every overlay 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 openapi overlays
4 MCP tools reach this
find_overlaysBrowse and filter every overlay in the catalog.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.
Call it yourself
curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/datadog-configuration-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.
A second provider on the same verified email joins the account you already have.