Datadog · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Datadog Patch API

4 actions 4 updates phrasing extends openapi/datadog-patch-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.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/api/v2/scim/Users/{user_uuid}'].patch
$.paths['/api/v2/security/signals/notification_rules/{id}'].patch
$.paths['/api/v2/security/vulnerabilities/notification_rules/{id}'].patch

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Datadog Patch API
  version: 1.0.0
extends: openapi/datadog-patch-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: 3
- target: $.paths['/api/v2/scim/Users/{user_uuid}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Patch a SCIM user
      effect: write
      questions:
      - How do I deactivate or rename a user through SCIM?
      - Can I apply SCIM patch operations to a single user?
      instructions:
      - text: Apply SCIM patch {Operations} to user {user_uuid}.
        slots:
          Operations: requestBody.Operations
          user_uuid: path.user_uuid
      - text: Partially update SCIM user {user_uuid} with {Operations}.
        slots:
          user_uuid: path.user_uuid
          Operations: requestBody.Operations
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/v2/security/signals/notification_rules/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Patch a security signal notification rule
      effect: write
      questions:
      - How do I change only the recipients of a security signal notification rule?
      - Can I disable a signal-based notification rule without resending every field?
      instructions:
      - text: Patch signal notification rule {id} with {changes}.
        slots:
          id: path.id
          changes: requestBody.data
      - text: Update just {changes} on security signal notification rule {id}.
        slots:
          changes: requestBody.data
          id: path.id
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/v2/security/vulnerabilities/notification_rules/{id}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Patch a vulnerability notification rule
      effect: write
      questions:
      - How do I change the targets of a vulnerability notification rule?
      - Can I partially update a vulnerability-based notification rule?
      instructions:
      - text: Patch vulnerability notification rule {id} with {changes}.
        slots:
          id: path.id
          changes: requestBody.data
      - text: Update just {changes} on vulnerability notification rule {id}.
        slots:
          changes: requestBody.data
          id: path.id
      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.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/datadog-patch-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.