APIBreak

What Datadog changed, 30 April 2026 to 30 October 2026

1029 operations became 1712. 32 were removed, 4 were newly deprecated, 715 were added, and 2 request fields became required.

Read from DataDog/datadog-api-client-go at 5d6a9ae and 7550186 (version 1.0). Generated 31 October 2026 by the specification parser the APIBreak Action uses, applied to Datadog's published specification.

Datadog publishes the OpenAPI description its API clients are generated from in its client repositories. This page reads the v2 API file, .generator/schemas/v2/openapi.yaml in DataDog/datadog-api-client-go; v1 endpoints live in a separate file that is not compared here. Version policy and shutdown dates are not in the specification, so this page does not state them; it reads the deprecated flag on each operation.

Removed from the specification

  • DELETE /api/v2/cloud_auth/aws/persona_mapping/{persona_mapping_id} removed in d7d87d5 · 28 October 2026
  • DELETE /api/v2/metrics/config/bulk-tags removed in 46dc330 · 29 October 2026
  • DELETE /api/v2/services/{service_id}
  • DELETE /api/v2/teams/{team_id}
  • GET /api/unstable/fleet/agent_versions
  • GET /api/unstable/fleet/agents
  • GET /api/unstable/fleet/agents/{agent_key}
  • GET /api/unstable/fleet/clusters
  • GET /api/unstable/fleet/clusters/{cluster_name}/instrumented_pods
  • GET /api/unstable/fleet/deployments
  • GET /api/unstable/fleet/deployments/{deployment_id}
  • GET /api/unstable/fleet/schedules
  • GET /api/unstable/fleet/schedules/{id}
  • GET /api/v2/cloud_auth/aws/persona_mapping removed in d7d87d5 · 28 October 2026
  • GET /api/v2/cloud_auth/aws/persona_mapping/{persona_mapping_id} removed in d7d87d5 · 28 October 2026
  • GET /api/v2/services
  • GET /api/v2/services/{service_id}
  • GET /api/v2/siem-historical-detections/histsignals/search
  • GET /api/v2/spa/recommendations/{service}
  • GET /api/v2/spa/recommendations/{service}/{shard}
  • GET /api/v2/teams
  • GET /api/v2/teams/{team_id}
  • PATCH /api/v2/posture_management/findings
  • PATCH /api/v2/services/{service_id}
  • PATCH /api/v2/teams/{team_id}
  • POST /api/unstable/fleet/deployments/configure
  • POST /api/unstable/fleet/deployments/upgrade
  • POST /api/unstable/fleet/deployments/{deployment_id}/cancel
  • POST /api/v2/cloud_auth/aws/persona_mapping removed in d7d87d5 · 28 October 2026
  • POST /api/v2/metrics/config/bulk-tags removed in 46dc330 · 29 October 2026
  • POST /api/v2/services
  • POST /api/v2/teams

Path parameters renamed, not removed (6)

These operations are still in the current specification at the same URL; only the name of a path parameter changed. A caller sends the same request either way, so they are not counted as removed or added above. Client code generated from the specification may still see a renamed argument.

Show each operation, baseline name first
  • DELETE /api/v2/personal_access_tokens/{pat_id}
    now DELETE /api/v2/personal_access_tokens/{token_id}
  • DELETE /api/v2/service_accounts/{service_account_id}/access_tokens/{pat_id}
    now DELETE /api/v2/service_accounts/{service_account_id}/access_tokens/{token_id}
  • GET /api/v2/personal_access_tokens/{pat_id}
    now GET /api/v2/personal_access_tokens/{token_id}
  • GET /api/v2/service_accounts/{service_account_id}/access_tokens/{pat_id}
    now GET /api/v2/service_accounts/{service_account_id}/access_tokens/{token_id}
  • PATCH /api/v2/personal_access_tokens/{pat_id}
    now PATCH /api/v2/personal_access_tokens/{token_id}
  • PATCH /api/v2/service_accounts/{service_account_id}/access_tokens/{pat_id}
    now PATCH /api/v2/service_accounts/{service_account_id}/access_tokens/{token_id}

Newly deprecated in this window

A deprecation is the notice period. It is the cheapest moment to act and the easiest one to miss. This list compares operations present at the baseline.

  • GET /api/v2/on-call/schedules/{schedule_id}/on-call
  • GET /api/v2/slo/report/{report_id}/download
  • GET /api/v2/slo/report/{report_id}/status
  • POST /api/v2/slo/report

11 operations in the deprecated list below have no matching operation at the baseline, so they are not classified here: the snapshot does not show whether they arrived deprecated or gained the flag later.

Deprecated as of the current specification (30)

Everything the vendor currently marks deprecated, whether or not it changed recently. The vendor has flagged each of these for possible removal, with or without a date attached.

  • DELETE /api/v2/apicatalog/api/{id}
  • DELETE /api/v2/integration/salesforce-incidents/incident-templates/{incident_template_id}
  • DELETE /api/v2/integration/salesforce-incidents/organizations/{salesforce_org_id}
  • DELETE /api/v2/team/{super_team_id}/member_teams/{member_team_id}
  • GET /api/v2/apicatalog/api
  • GET /api/v2/apicatalog/api/{id}/openapi
  • GET /api/v2/compliance_findings/rule_based_view
  • GET /api/v2/cost/oci_config
  • GET /api/v2/integration/salesforce-incidents/incident-templates
  • GET /api/v2/integration/salesforce-incidents/organizations
  • GET /api/v2/llm-obs/v1/experiments/{experiment_id}/events
  • GET /api/v2/llm-obs/v2/experiments/{experiment_id}/events
  • GET /api/v2/on-call/schedules/{schedule_id}/on-call
  • GET /api/v2/security/vulnerabilities
  • GET /api/v2/slo/report/{report_id}/download
  • GET /api/v2/slo/report/{report_id}/status
  • GET /api/v2/team/{super_team_id}/member_teams
  • GET /api/v2/usage/application_security
  • GET /api/v2/usage/cost_by_org
  • GET /api/v2/usage/lambda_traced_invocations
  • GET /api/v2/usage/observability_pipelines
  • PATCH /api/v2/integration/salesforce-incidents/incident-templates/{incident_template_id}
  • POST /api/v2/apicatalog/openapi
  • POST /api/v2/dora/incident
  • POST /api/v2/incidents/{incident_id}/cases/page
  • POST /api/v2/integration/salesforce-incidents/incident-templates
  • POST /api/v2/scorecard/outcomes/batch
  • POST /api/v2/slo/report
  • POST /api/v2/team/{super_team_id}/member_teams
  • PUT /api/v2/apicatalog/api/{id}/openapi

Request fields removed from the specification

The current specification no longer lists these request fields, which the baseline did. A caller that still sends one is sending a parameter the new version does not define; whether Datadog rejects or ignores it at runtime is not something a specification diff can show, and what it means for an integration depends on how Datadog versions — see the note at the top of this page.

  • PATCH /api/v2/static-analysis/custom/rulesets/{ruleset_name} no longer lists data.attributes.rules[].last_revision.attributes (application/json)
  • PATCH /api/v2/static-analysis/custom/rulesets/{ruleset_name} no longer lists data.attributes.rules[].last_revision.type (application/json)
  • PATCH /api/v2/statuspages/{page_id} no longer lists data.attributes.enabled (application/json)
  • POST /api/v2/siem-historical-detections/jobs no longer lists data.attributes.id (application/json)
  • POST /api/v2/siem-historical-detections/jobs/signal_convert no longer lists data.attributes.id (application/json)
  • POST /api/v2/statuspages no longer lists data.attributes.enabled (application/json)

Request fields that became required

Only JSON request bodies are compared. A top-level field applies whenever the operation is sent a JSON body. A nested field applies only inside each object containing it that is sent (for an array, each element), so a caller that never sends that object, or sends an empty array, is not affected.

  • POST /api/v2/agentless_scanning/accounts/aws — now requires data.attributes.compliance_host when data.attributes is sent
  • POST /api/v2/deletion/data/{product} — now requires data.attributes.displayed_total when data.attributes is sent

Datadog API questions

Every answer below is computed from the snapshot above, and each links to the Datadog specification it was read from.

Which Datadog API endpoints were removed recently?
32 operations were removed from .generator/schemas/v2/openapi.yaml in DataDog/datadog-api-client-go between 30 April 2026 and 30 October 2026: DELETE /api/v2/cloud_auth/aws/persona_mapping/{persona_mapping_id}, DELETE /api/v2/metrics/config/bulk-tags, DELETE /api/v2/services/{service_id}, DELETE /api/v2/teams/{team_id}, GET /api/unstable/fleet/agent_versions, GET /api/unstable/fleet/agents, GET /api/unstable/fleet/agents/{agent_key}, GET /api/unstable/fleet/clusters and 24 more (all listed above). The file went from 1029 to 1712 operations.
Source: DataDog/datadog-api-client-go, the two commits compared
Which Datadog API endpoints are deprecated?
As of 30 October 2026, .generator/schemas/v2/openapi.yaml in DataDog/datadog-api-client-go marks 30 operations deprecated: DELETE /api/v2/apicatalog/api/{id}, DELETE /api/v2/integration/salesforce-incidents/incident-templates/{incident_template_id}, DELETE /api/v2/integration/salesforce-incidents/organizations/{salesforce_org_id}, DELETE /api/v2/team/{super_team_id}/member_teams/{member_team_id}, GET /api/v2/apicatalog/api, GET /api/v2/apicatalog/api/{id}/openapi, GET /api/v2/compliance_findings/rule_based_view, GET /api/v2/cost/oci_config and 22 more (all listed above). 4 compared operations (paired with a baseline operation) gained the deprecated flag between 30 April 2026 and 30 October 2026. 15 were already deprecated at the baseline. 11 have no matching operation at the baseline (added during the window), so this page does not say whether they arrived deprecated or were deprecated later.
Source: DataDog/datadog-api-client-go, the two commits compared
Did any Datadog API request fields become required?
2 JSON request fields became required between 30 April 2026 and 30 October 2026: data.attributes.compliance_host on POST /api/v2/agentless_scanning/accounts/aws and data.attributes.displayed_total on POST /api/v2/deletion/data/{product}. All are nested, so each applies only inside each object containing it (the part before the last dot; for an array, each element) that a JSON request body sends: such an object sent without the field no longer matches the current specification, and a body that omits the object, or sends an empty array, is unaffected. The 6 operations whose path parameters were renamed in this window are not compared for request fields.
Source: DataDog/datadog-api-client-go, the two commits compared
Where is the Datadog OpenAPI specification?
In the DataDog/datadog-api-client-go repository on GitHub. This page reads .generator/schemas/v2/openapi.yaml at commit 7550186 (version 1.0), dated 30 October 2026.
Source: DataDog/datadog-api-client-go on GitHub

The Action does not check Datadog yet

It checks GitHub REST and Stripe. If you want your CI to check the Datadog endpoints you call, say so in an issue, because requests like that decide which vendor the Action should support next.

a real report

API changes at other vendors

See every vendor