[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqpMr71nAczeol8E2bbtqsAiDqPcKpk0_ORLpWrgDVJM":3,"$flw3mWziuUCzbqe7xdUonYy59b6X7rFqEge4oayVgzCQ":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"datadog-v2-openapi","Datadog API v2","datadog","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FDataDog\u002Fdatadog-api-client-typescript\u002Fmaster\u002F.generator\u002Fschemas\u002Fv2\u002Fopenapi.yaml",{"id":13,"contentHash":14,"fetchedAt":15},"01KX1VZ3NJ23QEJ2H05BMR5HEQ","0a3120554acdb0789323ca1dead12d7e2d10c77de9fa5c90a692034a32b2fb00","2026-07-08T22:00:54.054Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX3FEJQZMRZWT1QJ5CDG5CRZ","2c3482ea2dbd72097facd1a5f58a7ba60f6db4198d4ccbf92b019deedf5c8146","2026-07-09T13:00:38.202Z",null,{"alerts":22},[23,30,37,44,51,58,65,72,79,86,94,101,108,115,122,129,136,143,150,158,165,172,179,186,193,200,207,214,221,228,235,242,249,256,263,270,277,284,291,298,305,312,319,326,333,340,347,354,361,368],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX3FEWJ5MEEG1PM017HV9B2R","Additive","Add Entra ID Azure App Registrations endpoints and models","New endpoints and models added for managing Entra ID Azure App Registrations in Security Monitoring:\n- New GET endpoint `\u002Fapi\u002Fv2\u002Fsecurity_monitoring\u002Fconfiguration\u002Fintegration_config\u002Fentra_id\u002Fazure_app_registrations` to retrieve Azure App Registrations and Entra ID integration status\n- New POST endpoints for `\u002Fapi\u002Fv2\u002Fsecurity_monitoring\u002Fconfiguration\u002Fintegration_config\u002F{integration_type}\u002Factivate` and `\u002Fdeactivate` to manage entity context sync integrations\n- Added schema definitions: `SecurityMonitoringAzureAppRegistration`, `SecurityMonitoringEntraIdAzureAppRegistrations*` models, and `SecurityMonitoringIntegrationActivate*` request models\n- Made `secrets` field optional in `SecurityMonitoringIntegrationConfigCreateAttributes` and `SecurityMonitoringIntegrationConfigUpdateAttributes` to support source types like Entra ID that don't require secrets\n\nAll changes are additive and do not break existing integrations.","2026-07-09T13:00:49.605Z","2026-07-09-add-entra-id-azure-app-registrations-endpoints-and-models",{"id":31,"severity":32,"title":33,"summary":34,"contentHash":14,"detectedAt":35,"slug":36},"01KX1VZFCGZ6Q0C918V4HZKS6W","Breaking","Remove attached_to, prerequisite, table_id fields from IncidentUserDefinedFieldAttributesResponse","Three fields — **`attached_to`**, **`prerequisite`**, and **`table_id`** — have been removed from the `IncidentUserDefinedFieldAttributesResponse` schema, including from its `required` array. Clients that read or deserialize these fields from incident user-defined field API responses will either fail deserialization (if strict) or silently lose data. All four incident user-defined field endpoints are affected, as reflected in the removed example values.","2026-07-08T22:01:07.216Z","2026-07-08-remove-attached-to-prerequisite-table-id-fields-from",{"id":38,"severity":25,"title":39,"summary":40,"contentHash":41,"detectedAt":42,"slug":43},"01KX1E74RAY1HRGAXDR8GS6RCF","Add ServerlessFunction asset type to SBOM list endpoint","The Datadog SBOM API now supports a new **ServerlessFunction** asset type alongside existing types. Documentation clarifies that the `filter[asset_type]` parameter is required for initial requests, and that infrastructure asset types (`Host`, `HostImage`, `Image`, `ServerlessFunction`) cannot be mixed with code types (`Repository`, `Service`) in the same request. This is backward-compatible; existing code continues to work unchanged.","ea5cf83e11c805e7285a174834a2cae26f4ceec8076d5fb5aa9942da6f253fea","2026-07-08T18:00:38.410Z","2026-07-08-add-serverlessfunction-asset-type-to-sbom-list-endpoint",{"id":45,"severity":25,"title":46,"summary":47,"contentHash":48,"detectedAt":49,"slug":50},"01KWYE314RTEKZCGS9GWHNR7R3","Add user\u002Forg identity provider and OAuth2 client authorization endpoints","This update introduces new API endpoints and path parameters to manage identity provider overrides for users and OAuth2 client authorizations. **New endpoints** include `GET \u002Fapi\u002Fv2\u002Fusers\u002F{user_id}\u002Fidentity_providers`, `PATCH \u002Fapi\u002Fv2\u002Fusers\u002F{user_id}\u002Frelationships\u002Fidentity_providers`, and related infrastructure for user and organization authorized client management. The changes also add new path parameter types (`IdentityProviderId`, `OAuth2ClientId`, `OrgAuthorizedClientId`, `UserAuthorizedClientId`, `UserAuthorizedClientIdForOrg`, `UserIdForOrgClient`) and new API tags for organizing these capabilities. The DORA deployment schema also changed timestamp fields from Unix nanoseconds to ISO 8601 strings and made `finished_at` optional, which is a **breaking change to the schema** but backward-compatible if clients only read the fields.","45bb51d786da44812f952063dbbd25534bf8b65aacc3ef5e008e87436f6db9b1","2026-07-07T14:00:40.344Z","2026-07-07-add-user-org-identity-provider-and-oauth2-client",{"id":52,"severity":25,"title":53,"summary":54,"contentHash":55,"detectedAt":56,"slug":57},"01KWY3SA4HH6QSWW59CG2C7TC3","Add Linear issue integration for security findings","Two new endpoints and four new schema types added to support creating and attaching security findings to Linear issues. **POST** and **PATCH** `\u002Fapi\u002Fv2\u002Fsecurity\u002Ffindings\u002Flinear_issues` enable bidirectional sync between Datadog security findings and Linear issues; new request\u002Fresponse schema types (`AttachLinearIssueRequest`, `CreateLinearIssueRequestArray`, etc.) and `linear_issue` field added to `FindingCase` response. All changes are purely additive with no breaking modifications to existing endpoints or schemas.","2929c6607bf7cd4fe09186c900ac90fd68e9264efa79a56dd99cc7e702684ecb","2026-07-07T11:00:36.113Z","2026-07-07-add-linear-issue-integration-for-security-findings",{"id":59,"severity":25,"title":60,"summary":61,"contentHash":62,"detectedAt":63,"slug":64},"01KWV72XYXYP341VXCEW3N9E6J","Add workload_activity rule type to notification rules","A new enum value `workload_activity` has been added to the rule type options for notification rules in the Datadog API. This is an additive change that allows vulnerability-based notification rules to filter by this additional rule type without affecting existing integrations.","2fa1779a07e2a4edbaf089a382feff1df0909e58a4bdd2a509ca621c2df13fb2","2026-07-06T08:00:33.757Z","2026-07-06-add-workload-activity-rule-type-to-notification-rules",{"id":66,"severity":25,"title":67,"summary":68,"contentHash":69,"detectedAt":70,"slug":71},"01KWJA4BQ6HFT3YPR07HZQPNKG","Add IncidentTypeConfiguration schema and configuration field","Added a new `IncidentTypeConfiguration` schema with incident-type-scoped behavior settings, and added a read-only `configuration` field to `IncidentTypeAttributes` and `IncidentTypeUpdateAttributes`. Also added a new `IncidentTypeSlugSource` enum for ServiceNow integration support. These are purely additive changes to the Incident Type resource that do not break existing integrations.","4b8451b16053ca5a9af07ad0b3d8fddbf3f692fccb643b7c618fbc8f82ddbd01","2026-07-02T21:00:36.454Z","2026-07-02-add-incidenttypeconfiguration-schema-and-configuration-field",{"id":73,"severity":25,"title":74,"summary":75,"contentHash":76,"detectedAt":77,"slug":78},"01KWJ6PE8YKCQZWZXPC4V3VK8R","Add POST \u002Fapi\u002Fv2\u002Fsnapshot endpoint for graph snapshots","A new **POST \u002Fapi\u002Fv2\u002Fsnapshot** endpoint has been added to create graph widget snapshots. This includes new request\u002Fresponse schemas (`CreateSnapshotRequest`, `CreateSnapshotResponse`) and supporting types for template variables, TTL configuration, and legend styling. The endpoint is in preview and subject to change.","3c98dd3870f3662959309ec0dc228b5a0b64d608f8cf6b593eeda8c3117e594d","2026-07-02T20:00:34.590Z","2026-07-02-add-post-api-v2-snapshot-endpoint-for-graph-snapshots",{"id":80,"severity":25,"title":81,"summary":82,"contentHash":83,"detectedAt":84,"slug":85},"01KWHENDJ2S5ZD9KNRX036S73M","Add S3 server-side encryption options to Observability Pipeline","New optional fields `server_side_encryption` and `ssekms_key_id` added to the Amazon S3 destination configuration for Observability Pipelines, along with a new enum type `ObservabilityPipelineAmazonS3DestinationServerSideEncryption`. These fields allow customers to specify encryption method (AWS KMS or AES256) and provide a KMS key ID when using KMS encryption, with no breaking changes to existing configurations.","79fe7ae2997e9dbeff122a9b676e7b3e61c8f435381679e3253598824b191bae","2026-07-02T13:00:35.266Z","2026-07-02-add-s3-server-side-encryption-options-to-observability",{"id":87,"severity":88,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KWGXG4HPQKACJDAYA4NWCVE1","Informational","Clarified test ID documentation across flaky test APIs","Updated documentation strings for the `id` field in flaky test schemas to clarify that it represents the `@test.fingerprint_fqn` facet value and can be used with the new `fingerprint_fqn` search filter. No API behavior or schema structure changed—these are pure documentation improvements to help engineers better understand and use the existing test ID field.","1e54a85ca3a3bc39d4995003bc3621a93e4653394deea78c35f62cd12861b25c","2026-07-02T08:00:36.406Z","2026-07-02-clarified-test-id-documentation-across-flaky-test-apis",{"id":95,"severity":25,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KWFDDZMS2TG09V36ZDMA15ZP","Add included field and pagination meta to reference table responses","The diff adds three new optional response fields: an `included` array to `BatchRowsQueryResponse` containing full row resources, and a `meta` object to `ListRowsResponse` with pagination details including `next_continuation_token`. It also expands the list of supported Datadog sites to include `uk1.datadoghq.com`. These are purely additive changes that do not alter existing fields or break backward compatibility.","4f80be62df9057b3fe7f182f4b1a4ac1126424b455f49e54e17ad2bc762e7d1d","2026-07-01T18:00:34.201Z","2026-07-01-add-included-field-and-pagination-meta-to-reference-table",{"id":102,"severity":25,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KWEZPQ6431EYJV2WE205CYF5","Add field and rule variation support to parse_grok processor","The parse_grok processor schema was extended with a new optional `field` parameter (defaults to \"message\") and introduces a new `ObservabilityPipelineParseGrokProcessorRuleItem` type that supports either source-based or include-based Grok rules via `oneOf`. Existing integrations using the original `ObservabilityPipelineParseGrokProcessorRule` will continue to work; the schema now allows callers to specify which log field to parse and supports an alternative rule structure using include queries.","3d598e5cd8bc607e8316c8d6aa715343ccde02f2e83ab393cea490243aa1aaac","2026-07-01T14:00:40.388Z","2026-07-01-add-field-and-rule-variation-support-to-parse-grok-processor",{"id":109,"severity":25,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KWEND00KX6TKR3CV7YZ6MHDC","Add optional condition fields and S3 access key support","The API now allows conditions to reference saved filters via an optional `saved_filter_id` field, making `operator`, `attribute`, and `value` conditionally required rather than always required. Additionally, S3 archive integrations now support both access-key-based and IAM-role-based authentication approaches. A new optional `description` field was added to critical assets. All changes are backwards-compatible as they only add new optional fields and make previously required fields conditionally required.","6cab4fdf053a9efd7f5f1c87e8fab882160630b1343ec37ac714661298dc31be","2026-07-01T11:00:35.987Z","2026-07-01-add-optional-condition-fields-and-s3-access-key-support",{"id":116,"severity":88,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KWEHZ1E2VD9KMW8X0XXJA8EP","Removed preview notice from security findings endpoints","Removed the `x-unstable` preview notice from two security findings endpoints (`POST` and `PUT` on a security findings path), indicating these endpoints are no longer in preview status. This is a documentation-only change that does not affect runtime behavior or API contract.","703af6848186fbd2e4062288f5e9fa4871cd26198bd8689ab151b29195b18395","2026-07-01T10:00:32.962Z","2026-07-01-removed-preview-notice-from-security-findings-endpoints",{"id":123,"severity":88,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KWC3022YJB04E6NZBGGAAG7W","Update worked_by parameter description for clarity","The description of the `worked_by` query parameter was updated to clarify that it filters by user handle rather than user UUID. This is a documentation-only change that does not affect the parameter's actual behavior or API contract.","22b158810c723281317137aea99c844a3404ec16a73be201aff21d3a96867ac0","2026-06-30T11:00:28.894Z","2026-06-30-update-worked-by-parameter-description-for-clarity",{"id":130,"severity":25,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KWBW4FBSYQVEQDZGF79TH18K","Add TLS config to ObservabilityPipelineCloudPremDestination, mark Tag Indexing Rules as preview","The diff adds a new optional `tls` field to the `ObservabilityPipelineCloudPremDestination` schema to support TLS encryption configuration. Additionally, all Tag Indexing Rules endpoints are now marked with `x-unstable` metadata indicating the feature is in preview. Both changes are additive and backwards-compatible.","14bc489d4986bab4de9e79e1c6befd262d72d40367eb512bb6d70f28f351c7fd","2026-06-30T09:00:33.529Z","2026-06-30-add-tls-config-to-observabilitypipelinecloudpremdestination",{"id":137,"severity":32,"title":138,"summary":139,"contentHash":140,"detectedAt":141,"slug":142},"01KWAC2KK2KH9NNSKVK8C1NN68","Remove tls field from ObservabilityPipelineCloudPremDestination","The **`tls`** field (referencing `ObservabilityPipelineTls`) has been removed from the `ObservabilityPipelineCloudPremDestination` schema. Any client code that sets or reads `tls` on this destination object will break. Additionally, `uk1.datadoghq.com` has been added as a valid server enum value, which is purely additive.","54ee0009ef342683663ffbd1223781be3d7bcaaa0659821afe1d0c3a64c98cc2","2026-06-29T19:00:40.674Z","2026-06-29-remove-tls-field-from",{"id":144,"severity":25,"title":145,"summary":146,"contentHash":147,"detectedAt":148,"slug":149},"01KWA56Z0521RTBCEFV50WMADZ","Add TLS configuration to Observability Pipeline cloud-prem destination","A new optional `tls` field has been added to the ObservabilityPipelineCloudPremDestination schema, providing configuration for TLS encryption. This is a purely additive change that does not affect existing integrations.","cdc4f3cc807b2ccd5f910779270645c16eb8bc3241343bb4555c2f1dea521967","2026-06-29T17:00:43.397Z","2026-06-29-add-tls-configuration-to-observability-pipeline-cloud-prem",{"id":151,"severity":152,"title":153,"summary":154,"contentHash":155,"detectedAt":156,"slug":157},"01KW9M1A99YYDYJJ6PZSVRZKS3","Deprecation","Deprecate GET \u002Fapi\u002Fv2\u002Fcompliance_findings\u002Frule_based_view","The `GET \u002Fapi\u002Fv2\u002Fcompliance_findings\u002Frule_based_view` endpoint is now marked as deprecated and will be sunset on 2027-06-26. Clients should migrate to the Security Monitoring - Search Security Findings endpoint instead.","b0b0d09b0c13f2a3e1e0b829db74aabbb6704437a1335322d74c3adf8339f607","2026-06-29T12:00:32.553Z","2026-06-29-deprecate-get-api-v2-compliance-findings-rule-based-view",{"id":159,"severity":32,"title":160,"summary":161,"contentHash":162,"detectedAt":163,"slug":164},"01KW96A6AHF5VHSSN9GW7P681P","CIAppPipelineEventJob schema restructured; FinishedPipeline required field added","Several breaking changes to CI App pipeline event schemas:\n\n- **`CIAppPipelineEventJob`** was previously a concrete object schema; it is now a `oneOf` union of `CIAppPipelineEventFinishedJob` and `CIAppPipelineEventInProgressJob`. Clients that previously used the flat schema will need to handle both variants.\n- **`CIAppPipelineEventFinishedPipeline`** gains a new **required** field `end`, which was previously already present but not listed as required — clients sending pipeline-finished events that omit `end` will now be rejected.\n- **`CIAppPipelineEventFinishedJob`** (new schema, extracted from the old `CIAppPipelineEventJob`) changes required fields: `unique_id` → `id`, and adds `pipeline_unique_id` and `pipeline_name` as required; removes `partial_retry` as required.\n- **`CIAppPipelineEventInProgressJob`** (new schema, extracted from the old `CIAppPipelineEventJob`) changes its `status` reference from `CIAppPipelineEventJobStatus` to the new `CIAppPipelineEventJobInProgressStatus` (enum `[\"running\"]`), and drops `end` from required fields.\n- New schema **`CIAppPipelineEventJobInProgressStatus`** added with enum value `running`.","5f6744e21b672fd483d947faa2839f00b14e70410c5d8beedc0ddcc7a6e90fa3","2026-06-29T08:00:43.345Z","2026-06-29-ciapppipelineeventjob-schema-restructured-finishedpipeline",{"id":166,"severity":25,"title":167,"summary":168,"contentHash":169,"detectedAt":170,"slug":171},"01KW274XAXE32M96Y16SQYKMRZ","Add CycloneDX BOM import endpoint for security vulnerabilities","Datadog API adds support for importing security vulnerabilities via **POST \u002Fapi\u002Fv2\u002Fsecurity\u002Ffindings** using the CycloneDX 1.5 Bill of Materials format. This new endpoint accepts `CycloneDXBom` objects containing vulnerability data for external security scanners. The change includes 11 new schema definitions (`CycloneDXBom`, `CycloneDXComponent`, `CycloneDXMetadata`, etc.) and does not affect existing endpoints or functionality.","0c688cad078c254594b4c871c520a3b199da546b6509a602d4540c2134102c8a","2026-06-26T15:00:37.853Z","2026-06-26-add-cyclonedx-bom-import-endpoint-for-security",{"id":173,"severity":25,"title":174,"summary":175,"contentHash":176,"detectedAt":177,"slug":178},"01KW0CS4AF2GVF16VQPG8PXQ76","Add metric volumes relationship and filtering for list metrics endpoint","The Datadog v2 API adds support for querying metric volumes alongside metric configurations. New optional query parameters `filter[is_configurable]`, `include`, and `sort` enable fetching and organizing metrics by their ingested\u002Findexed volume, with response structures updated to support relationships and included metric volume data. This is purely additive—existing integrations continue working unchanged.","4f12948208b2573ef77f47e656e04587632574289ee3344f08303733ad32c9a2","2026-06-25T22:00:34.383Z","2026-06-25-add-metric-volumes-relationship-and-filtering-for-list",{"id":180,"severity":25,"title":181,"summary":182,"contentHash":183,"detectedAt":184,"slug":185},"01KVZR6FY7QX5AVVDCKSC1T6XN","Add optional buffer field to ClickHouse destination","A new optional `buffer` field has been added to the **ObservabilityPipelineClickhouseDestination** schema, referencing `ObservabilityPipelineBufferOptions`. This is a purely additive change that enables new buffering configuration options for ClickHouse destinations without affecting existing integrations.","55bcb924604c2c5b14d5ca6fde29fb339a036298cb31279f53b59b873d1b9077","2026-06-25T16:00:52.167Z","2026-06-25-add-optional-buffer-field-to-clickhouse-destination",{"id":187,"severity":25,"title":188,"summary":189,"contentHash":190,"detectedAt":191,"slug":192},"01KVZ70R9SWQZ2VCV5FV54D1E0","Report Schedules: Add list and toggle operations, new schemas","Added three new endpoints for report schedules: **GET** `\u002Fapi\u002Fv2\u002Freporting\u002Fschedule\u002F{schedule_uuid}` to retrieve a single schedule, **DELETE** `\u002Fapi\u002Fv2\u002Freporting\u002Fschedule\u002F{schedule_uuid}` to delete a schedule, and **PATCH** `\u002Fapi\u002Fv2\u002Freporting\u002Fschedule\u002F{schedule_uuid}\u002Ftoggle` to activate or pause a schedule. Also added new schemas (`ReportScheduleListResponse`, `ReportScheduleListResponseData`, `ReportScheduleListResponseAttributes`, `ReportScheduleIncludedResourceType`, etc.) and updated example values for the `timeframe` field from \"calendar_month\" to \"1w\". All changes are additive and do not alter existing API behaviour.","42da023eff5080ad7abd45ad6b79e60037ce02b4dc880d2b42e5fd263fbcf12c","2026-06-25T11:00:38.329Z","2026-06-25-report-schedules-add-list-and-toggle-operations-new-schemas",{"id":194,"severity":25,"title":195,"summary":196,"contentHash":197,"detectedAt":198,"slug":199},"01KVXG3909EFRKC43426Q7C7HY","Add Governance Controls API endpoints and schemas","New Governance Controls API endpoints and supporting schemas added to Datadog API v2. Includes **GET** `\u002Fapi\u002Fv2\u002Fgovernance\u002Fcontrols\u002F{detection_type}` and **PATCH** `\u002Fapi\u002Fv2\u002Fgovernance\u002Fcontrols\u002F{detection_type}` endpoints, along with `GovernanceControlAttributes`, `GovernanceControlData`, `GovernanceControlResponse`, and related schema definitions. These are purely additive and do not affect existing integrations.","60f30e0c79331275b0a8b8477a33723961d72798c0110b328d5f96f74a81fea4","2026-06-24T19:00:49.289Z","2026-06-24-add-governance-controls-api-endpoints-and-schemas",{"id":201,"severity":25,"title":202,"summary":203,"contentHash":204,"detectedAt":205,"slug":206},"01KVX970SFTPHGWPTMCH0EX0NT","Add optional cost data parameters to Get Budget endpoint","The GET `\u002Fbudgets\u002F{budget_id}` endpoint gains four new optional query parameters (`actual`, `forecast`, `start`, `end`) that allow clients to request cost data alongside budget information. Three new schema types (`BudgetAttributesCosts`, `BudgetAttributesCostsUnit`, `BudgetWithEntriesDataAttributesEntriesItemsCosts`) are added to support the cost data in responses, and the endpoint documentation is expanded to explain the new functionality. Two new error response codes (400, 404) are also documented. All changes are purely additive and backward-compatible.","514be90cbb1a702dbadf51f51b737d445c5fcb45ac57b582a4d7cddabc9ae0e0","2026-06-24T17:00:31.919Z","2026-06-24-add-optional-cost-data-parameters-to-get-budget-endpoint",{"id":208,"severity":25,"title":209,"summary":210,"contentHash":211,"detectedAt":212,"slug":213},"01KVX5SQVYAQWCCZEZS3HQAWMH","Add custom forecast endpoints for budgets","New endpoints and schemas added to support custom budget forecasting: **`PUT \u002Fapi\u002Fv2\u002Fcost\u002Fbudget\u002Fcustom-forecast`** to create\u002Freplace custom forecasts and **`DELETE \u002Fapi\u002Fv2\u002Fcost\u002Fbudget\u002F{budget_id}\u002Fcustom-forecast`** to delete them. These are additive endpoints with supporting schemas (`CustomForecastEntry`, `CustomForecastResponse`, etc.) that enable clients to define custom monthly forecast amounts scoped by tag filters.","fff240d31efcb3d36f1a6da6c30477a543b7136f6c49e538d12a813c3433714d","2026-06-24T16:00:51.070Z","2026-06-24-add-custom-forecast-endpoints-for-budgets",{"id":215,"severity":25,"title":216,"summary":217,"contentHash":218,"detectedAt":219,"slug":220},"01KVWYXEXMPXAZ0MFE6SPPFT2F","Add WebSocket source and security filter\u002Frule exports","The API adds a new **WebSocket source** type for Observability Pipelines with full support for TLS, authentication strategies (none, basic, bearer, custom), and custom decoding. Additionally, the Terraform export endpoints now support **security filters** and **rules** resource types alongside the existing suppressions and critical_assets types, with updated documentation noting that partner rules cannot be exported.","a4d8c6afa03d6285ff70b77a8611ffa8aadff5fcff77f80bc47f5c9de3256184","2026-06-24T14:00:32.948Z","2026-06-24-add-websocket-source-and-security-filter-rule-exports",{"id":222,"severity":25,"title":223,"summary":224,"contentHash":225,"detectedAt":226,"slug":227},"01KVWH61KSX8EF7YNTXYB99T2N","Add ClickHouse destination for Observability Pipelines","Adds new ClickHouse destination support to Observability Pipelines with schemas for configuration, authentication, batching, compression, and format options. This is purely additive and does not modify existing destination types or API behavior.","14a64d0b572e29d9dba8cf926b55a7e81e5c3f361d3e32602be951eee31afcb4","2026-06-24T10:00:34.169Z","2026-06-24-add-clickhouse-destination-for-observability-pipelines",{"id":229,"severity":25,"title":230,"summary":231,"contentHash":232,"detectedAt":233,"slug":234},"01KVV4HVR37YZVPBJMSBXRTS6T","Add variant management endpoints for feature flags","Three new endpoints have been added to manage feature flag variants: `POST \u002Fapi\u002Fv2\u002Ffeature-flags\u002F{feature_flag_id}\u002Fvariants` to create variants, `PUT \u002Fapi\u002Fv2\u002Ffeature-flags\u002F{feature_flag_id}\u002Fvariants\u002F{variant_id}` to update variants, and `DELETE \u002Fapi\u002Fv2\u002Ffeature-flags\u002F{feature_flag_id}\u002Fvariants\u002F{variant_id}` to delete variants. A new `UpdateVariantRequest` schema and `variant_id` path parameter were also introduced. These are purely additive changes that enable new functionality without affecting existing integrations.","1dc715afb28332ed5a1af0e1b0aadb6f72d988587865e4660349fc2414fcf779","2026-06-23T21:00:35.459Z","2026-06-23-add-variant-management-endpoints-for-feature-flags",{"id":236,"severity":32,"title":237,"summary":238,"contentHash":239,"detectedAt":240,"slug":241},"01KVQK8JPGV3MPXGGX1V9AX3BC","repository_id removed from required fields; deprecated in favor of repository_url","**`repository_id`** has been deprecated and replaced by the new **`repository_url`** field in both `BranchCoverageSummaryRequestData` and `CommitCoverageSummaryRequestData`. Critically, `repository_id` has been **removed from the `required` array** in both schemas — clients that only send `repository_id` (without `repository_url`) may still work today, but the intent is to migrate to `repository_url`. The removal of `repository_id` as a required field is a schema contract change, and clients that relied on the required constraint for validation or code generation will see a difference. The new `repository_url` field accepts full URLs with or without a scheme.","2594532ce3581667b281f152288d469a9d8ef37e251b008f1a1a50d3f503bd67","2026-06-22T12:00:42.192Z","2026-06-22-repository-id-removed-from-required-fields-deprecated-in",{"id":243,"severity":25,"title":244,"summary":245,"contentHash":246,"detectedAt":247,"slug":248},"01KVFHRNJ681G9MAMTYXEKVPMV","Test Optimization service settings schema expansions","Five new optional response fields added to `TestOptimizationServiceSettingsAttributes` (`*_is_overridden` flags) and five new optional request fields added to `TestOptimizationUpdateServiceSettingsRequestAttributes` (`*_inherit` flags) to support service-level setting overrides and inheritance. Additionally, the `id` field example changed format, `pr_comments_enabled` description clarified as repository-level-only (non-overridable), and endpoint documentation updated to reflect inheritance semantics—all backward-compatible additions and clarifications.","d9596614a5a91fae2aecd06416023f7f663ee2d97513c9c29bcefaeaa319f559","2026-06-19T09:00:36.806Z","2026-06-19-test-optimization-service-settings-schema-expansions",{"id":250,"severity":25,"title":251,"summary":252,"contentHash":253,"detectedAt":254,"slug":255},"01KVFEE183NBM9HG327AY233XB","Add degradation update endpoints and status page fields","The Datadog API adds new endpoints for managing degradation updates (`PATCH` and `DELETE` on `\u002Fapi\u002Fv2\u002Fstatuspages\u002F{page_id}\u002Fdegradations\u002F{degradation_id}\u002Fupdates\u002F{update_id}`), a new `DegradationUpdate` schema family for response modeling, and several optional response fields to the status page resource (`enabled`, `slack_app_icon`, `slack_subscriptions_enabled`). Auth scopes are refined across multiple status page endpoints to enforce more granular permission controls. These changes are backward-compatible additions that enhance status page management capabilities.","c9284dcbf7bdcf44a5e0b89d78a54581595acd4d78419714c8480324da13acf9","2026-06-19T08:02:22.595Z","2026-06-19-add-degradation-update-endpoints-and-status-page-fields",{"id":257,"severity":25,"title":258,"summary":259,"contentHash":260,"detectedAt":261,"slug":262},"01KVDKZ1A3WKEYZ4MTKA16W1D7","Add RUM SDK remote configuration management API","This diff adds new endpoints and schemas for managing RUM SDK configurations via remote config. New endpoints `GET \u002Fapi\u002Fv2\u002Fremote_config\u002Fproducts\u002Frum\u002Fconfigs\u002F{config_id}` and `PUT \u002Fapi\u002Fv2\u002Fremote_config\u002Fproducts\u002Frum\u002Fconfigs\u002F{config_id}` enable retrieval and updating of RUM SDK configurations. Additionally, a new `remote_config_id` field is added to the RUM application schema, and 20+ new schema definitions support the remote configuration system.","2cb812caed7cd351a4374fb905fffff564b988947bf4423e7c3e26c86ef26fc1","2026-06-18T15:00:33.731Z","2026-06-18-add-rum-sdk-remote-configuration-management-api",{"id":264,"severity":25,"title":265,"summary":266,"contentHash":267,"detectedAt":268,"slug":269},"01KVDGJJJVWH5BX1FQNJNP6HTJ","Add ticket creation rules endpoints and due date rule schemas","Added new schemas and endpoints for managing security finding automation rules. New schemas include `AutomationRuleActorType`, `AutomationRuleCreatedBy`, `AutomationRuleModifiedBy`, `AutomationRuleScope`, and `DueDateRule*` types for due date automation. New endpoints for ticket creation rules (POST\u002FGET\u002FPUT\u002FDELETE `\u002Fapi\u002Fv2\u002Fsecurity\u002Ffindings\u002Fautomation\u002Fticket_creation_rules*`) and due date rules are now available. These are purely additive and fully backward compatible.","78322228fc6749102a934c27028f55f64c24300e4b95d812c496f790f7628b25","2026-06-18T14:01:19.707Z","2026-06-18-add-ticket-creation-rules-endpoints-and-due-date-rule",{"id":271,"severity":25,"title":272,"summary":273,"contentHash":274,"detectedAt":275,"slug":276},"01KVBP5FRVJ2B2EH9JXYN38AK4","Add Governance Insights API endpoint and schemas","Added a new `\u002Fapi\u002Fv2\u002Fgovernance\u002Finsights` GET endpoint and 13 supporting schema definitions for retrieving governance insights with optional value computation. This is a new capability that does not affect existing endpoints or break any current integrations.","9d1104f20f8952fab0ce03723339171a63f7158436b08781fadab96b5b2d0c49","2026-06-17T21:00:33.435Z","2026-06-17-add-governance-insights-api-endpoint-and-schemas",{"id":278,"severity":25,"title":279,"summary":280,"contentHash":281,"detectedAt":282,"slug":283},"01KVB506MNKAQ7N2CFTNARD5CF","Add IoC triage state endpoints and fields","Adds new triage-related fields (`triage_state`, `triaged_at`, `triaged_by`) to IoC indicator response schemas (`IoCIndicator` and `IoCIndicatorDetailed`), introduces a new POST endpoint `\u002Fapi\u002Fv2\u002Fsecurity\u002Fsiem\u002Fioc-explorer\u002Ftriage` to create\u002Fupdate triage states, and adds supporting data structures and query parameters for filtering. All changes are additive with new optional response fields and a new beta endpoint.","7dfbf22f75cf141190e628a39284591eded02e3c3a50b25e61793ef0141e1e56","2026-06-17T16:00:34.453Z","2026-06-17-add-ioc-triage-state-endpoints-and-fields",{"id":285,"severity":88,"title":286,"summary":287,"contentHash":288,"detectedAt":289,"slug":290},"01KV9Z7FYXRZS09S19YZDMCGKK","Add Go code example to GetUsageSummaryAvailableFields","Added a Go code example to the `GetUsageSummaryAvailableFields` endpoint documentation showing how to iterate through usage fields across multiple layers. This improves developer guidance without changing any API behaviour or contract.","e4a78291607e9e4a2d251ad04c766ba584fc09773cc73b8941109050e4e2d819","2026-06-17T05:00:27.485Z","2026-06-17-add-go-code-example-to-getusagesummaryavailablefields",{"id":292,"severity":25,"title":293,"summary":294,"contentHash":295,"detectedAt":296,"slug":297},"01KV90B516H1A28THMBB1YEET5","Add GET \u002Fapi\u002Fv2\u002Fworkflows list endpoint","New `GET \u002Fapi\u002Fv2\u002Fworkflows` endpoint added to list all workflows in an organization with support for pagination, sorting, filtering, and optional full specs. Three new response schema types (`ListWorkflowsResponse`, `WorkflowListItem`, and related metadata) are introduced to support this endpoint.","7f3750c8aa5ccba7dffed72a2d7e03979aee708c5815bbbcfb7abcb6d6a67d3f","2026-06-16T20:00:41.510Z","2026-06-16-add-get-api-v2-workflows-list-endpoint",{"id":299,"severity":25,"title":300,"summary":301,"contentHash":302,"detectedAt":303,"slug":304},"01KV8SF5YG8YJQHVJBMY4XWRRP","Add GET \u002Fapi\u002Fv2\u002Fsecurity\u002Fasm\u002Fservices endpoint","A new GET endpoint `\u002Fapi\u002Fv2\u002Fsecurity\u002Fasm\u002Fservices\u002F{service_filter}` has been added to retrieve Application Security details for services matching a given name. The change introduces three new schema types (`ApplicationSecurityServiceAttributes`, `ApplicationSecurityServiceResource`, `ApplicationSecurityServiceType`, `ApplicationSecurityServicesMetadata`, `ApplicationSecurityServicesResponse`) and a new path parameter definition (`ApplicationSecurityServiceNameParam`). This is purely additive and does not affect existing functionality.","0b9d306dffad1f583f07b2b39dcd9821b3048d26543c0a198cb7e1e32705aa00","2026-06-16T18:00:33.488Z","2026-06-16-add-get-api-v2-security-asm-services-endpoint",{"id":306,"severity":32,"title":307,"summary":308,"contentHash":309,"detectedAt":310,"slug":311},"01KV8F5RQ0MEVJS7SHMMBA55PW","CloudWorkloadSecurityAgentRuleActionSetValue integer narrowed from int64 to int32","The integer variant of `CloudWorkloadSecurityAgentRuleActionSetValue` has been changed from `format: int64` to `format: int32` with a `maximum: 2147483647`. This is a breaking change for any client that passes or receives integer values larger than 2,147,483,647 (i.e. values that fit in a 64-bit signed integer but not a 32-bit one). Existing integrations sending large int64 values in `set_value` actions will now violate the schema and may be rejected.","96bc078862547a462a00a908b12a944e25641b8fd70e95ff946cfd91769342dd","2026-06-16T15:00:39.264Z","2026-06-16-cloudworkloadsecurityagentruleactionsetvalue-integer",{"id":313,"severity":88,"title":314,"summary":315,"contentHash":316,"detectedAt":317,"slug":318},"01KV8BQSCEVJTDAPFN366YTB6S","Remove x-unstable preview notice from ServiceNow integration endpoints","The `x-unstable` metadata indicating preview status and subject to change has been removed from both the GET and POST endpoints for the ServiceNow security findings integration. This indicates the endpoints have graduated from preview to stable status, which is good news for consumers but does not change the actual API behavior or contract.","c96c4a4744075be77cb94e8d38e5328fb2c70e983a5fc747d02d910eb046f6c6","2026-06-16T14:00:35.470Z","2026-06-16-remove-x-unstable-preview-notice-from-servicenow",{"id":320,"severity":25,"title":321,"summary":322,"contentHash":323,"detectedAt":324,"slug":325},"01KV84VVZYH73CKZHP7QMK69K3","Add inline rule configuration to deployment gates evaluation","The deployment gates evaluation endpoint now supports optional inline rule configuration via a new `configuration` field in `DeploymentGatesEvaluationRequestAttributes`. Four new schema objects define the structure: `DeploymentGatesEvaluationConfiguration`, `DeploymentGatesEvaluationRule`, `DeploymentGatesMonitorRule`, `DeploymentGatesFDDRule`, and related type\u002Foptions schemas. This allows rules to be evaluated directly from the request instead of requiring preconfigured gates, while maintaining backward compatibility with the existing gate-based flow.","0be0027a98126d170fcdf04ad2c4442717c96292d04644a0542f636b2f905538","2026-06-16T12:00:29.182Z","2026-06-16-add-inline-rule-configuration-to-deployment-gates-evaluation",{"id":327,"severity":32,"title":328,"summary":329,"contentHash":330,"detectedAt":331,"slug":332},"01KV7Y0KBT5NSMWB12GRCJ4H0G","PATCH \u002Fapi\u002Fv2\u002Fposture_management\u002Ffindings endpoint removed","The `PATCH \u002Fapi\u002Fv2\u002Fposture_management\u002Ffindings` endpoint (`MuteFindings` \u002F \"Mute or unmute a batch of findings\") has been removed from the spec, along with all associated schemas (`BulkMuteFindingsRequest`, `BulkMuteFindingsRequestAttributes`, `BulkMuteFindingsRequestData`, `BulkMuteFindingsRequestMeta`, `BulkMuteFindingsRequestMetaFindings`, `BulkMuteFindingsRequestProperties`, `BulkMuteFindingsResponse`, `BulkMuteFindingsResponseData`). Any client calling this endpoint to bulk mute\u002Funmute security findings will no longer have a documented contract and the operation will break. Datadog's own docs previously noted to prefer the newer search security findings endpoint, but this removal is an explicit breaking change for existing integrations that rely on the `MuteFindings` operation.","5117d914f685f5f026b22ccdcf8f64f1a4d8f5249d25590acc026dacb9a2b952","2026-06-16T10:00:44.154Z","2026-06-16-patch-api-v2-posture-management-findings-endpoint-removed",{"id":334,"severity":25,"title":335,"summary":336,"contentHash":337,"detectedAt":338,"slug":339},"01KV6DYE3P89EVK9QJRB544DFM","Add Tag Policies API endpoints","Introduces new Tag Policies API endpoints and schemas for managing tag governance rules. Adds `POST \u002Fapi\u002Fv2\u002Ftag-policies`, `GET \u002Fapi\u002Fv2\u002Ftag-policies`, `GET \u002Fapi\u002Fv2\u002Ftag-policies\u002F{policy_id}`, `PATCH \u002Fapi\u002Fv2\u002Ftag-policies\u002F{policy_id}`, and `GET \u002Fapi\u002Fv2\u002Ftag-policies\u002F{policy_id}\u002Fscore` endpoints along with supporting request\u002Fresponse schemas. These are purely new capabilities with no breaking changes to existing APIs.","c94e0cc5e88f2dc038874d7920a859304cebc625fa403f111186f34b318c9aa7","2026-06-15T20:00:41.590Z","2026-06-15-add-tag-policies-api-endpoints",{"id":341,"severity":25,"title":342,"summary":343,"contentHash":344,"detectedAt":345,"slug":346},"01KV5NX8JA2JJFRG6M6PJE4SKV","Add LLM Observability patterns discovery endpoints and schemas","The Datadog API v2 adds support for LLM Observability patterns discovery with several new endpoints, query parameters, and response schemas. This includes `GET \u002Fapi\u002Fv2\u002Fllm-obs\u002Fv1\u002Ftopic-discovery-topics` and `GET \u002Fapi\u002Fv2\u002Fllm-obs\u002Fv1\u002Ftopic-discovery-topics\u002Fwith-cluster-points` for retrieving discovered topics and clustered points, plus new parameter definitions and schema objects like `LLMObsPatternsClusteredPoint`, `LLMObsPatternsTopic`, and related types. All changes are purely additive and do not modify existing functionality.","bcc4ab179a94f2753b173d0ca307153889cf00fa3f79a9f7849bed9b0d88a7c9","2026-06-15T13:00:37.322Z","2026-06-15-add-llm-observability-patterns-discovery-endpoints-and",{"id":348,"severity":32,"title":349,"summary":350,"contentHash":351,"detectedAt":352,"slug":353},"01KV5BKWJA5K9VQFMM8C7JY7KA","RUM hardcoded retention filter endpoints removed; new Security Monitoring and Data Observability endpoints added","This diff contains both breaking removals and additive additions:\n\n- **Breaking**: The entire `RUM Retention Filters Hardcoded` API surface is removed — endpoints `GET \u002Fapi\u002Fv2\u002Frum\u002Fapplications\u002F{app_id}\u002Fretention_filters\u002Fhardcoded` (list), `GET \u002Fapi\u002Fv2\u002Frum\u002Fapplications\u002F{app_id}\u002Fretention_filters\u002Fhardcoded\u002F{rf_id}` (get), and `PATCH \u002Fapi\u002Fv2\u002Frum\u002Fapplications\u002F{app_id}\u002Fretention_filters\u002Fhardcoded\u002F{rf_id}` (update) are gone, along with all associated schemas (`RumHardcodedRetentionFilterAttributes`, `RumHardcodedCrossProductSampling`, etc.) and path parameters.\n- **Additive**: New `POST \u002Fapi\u002Fv2\u002Fsecurity_monitoring\u002Frules\u002F{rule_id}\u002Frestore\u002F{version}` endpoint added (beta) to restore a security monitoring rule to a historical version, with a new `SecurityMonitoringRuleVersion` path parameter.\n- **Additive**: New `Data Observability` API tag and schemas (`DataObservabilityMonitorRunStatus`, `DataObservabilityMonitorRunType`, `GetDataObservabilityMonitorRunStatusResponse`, etc.) added for monitoring data observability monitor run status.","45bf7aa87c50074c41d2080bf10b91c1ff5ef921c668b46f70e2be64e7568812","2026-06-15T10:00:44.362Z","2026-06-15-rum-hardcoded-retention-filter-endpoints-removed-new",{"id":355,"severity":25,"title":356,"summary":357,"contentHash":358,"detectedAt":359,"slug":360},"01KTZ7XG70MVN5EJ232E8PRWTD","Add optional filter[metric] query parameter","Added optional `filter[metric]` query parameter to filter tag keys by Cloud Cost Management metric. This is a purely additive change that does not affect existing integrations and is backward compatible.","7a0c27e6f7243fad8197377b0f51bba8fa15a90b69ed60a999ade5f27bf4776a","2026-06-13T01:00:38.496Z","2026-06-13-add-optional-filter-metric-query-parameter",{"id":362,"severity":25,"title":363,"summary":364,"contentHash":365,"detectedAt":366,"slug":367},"01KTZ4FE9RYP4N9XVMSPV716KR","Add max session duration update endpoint","A new `PUT \u002Fapi\u002Fv2\u002Flogin\u002Forg_configs\u002Fmax_session_duration` endpoint and supporting schema types are added to allow updating the maximum session duration for an organization. This is a purely additive change and does not affect existing integrations.","5e6aac240b7f6f10e2ff6f782bcaf5d1c94e10328643b34883c12a443d1ca847","2026-06-13T00:00:32.056Z","2026-06-13-add-max-session-duration-update-endpoint",{"id":369,"severity":25,"title":370,"summary":371,"contentHash":372,"detectedAt":373,"slug":374},"01KTYPR3WWQ1TWM53NCD15P7CW","Add ObservabilityPipelineGenerateMetricsV2Processor schema","Datadog API v2 adds a new `ObservabilityPipelineGenerateMetricsV2Processor` schema and corresponding type definition to the OpenAPI spec. This is a new processor type for Observability Pipelines that creates custom metrics from logs with enhanced configuration options. The change is purely additive — existing integrations using `ObservabilityPipelineGenerateMetricsProcessor` continue to work unchanged.","1990b3cc3465fd59bf82d144321f8fb61fc282483e87ce58d40dd8171043a6bd","2026-06-12T20:00:36.252Z","2026-06-12-add-observabilitypipelinegeneratemetricsv2processor-schema"]