datadog_api_client 2.46.0 → 2.47.0

data/.generator/schemas/v2/openapi.yaml

@@ -1496,6 +1496,8 @@ components:
           $ref: '#/components/schemas/AWSAccountPartition'
         aws_regions:
           $ref: '#/components/schemas/AWSRegions'
+        ccm_config:
+          $ref: '#/components/schemas/AWSCCMConfig'
         logs_config:
           $ref: '#/components/schemas/AWSLogsConfig'
         metrics_config:
@@ -1561,6 +1563,8 @@ components:
           $ref: '#/components/schemas/AWSAccountPartition'
         aws_regions:
           $ref: '#/components/schemas/AWSRegions'
+        ccm_config:
+          $ref: '#/components/schemas/AWSCCMConfig'
         created_at:
           description: Timestamp of when the account integration was created.
           format: date-time
@@ -1634,6 +1638,8 @@ components:
           $ref: '#/components/schemas/AWSAccountPartition'
         aws_regions:
           $ref: '#/components/schemas/AWSRegions'
+        ccm_config:
+          $ref: '#/components/schemas/AWSCCMConfig'
         logs_config:
           $ref: '#/components/schemas/AWSLogsConfig'
         metrics_config:
@@ -1765,6 +1771,15 @@ components:
       required:
       - role_name
       type: object
+    AWSCCMConfig:
+      description: AWS Cloud Cost Management config.
+      properties:
+        data_export_configs:
+          description: List of data export configurations for Cost and Usage Reports.
+          items:
+            $ref: '#/components/schemas/DataExportConfig'
+          type: array
+      type: object
     AWSCredentials:
       description: The definition of `AWSCredentials` object.
       oneOf:
@@ -5280,7 +5295,7 @@ components:
       description: Data of the case to attach security findings to.
       properties:
         id:
-          description: The unique identifier of the case.
+          description: Unique identifier of the case.
           example: c1234567-89ab-cdef-0123-456789abcdef
           type: string
         relationships:
@@ -5311,10 +5326,6 @@ components:
       properties:
         attributes:
           $ref: '#/components/schemas/AttachJiraIssueRequestDataAttributes'
-        id:
-          description: The unique identifier of the Jira issue attachment request.
-          example: j1234567-89ab-cdef-0123-456789abcdef
-          type: string
         relationships:
           $ref: '#/components/schemas/AttachJiraIssueRequestDataRelationships'
         type:
@@ -5326,7 +5337,7 @@ components:
       description: Attributes of the Jira issue to attach security findings to.
       properties:
         jira_issue_url:
-          description: The URL of the Jira issue to attach security findings to.
+          description: URL of the Jira issue to attach security findings to.
           example: https://domain.atlassian.net/browse/PROJ-123
           type: string
       required:
@@ -5337,8 +5348,12 @@ components:
       properties:
         findings:
           $ref: '#/components/schemas/Findings'
+          description: Security findings to attach to the Jira issue.
         project:
           $ref: '#/components/schemas/CaseManagementProject'
+          description: Case management project with Jira integration configured. It
+            is used to attach security findings to the Jira issue. To configure the
+            integration, see [Bidirectional ticket syncing with Jira](https://docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira).
       required:
       - findings
       - project
@@ -9110,17 +9125,17 @@ components:
       description: An insight of the case.
       properties:
         ref:
-          description: The reference of the insight.
+          description: Reference of the insight.
           example: /security/appsec/vm/library/vulnerability/dfa027f7c037b2f77159adc027fecb56?detection=static
           type: string
         resource_id:
-          description: The unique identifier of the resource. For example, the unique
+          description: Unique identifier of the resource. For example, the unique
             identifier of a security finding.
           example: ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==
           type: string
         type:
-          description: The type of the resource. For example, the type of a security
-            finding is "SECURITY_FINDING".
+          description: Type of the resource. For example, the type of a security finding
+            is "SECURITY_FINDING".
           example: SECURITY_FINDING
           type: string
       type: object
@@ -9135,7 +9150,7 @@ components:
     CaseManagementProjectData:
       properties:
         id:
-          description: The unique identifier of the case management project.
+          description: Unique identifier of the case management project.
           example: aeadc05e-98a8-11ec-ac2c-da7ad0900001
           type: string
         type:
@@ -10243,6 +10258,10 @@ components:
           description: Whether the policy is pinned
           example: false
           type: boolean
+        policyType:
+          description: The type of the policy
+          example: policy
+          type: string
         policyVersion:
           description: The version of the policy
           example: '1'
@@ -10421,11 +10440,11 @@ components:
     CloudWorkloadSecurityAgentPolicyVersion:
       description: The versions of the policy
       properties:
-        Date:
+        date:
           description: The date and time the version was created
           nullable: true
           type: string
-        Name:
+        name:
           description: The version of the policy
           example: 1.47.0-rc2
           type: string
@@ -10452,8 +10471,11 @@ components:
           $ref: '#/components/schemas/CloudWorkloadSecurityAgentRuleActionSet'
       type: object
     CloudWorkloadSecurityAgentRuleActionHash:
-      additionalProperties: {}
-      description: An empty object indicating the hash action
+      description: Hash file specified by the field attribute
+      properties:
+        field:
+          description: The field of the hash action
+          type: string
       type: object
     CloudWorkloadSecurityAgentRuleActionMetadata:
       description: The metadata action applied on the scope matching the rule
@@ -10501,9 +10523,14 @@ components:
           format: int64
           type: integer
         value:
-          description: The value of the set action
-          type: string
+          $ref: '#/components/schemas/CloudWorkloadSecurityAgentRuleActionSetValue'
       type: object
+    CloudWorkloadSecurityAgentRuleActionSetValue:
+      description: The value of the set action
+      oneOf:
+      - type: string
+      - type: integer
+      - type: boolean
     CloudWorkloadSecurityAgentRuleActions:
       description: The array of actions the rule can perform if triggered
       items:
@@ -12882,10 +12909,6 @@ components:
       properties:
         attributes:
           $ref: '#/components/schemas/CreateCaseRequestDataAttributes'
-        id:
-          description: The unique identifier of the case.
-          example: c1234567-89ab-cdef-0123-456789abcdef
-          type: string
         relationships:
           $ref: '#/components/schemas/CreateCaseRequestDataRelationships'
         type:
@@ -12897,21 +12920,21 @@ components:
       description: Attributes of the case to create.
       properties:
         assignee_id:
-          description: The unique identifier of the user assigned to the case.
+          description: Unique identifier of the user assigned to the case.
           example: f315bdaf-9ee7-4808-a9c1-99c15bf0f4d0
           type: string
         description:
-          description: The description of the case. If not provided, the description
-            will be automatically generated.
+          description: Description of the case. If not provided, the description will
+            be automatically generated.
           example: A description of the case.
           type: string
         priority:
           $ref: '#/components/schemas/CasePriority'
-          description: The priority of the case. If not provided, the priority will
-            be automatically set to "NOT_DEFINED".
+          description: Priority of the case. If not provided, the priority will be
+            automatically set to "NOT_DEFINED".
           example: P4
         title:
-          description: The title of the case. If not provided, the title will be automatically
+          description: Title of the case. If not provided, the title will be automatically
             generated.
           example: A title for the case.
           type: string
@@ -12921,10 +12944,10 @@ components:
       properties:
         findings:
           $ref: '#/components/schemas/Findings'
-          description: Security findings of the case to create.
+          description: Security findings to create a case for.
         project:
           $ref: '#/components/schemas/CaseManagementProject'
-          description: Project of the case to create.
+          description: Case management project in which the case will be created.
       required:
       - findings
       - project
@@ -13184,6 +13207,27 @@ components:
       - options
       - type
       type: object
+    CreateEmailNotificationChannelConfig:
+      description: Configuration to create an e-mail notification channel
+      properties:
+        address:
+          description: The e-mail address to be notified
+          example: ''
+          type: string
+        formats:
+          description: Preferred content formats for notifications.
+          example:
+          - html
+          items:
+            $ref: '#/components/schemas/NotificationChannelEmailFormatType'
+          type: array
+        type:
+          $ref: '#/components/schemas/NotificationChannelEmailConfigType'
+      required:
+      - type
+      - address
+      - formats
+      type: object
     CreateIncidentNotificationRuleRequest:
       description: Create request for a notification rule.
       properties:
@@ -13207,29 +13251,14 @@ components:
           items:
             $ref: '#/components/schemas/CreateJiraIssueRequestData'
           type: array
-        included:
-          items:
-            $ref: '#/components/schemas/CreateJiraIssueRequestArrayIncluded'
-          type: array
       required:
       - data
       type: object
-    CreateJiraIssueRequestArrayIncluded:
-      description: 'Attributes and relationships of the case linked to the Jira issue.
-        Should contain all of the following: case, project, and security findings.'
-      oneOf:
-      - $ref: '#/components/schemas/CreateCaseRequestData'
-      - $ref: '#/components/schemas/CaseManagementProjectData'
-      - $ref: '#/components/schemas/FindingData'
     CreateJiraIssueRequestData:
       description: Data of the Jira issue to create.
       properties:
         attributes:
           $ref: '#/components/schemas/CreateJiraIssueRequestDataAttributes'
-        id:
-          description: The unique identifier of the Jira issue creation request.
-          example: j1234567-89ab-cdef-0123-456789abcdef
-          type: string
         relationships:
           $ref: '#/components/schemas/CreateJiraIssueRequestDataRelationships'
         type:
@@ -13240,48 +13269,74 @@ components:
     CreateJiraIssueRequestDataAttributes:
       description: Attributes of the Jira issue to create.
       properties:
+        assignee_id:
+          description: Unique identifier of the user assigned to the Jira issue.
+          example: f315bdaf-9ee7-4808-a9c1-99c15bf0f4d0
+          type: string
+        description:
+          description: Description of the Jira issue. If not provided, the description
+            will be automatically generated.
+          example: A description of the Jira issue.
+          type: string
         fields:
-          $ref: '#/components/schemas/CreateJiraIssueRequestDataAttributesFields'
-      type: object
-    CreateJiraIssueRequestDataAttributesFields:
-      description: Custom fields of the Jira issue to create. For the list of available
-        fields, see [Jira documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-createmeta-projectidorkey-issuetypes-issuetypeid-get).
-      properties:
-        fields:
+          additionalProperties: {}
+          description: Custom fields of the Jira issue to create. For the list of
+            available fields, see [Jira documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-createmeta-projectidorkey-issuetypes-issuetypeid-get).
           example:
-            customfield_10001: Value 1
-            customfield_10002:
-            - Value 2
-            - Value 3
+            key1: value
+            key2:
+            - value
+            key3:
+              key4: value
           type: object
+        priority:
+          $ref: '#/components/schemas/CasePriority'
+          description: Priority of the Jira issue. If not provided, the priority will
+            be automatically set to "NOT_DEFINED".
+          example: P4
+        title:
+          description: Title of the Jira issue. If not provided, the title will be
+            automatically generated.
+          example: A title for the Jira issue.
+          type: string
       type: object
     CreateJiraIssueRequestDataRelationships:
       description: Relationships of the Jira issue to create.
       properties:
-        case:
-          $ref: '#/components/schemas/CreateJiraIssueRequestDataRelationshipsCase'
+        findings:
+          $ref: '#/components/schemas/Findings'
+          description: Security findings to create a Jira issue for.
+        project:
+          $ref: '#/components/schemas/CaseManagementProject'
+          description: Case management project configured with the Jira integration.
+            It is used to create the Jira issue. To configure the Jira integration,
+            see [Bidirectional ticket syncing with Jira](https://docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira).
       required:
-      - case
+      - findings
+      - project
       type: object
-    CreateJiraIssueRequestDataRelationshipsCase:
-      description: Case linked to the Jira issue.
+    CreateNotificationChannelAttributes:
+      description: Attributes for creating an on-call notification channel.
       properties:
-        data:
-          $ref: '#/components/schemas/CreateJiraIssueRequestDataRelationshipsCaseData'
-      required:
-      - data
+        config:
+          $ref: '#/components/schemas/CreateNotificationChannelConfig'
+          description: Notification channel configuration
       type: object
-    CreateJiraIssueRequestDataRelationshipsCaseData:
-      description: Case linked to the Jira issue.
+    CreateNotificationChannelConfig:
+      description: Defines the configuration for creating an On-Call notification
+        channel
+      oneOf:
+      - $ref: '#/components/schemas/CreatePhoneNotificationChannelConfig'
+      - $ref: '#/components/schemas/CreateEmailNotificationChannelConfig'
+    CreateNotificationChannelData:
+      description: Data for creating an on-call notification channel
       properties:
-        id:
-          example: c1234567-89ab-cdef-0123-456789abcdef
-          type: string
+        attributes:
+          $ref: '#/components/schemas/CreateNotificationChannelAttributes'
         type:
-          $ref: '#/components/schemas/CaseDataType'
+          $ref: '#/components/schemas/NotificationChannelType'
       required:
       - type
-      - id
       type: object
     CreateNotificationRuleParameters:
       description: Body of the notification rule create request.
@@ -13443,6 +13498,19 @@ components:
       type: string
       x-enum-varnames:
       - PAGES
+    CreatePhoneNotificationChannelConfig:
+      description: Configuration to create a phone notification channel
+      properties:
+        number:
+          description: The E-164 formatted phone number (e.g. +3371234567)
+          example: ''
+          type: string
+        type:
+          $ref: '#/components/schemas/NotificationChannelPhoneConfigType'
+      required:
+      - type
+      - number
+      type: object
     CreateRuleRequest:
       description: Scorecard create rule request.
       properties:
@@ -14009,6 +14077,23 @@ components:
       type: string
       x-enum-varnames:
       - UPLOAD
+    CreateUserNotificationChannelRequest:
+      description: A top-level wrapper for creating a notification channel for a user
+      example:
+        data:
+          attributes:
+            config:
+              address: foo@bar.com
+              formats:
+              - html
+              type: email
+          type: notification_channels
+      properties:
+        data:
+          $ref: '#/components/schemas/CreateNotificationChannelData'
+      required:
+      - data
+      type: object
     CreateWorkflowRequest:
       description: A request object for creating a new workflow.
       example:
@@ -15837,6 +15922,15 @@ components:
       type: object
     DORAListDeploymentsRequest:
       description: Request to get a list of deployments.
+      example:
+        data:
+          attributes:
+            from: '2025-01-01T00:00:00Z'
+            limit: 100
+            query: service:(shopist OR api-service) env:production team:backend
+            sort: -started_at
+            to: '2025-01-31T23:59:59Z'
+          type: dora_deployments_list_request
       properties:
         data:
           $ref: '#/components/schemas/DORAListDeploymentsRequestData'
@@ -15845,6 +15939,13 @@ components:
       type: object
     DORAListDeploymentsRequestAttributes:
       description: Attributes to get a list of deployments.
+      example:
+        from: '2025-01-01T00:00:00Z'
+        limit: 500
+        query: service:(shopist OR api-service OR payment-service) env:(production
+          OR staging) team:(backend OR platform)
+        sort: -started_at
+        to: '2025-01-31T23:59:59Z'
       properties:
         from:
           description: Minimum timestamp for requested events.
@@ -15869,6 +15970,14 @@ components:
       type: object
     DORAListDeploymentsRequestData:
       description: The JSON:API data.
+      example:
+        attributes:
+          from: '2025-01-15T08:00:00Z'
+          limit: 200
+          query: env:production service:payment-service version:*v2*
+          sort: -finished_at
+          to: '2025-01-15T18:00:00Z'
+        type: dora_deployments_list_request
       properties:
         attributes:
           $ref: '#/components/schemas/DORAListDeploymentsRequestAttributes'
@@ -15886,6 +15995,15 @@ components:
       - DORA_DEPLOYMENTS_LIST_REQUEST
     DORAListFailuresRequest:
       description: Request to get a list of failures.
+      example:
+        data:
+          attributes:
+            from: '2025-01-01T00:00:00Z'
+            limit: 100
+            query: severity:(SEV-1 OR SEV-2) env:production team:backend
+            sort: -started_at
+            to: '2025-01-31T23:59:59Z'
+          type: dora_failures_list_request
       properties:
         data:
           $ref: '#/components/schemas/DORAListFailuresRequestData'
@@ -15894,6 +16012,13 @@ components:
       type: object
     DORAListFailuresRequestAttributes:
       description: Attributes to get a list of failures.
+      example:
+        from: '2025-01-01T00:00:00Z'
+        limit: 500
+        query: severity:(SEV-1 OR SEV-2) env:(production OR staging) service:(shopist
+          OR api-service OR payment-service) team:(backend OR platform OR payments)
+        sort: -started_at
+        to: '2025-01-31T23:59:59Z'
       properties:
         from:
           description: Minimum timestamp for requested events.
@@ -15918,6 +16043,14 @@ components:
       type: object
     DORAListFailuresRequestData:
       description: The JSON:API data.
+      example:
+        attributes:
+          from: '2025-01-15T00:00:00Z'
+          limit: 200
+          query: severity:SEV-1 service:(api-service OR payment-service) env:production
+          sort: -finished_at
+          to: '2025-01-15T23:59:59Z'
+        type: dora_failures_list_request
       properties:
         attributes:
           $ref: '#/components/schemas/DORAListFailuresRequestAttributes'
@@ -15935,6 +16068,39 @@ components:
       - DORA_FAILURES_LIST_REQUEST
     DORAListResponse:
       description: Response for the DORA list endpoints.
+      example:
+        data:
+        - attributes:
+            custom_tags:
+            - language:java
+            - department:engineering
+            - region:us-east-1
+            env: production
+            finished_at: 1693491984000000000
+            git:
+              commit_sha: 66adc9350f2cc9b250b69abddab733dd55e1a588
+              repository_url: https://github.com/organization/example-repository
+            service: shopist
+            started_at: 1693491974000000000
+            team: backend
+            version: v1.12.07
+          id: 4242fcdd31586083
+          type: dora_deployment
+        - attributes:
+            custom_tags:
+            - language:go
+            - department:platform
+            env: production
+            finished_at: 1693492084000000000
+            git:
+              commit_sha: 77bdc9350f2cc9b250b69abddab733dd55e1a599
+              repository_url: https://github.com/organization/api-service
+            service: api-service
+            started_at: 1693492074000000000
+            team: backend
+            version: v2.1.0
+          id: 4242fcdd31586084
+          type: dora_deployment
       properties:
         data:
           description: The list of DORA events.
@@ -16273,6 +16439,30 @@ components:
           example: canceled
           type: string
       type: object
+    DataExportConfig:
+      description: AWS Cost and Usage Report data export configuration.
+      properties:
+        bucket_name:
+          description: Name of the S3 bucket where the Cost and Usage Report is stored.
+          example: billing
+          type: string
+        bucket_region:
+          description: AWS region of the S3 bucket.
+          example: us-east-1
+          type: string
+        report_name:
+          description: Name of the Cost and Usage Report.
+          example: cost-and-usage-report
+          type: string
+        report_prefix:
+          description: S3 prefix where the Cost and Usage Report is stored.
+          example: reports
+          type: string
+        report_type:
+          description: Type of the Cost and Usage Report.
+          example: CUR2.0
+          type: string
+      type: object
     DataRelationshipsTeams:
       description: Associates teams with this schedule in a data structure.
       properties:
@@ -17075,6 +17265,12 @@ components:
       required:
       - id
       type: object
+    DeploymentGateRulesResponse:
+      description: Response for a deployment gate rules.
+      properties:
+        data:
+          $ref: '#/components/schemas/ListDeploymentRuleResponseData'
+      type: object
     DeploymentMetadata:
       description: Metadata object containing the publication creation information.
       properties:
@@ -17281,10 +17477,6 @@ components:
     DetachCaseRequestData:
       description: Data for detaching security findings from their case.
       properties:
-        id:
-          description: The unique identifier of the detachment request.
-          example: f8b9e3b1-24ec-4413-8be5-1b12b98533c6
-          type: string
         relationships:
           $ref: '#/components/schemas/DetachCaseRequestDataRelationships'
         type:
@@ -20219,6 +20411,13 @@ components:
           $ref: '#/components/schemas/EventPayloadAttributes'
         category:
           $ref: '#/components/schemas/EventCategory'
+        host:
+          description: Host name to associate with the event. Any tags associated
+            with the host are also applied to this event. Limited to 255 characters.
+          example: hostname
+          maxLength: 255
+          minLength: 1
+          type: string
         integration_id:
           $ref: '#/components/schemas/EventPayloadIntegrationId'
         message:
@@ -21220,7 +21419,7 @@ components:
         attributes:
           $ref: '#/components/schemas/FindingCaseResponseDataAttributes'
         id:
-          description: The unique identifier of the case.
+          description: Unique identifier of the case.
           example: c1234567-89ab-cdef-0123-456789abcdef
           type: string
         relationships:
@@ -21327,7 +21526,7 @@ components:
     FindingData:
       properties:
         id:
-          description: The unique identifier of the security finding.
+          description: Unique identifier of the security finding.
           example: ZGVmLTAwcC1pZXJ-aS0wZjhjNjMyZDNmMzRlZTgzNw==
           type: string
         type:
@@ -21390,15 +21589,15 @@ components:
       description: Jira issue associated with the case.
       properties:
         error_message:
-          description: The error message if the Jira issue creation failed.
+          description: Error message if the Jira issue creation failed.
           example: '{"errorMessages":["An error occured."],"errors":{}}'
           type: string
         result:
           $ref: '#/components/schemas/FindingJiraIssueResult'
         status:
-          description: The status of the Jira issue creation. Can be "COMPLETED" if
-            the Jira issue was created successfully, or "FAILED" if the Jira issue
-            creation failed.
+          description: Status of the Jira issue creation. Can be "COMPLETED" if the
+            Jira issue was created successfully, or "FAILED" if the Jira issue creation
+            failed.
           example: COMPLETED
           type: string
       type: object
@@ -21406,19 +21605,19 @@ components:
       description: Result of the Jira issue creation.
       properties:
         account_id:
-          description: The account ID of the Jira issue.
+          description: Account ID of the Jira issue.
           example: 463a8631-680e-455c-bfd3-3ed04d326eb7
           type: string
         issue_id:
-          description: The unique identifier of the Jira issue.
+          description: Unique identifier of the Jira issue.
           example: '2871276'
           type: string
         issue_key:
-          description: The key of the Jira issue.
+          description: Key of the Jira issue.
           example: PROJ-123
           type: string
         issue_url:
-          description: The URL of the Jira issue.
+          description: URL of the Jira issue.
           example: https://domain.atlassian.net/browse/PROJ-123
           type: string
       type: object
@@ -24666,6 +24865,30 @@ components:
       required:
       - data
       type: object
+    GetSuppressionVersionHistoryData:
+      description: Data for the suppression version history.
+      properties:
+        attributes:
+          $ref: '#/components/schemas/SuppressionVersionHistory'
+        id:
+          description: ID of the suppression.
+          type: string
+        type:
+          $ref: '#/components/schemas/GetSuppressionVersionHistoryDataType'
+      type: object
+    GetSuppressionVersionHistoryDataType:
+      description: Type of data.
+      enum:
+      - suppression_version_history
+      type: string
+      x-enum-varnames:
+      - SUPPRESSIONVERSIONHISTORY
+    GetSuppressionVersionHistoryResponse:
+      description: Response for getting the suppression version history.
+      properties:
+        data:
+          $ref: '#/components/schemas/GetSuppressionVersionHistoryData'
+      type: object
     GetTeamMembershipsSort:
       description: Specifies the order of returned team memberships
       enum:
@@ -29863,6 +30086,13 @@ components:
     Library:
       description: Vulnerability library.
       properties:
+        additional_names:
+          description: Related library or package names (such as child packages or
+            affected binary paths).
+          items:
+            example: linux-tools-common
+            type: string
+          type: array
         name:
           description: Vulnerability library name.
           example: linux-aws-5.15
@@ -30199,6 +30429,37 @@ components:
       type: string
       x-enum-varnames:
       - LIST_CONNECTIONS_RESPONSE
+    ListDeploymentRuleResponseData:
+      description: Data for a list of deployment rules.
+      properties:
+        attributes:
+          $ref: '#/components/schemas/ListDeploymentRulesResponseDataAttributes'
+        id:
+          description: Unique identifier of the deployment rule.
+          example: 1111-2222-3333-4444-555566667777
+          type: string
+        type:
+          $ref: '#/components/schemas/ListDeploymentRulesDataType'
+      required:
+      - type
+      - attributes
+      - id
+      type: object
+    ListDeploymentRulesDataType:
+      description: List deployment rule resource type.
+      enum:
+      - list_deployment_rules
+      example: list_deployment_rules
+      type: string
+      x-enum-varnames:
+      - LIST_DEPLOYMENT_RULES
+    ListDeploymentRulesResponseDataAttributes:
+      properties:
+        rules:
+          items:
+            $ref: '#/components/schemas/DeploymentRuleResponseDataAttributes'
+          type: array
+      type: object
     ListDevicesResponse:
       description: List devices response.
       properties:
@@ -30330,6 +30591,14 @@ components:
         meta:
           $ref: '#/components/schemas/KindResponseMeta'
       type: object
+    ListNotificationChannelsResponse:
+      description: Response type for listing notification channels for a user
+      properties:
+        data:
+          items:
+            $ref: '#/components/schemas/NotificationChannelData'
+          type: array
+      type: object
     ListPipelinesResponse:
       description: Represents the response payload containing a list of pipelines
         and associated metadata.
@@ -34504,6 +34773,174 @@ components:
       required:
       - notebookTrigger
       type: object
+    NotificationChannel:
+      description: A top-level wrapper for a user notification channel
+      example:
+        data:
+          attributes:
+            config:
+              address: foo@bar.com
+              formats:
+              - html
+              type: email
+          id: 27590dae-47be-4a7d-9abf-8f4e45124020
+          type: notification_channels
+      properties:
+        data:
+          $ref: '#/components/schemas/NotificationChannelData'
+      type: object
+    NotificationChannelAttributes:
+      description: Attributes for an on-call notification channel.
+      properties:
+        active:
+          description: Whether the notification channel is currently active.
+          type: boolean
+        config:
+          $ref: '#/components/schemas/NotificationChannelConfig'
+          description: Notification channel configuration
+      type: object
+    NotificationChannelConfig:
+      description: Defines the configuration for an On-Call notification channel
+      oneOf:
+      - $ref: '#/components/schemas/NotificationChannelPhoneConfig'
+      - $ref: '#/components/schemas/NotificationChannelEmailConfig'
+      - $ref: '#/components/schemas/NotificationChannelPushConfig'
+    NotificationChannelData:
+      description: Data for an on-call notification channel
+      properties:
+        attributes:
+          $ref: '#/components/schemas/NotificationChannelAttributes'
+        id:
+          description: Unique identifier for the channel
+          type: string
+        type:
+          $ref: '#/components/schemas/NotificationChannelType'
+      required:
+      - type
+      type: object
+    NotificationChannelEmailConfig:
+      description: Email notification channel configuration
+      properties:
+        address:
+          description: The e-mail address to be notified
+          example: ''
+          type: string
+        formats:
+          description: Preferred content formats for notifications.
+          example:
+          - html
+          items:
+            $ref: '#/components/schemas/NotificationChannelEmailFormatType'
+          type: array
+        type:
+          $ref: '#/components/schemas/NotificationChannelEmailConfigType'
+      required:
+      - type
+      - address
+      - formats
+      type: object
+    NotificationChannelEmailConfigType:
+      default: email
+      description: Indicates that the notification channel is an e-mail address
+      enum:
+      - email
+      example: email
+      type: string
+      x-enum-varnames:
+      - EMAIL
+    NotificationChannelEmailFormatType:
+      default: html
+      description: Specifies the format of the e-mail that is sent for On-Call notifications
+      enum:
+      - html
+      - text
+      example: html
+      type: string
+      x-enum-varnames:
+      - HTML
+      - TEXT
+    NotificationChannelPhoneConfig:
+      description: Phone notification channel configuration
+      properties:
+        formatted_number:
+          description: The formatted international version of Number (e.g. +33 7 1
+            23 45 67).
+          example: ''
+          type: string
+        number:
+          description: The E-164 formatted phone number (e.g. +3371234567)
+          example: ''
+          type: string
+        region:
+          description: The ISO 3166-1 alpha-2 two-letter country code.
+          example: ''
+          type: string
+        sms_subscribed_at:
+          description: If present, the date the user subscribed this number to SMS
+            messages
+          format: date-time
+          nullable: true
+          type: string
+        type:
+          $ref: '#/components/schemas/NotificationChannelPhoneConfigType'
+        verified:
+          description: Indicates whether this phone has been verified by the user
+            in Datadog On-Call
+          example: false
+          type: boolean
+      required:
+      - type
+      - number
+      - formatted_number
+      - region
+      - verified
+      type: object
+    NotificationChannelPhoneConfigType:
+      default: phone
+      description: Indicates that the notification channel is a phone
+      enum:
+      - phone
+      example: phone
+      type: string
+      x-enum-varnames:
+      - PHONE
+    NotificationChannelPushConfig:
+      description: Push notification channel configuration
+      properties:
+        application_name:
+          description: The name of the application used to receive push notifications
+          example: ''
+          type: string
+        device_name:
+          description: The name of the mobile device being used
+          example: ''
+          type: string
+        type:
+          $ref: '#/components/schemas/NotificationChannelPushConfigType'
+      required:
+      - type
+      - device_name
+      - application_name
+      type: object
+    NotificationChannelPushConfigType:
+      default: push
+      description: Indicates that the notification channel is a mobile device for
+        push notifications
+      enum:
+      - push
+      example: push
+      type: string
+      x-enum-varnames:
+      - PUSH
+    NotificationChannelType:
+      default: notification_channels
+      description: Indicates that the resource is of type 'notification_channels'.
+      enum:
+      - notification_channels
+      example: notification_channels
+      type: string
+      x-enum-varnames:
+      - NOTIFICATION_CHANNELS
     NotificationRule:
       description: 'Notification rules allow full control over notifications generated
         by the various Datadog security products.
@@ -34707,6 +35144,10 @@ components:
       description: The `add_env_vars` processor adds environment variable values to
         log events.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this processor in the pipeline.
@@ -34717,14 +35158,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the input for
-            this processor.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         type:
           $ref: '#/components/schemas/ObservabilityPipelineAddEnvVarsProcessorType'
         variables:
@@ -34736,8 +35169,8 @@ components:
       - id
       - type
       - include
-      - inputs
       - variables
+      - enabled
       type: object
     ObservabilityPipelineAddEnvVarsProcessorType:
       default: add_env_vars
@@ -34766,6 +35199,10 @@ components:
     ObservabilityPipelineAddFieldsProcessor:
       description: The `add_fields` processor adds static key-value fields to logs.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         fields:
           description: A list of static fields (key-value pairs) that is added to
             each log event processed by this component.
@@ -34783,14 +35220,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         type:
           $ref: '#/components/schemas/ObservabilityPipelineAddFieldsProcessorType'
       required:
@@ -34798,7 +35227,7 @@ components:
       - type
       - include
       - fields
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineAddFieldsProcessorType:
       default: add_fields
@@ -35101,15 +35530,25 @@ components:
             $ref: '#/components/schemas/ObservabilityPipelineConfigDestinationItem'
           type: array
         processors:
-          description: A list of processors that transform or enrich log data.
+          description: A list of processor groups that transform or enrich log data.
           example:
-          - id: filter-processor
+          - enabled: true
+            id: my-processor-group
             include: service:my-service
             inputs:
             - datadog-agent-source
-            type: filter
+            processors:
+            - enabled: true
+              id: filter-processor
+              include: status:error
+              type: filter
+            - enabled: true
+              field: message
+              id: json-processor
+              include: '*'
+              type: parse_json
           items:
-            $ref: '#/components/schemas/ObservabilityPipelineConfigProcessorItem'
+            $ref: '#/components/schemas/ObservabilityPipelineConfigProcessorGroup'
           type: array
         sources:
           description: A list of configured data sources for the pipeline.
@@ -35145,6 +35584,73 @@ components:
       - $ref: '#/components/schemas/ObservabilityPipelineAmazonSecurityLakeDestination'
       - $ref: '#/components/schemas/ObservabilityPipelineCrowdStrikeNextGenSiemDestination'
       - $ref: '#/components/schemas/ObservabilityPipelineGooglePubSubDestination'
+    ObservabilityPipelineConfigProcessorGroup:
+      description: A group of processors.
+      example:
+        enabled: true
+        id: my-processor-group
+        include: service:my-service
+        inputs:
+        - datadog-agent-source
+        processors:
+        - enabled: true
+          fields:
+          - name: env
+            value: prod
+          id: add-fields-processor
+          include: '*'
+          type: add_fields
+        - enabled: true
+          id: filter-processor
+          include: status:error
+          type: filter
+      properties:
+        enabled:
+          description: Whether this processor group is enabled.
+          example: true
+          type: boolean
+        id:
+          description: The unique identifier for the processor group.
+          example: grouped-processors
+          type: string
+        include:
+          description: Conditional expression for when this processor group should
+            execute.
+          example: service:my-service
+          type: string
+        inputs:
+          description: A list of IDs for components whose output is used as the input
+            for this processor group.
+          example:
+          - datadog-agent-source
+          items:
+            type: string
+          type: array
+        processors:
+          description: Processors applied sequentially within this group. Events flow
+            through each processor in order.
+          example:
+          - enabled: true
+            fields:
+            - name: env
+              value: prod
+            id: add-fields-processor
+            include: '*'
+            type: add_fields
+          - enabled: true
+            id: filter-processor
+            include: status:error
+            type: filter
+          items:
+            $ref: '#/components/schemas/ObservabilityPipelineConfigProcessorItem'
+          type: array
+      required:
+      - id
+      - include
+      - inputs
+      - processors
+      - enabled
+      type: object
     ObservabilityPipelineConfigProcessorItem:
       description: A processor for the pipeline.
       oneOf:
@@ -35262,6 +35768,10 @@ components:
         Remap Language (VRL)](https://vector.dev/docs/reference/vrl/) scripts with
         advanced filtering capabilities.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this processor.
           example: remap-vrl-processor
@@ -35273,14 +35783,6 @@ components:
             processor.
           example: '*'
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the input for
-            this processor.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         remaps:
           description: Array of VRL remap rules.
           items:
@@ -35294,7 +35796,7 @@ components:
       - type
       - include
       - remaps
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineCustomProcessorRemap:
       description: Defines a single VRL remap rule with its own filtering and transformation
@@ -35325,7 +35827,6 @@ components:
       - include
       - name
       - source
-      - enabled
       - drop_on_error
       type: object
     ObservabilityPipelineCustomProcessorType:
@@ -35434,6 +35935,10 @@ components:
       properties:
         action:
           $ref: '#/components/schemas/ObservabilityPipelineDatadogTagsProcessorAction'
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline (for example, as the `input`
@@ -35445,14 +35950,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         keys:
           description: A list of tag keys.
           example:
@@ -35473,7 +35970,7 @@ components:
       - mode
       - action
       - keys
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineDatadogTagsProcessorAction:
       description: The action to take on tags with matching keys.
@@ -35519,6 +36016,10 @@ components:
     ObservabilityPipelineDedupeProcessor:
       description: The `dedupe` processor removes duplicate fields in log events.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         fields:
           description: A list of log field paths to check for duplicates.
           example:
@@ -35536,14 +36037,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the input for
-            this processor.
-          example:
-          - parse-json-processor
-          items:
-            type: string
-          type: array
         mode:
           $ref: '#/components/schemas/ObservabilityPipelineDedupeProcessorMode'
         type:
@@ -35552,9 +36045,9 @@ components:
       - id
       - type
       - include
-      - inputs
       - fields
       - mode
+      - enabled
       type: object
     ObservabilityPipelineDedupeProcessorMode:
       description: The deduplication mode to apply to the fields.
@@ -35760,6 +36253,10 @@ components:
       description: The `enrichment_table` processor enriches logs using a static CSV
         file or GeoIP database.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         file:
           $ref: '#/components/schemas/ObservabilityPipelineEnrichmentTableFile'
         geoip:
@@ -35773,14 +36270,6 @@ components:
             targets.
           example: source:my-source
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the input for
-            this processor.
-          example:
-          - add-fields-processor
-          items:
-            type: string
-          type: array
         target:
           description: Path where enrichment results should be stored in the log.
           example: enriched.geoip
@@ -35791,8 +36280,8 @@ components:
       - id
       - type
       - include
-      - inputs
       - target
+      - enabled
       type: object
     ObservabilityPipelineEnrichmentTableProcessorType:
       default: enrichment_table
@@ -35823,6 +36312,10 @@ components:
         on a Datadog search query. Logs that match the `include` query are passed
         through; others are discarded.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline (for example, as the `input`
@@ -35835,21 +36328,13 @@ components:
             components; others are dropped.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         type:
           $ref: '#/components/schemas/ObservabilityPipelineFilterProcessorType'
       required:
       - id
       - type
       - include
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineFilterProcessorType:
       default: filter
@@ -35929,6 +36414,10 @@ components:
         Metrics can be counters, gauges, or distributions and optionally grouped by
         log fields.'
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline.
@@ -35939,14 +36428,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this processor.
-          example:
-          - source-id
-          items:
-            type: string
-          type: array
         metrics:
           description: Configuration for generating individual metrics.
           items:
@@ -35957,9 +36438,7 @@ components:
       required:
       - id
       - type
-      - inputs
-      - include
-      - metrics
+      - enabled
       type: object
     ObservabilityPipelineGenerateMetricsProcessorType:
       default: generate_datadog_metrics
@@ -36556,6 +37035,10 @@ components:
       description: The `ocsf_mapper` processor transforms logs into the OCSF schema
         using a predefined mapping configuration.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline.
@@ -36566,14 +37049,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this processor.
-          example:
-          - filter-processor
-          items:
-            type: string
-          type: array
         mappings:
           description: A list of mapping rules to convert events to the OCSF format.
           items:
@@ -36585,8 +37060,8 @@ components:
       - id
       - type
       - include
-      - inputs
       - mappings
+      - enabled
       type: object
     ObservabilityPipelineOcsfMapperProcessorMapping:
       description: Defines how specific events are transformed to OCSF using a mapping
@@ -36691,6 +37166,10 @@ components:
             by Datadog.
           example: true
           type: boolean
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: A unique identifier for this processor.
           example: parse-grok-processor
@@ -36700,14 +37179,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         rules:
           description: The list of Grok parsing rules. If multiple matching rules
             are provided, they are evaluated in order. The first successful match
@@ -36721,8 +37192,8 @@ components:
       - id
       - type
       - include
-      - inputs
       - rules
+      - enabled
       type: object
     ObservabilityPipelineParseGrokProcessorRule:
       description: 'A Grok parsing rule used in the `parse_grok` processor. Each rule
@@ -36807,6 +37278,10 @@ components:
         and flattens it into the event. This is useful when logs contain embedded
         JSON as a string.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         field:
           description: The name of the log field that contains a JSON string.
           example: message
@@ -36822,14 +37297,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         type:
           $ref: '#/components/schemas/ObservabilityPipelineParseJSONProcessorType'
       required:
@@ -36837,7 +37304,7 @@ components:
       - type
       - include
       - field
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineParseJSONProcessorType:
       default: parse_json
@@ -36870,6 +37337,10 @@ components:
             the filter query continue through the pipeline.
           example: false
           type: boolean
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline (for example, as the `input`
@@ -36885,14 +37356,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         limit:
           $ref: '#/components/schemas/ObservabilityPipelineQuotaProcessorLimit'
         name:
@@ -36922,9 +37385,8 @@ components:
       - type
       - include
       - name
-      - drop_events
       - limit
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineQuotaProcessorLimit:
       description: The maximum amount of data or number of events allowed before the
@@ -37000,6 +37462,10 @@ components:
       description: The `reduce` processor aggregates and merges logs based on matching
         keys and merge strategies.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         group_by:
           description: A list of fields used to group log events for merging.
           example:
@@ -37017,14 +37483,6 @@ components:
             targets.
           example: env:prod
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the input for
-            this processor.
-          example:
-          - parse-json-processor
-          items:
-            type: string
-          type: array
         merge_strategies:
           description: List of merge strategies defining how values from grouped events
             should be combined.
@@ -37037,9 +37495,9 @@ components:
       - id
       - type
       - include
-      - inputs
       - group_by
       - merge_strategies
+      - enabled
       type: object
     ObservabilityPipelineReduceProcessorMergeStrategy:
       description: Defines how a specific field should be merged across grouped events.
@@ -37096,6 +37554,10 @@ components:
     ObservabilityPipelineRemoveFieldsProcessor:
       description: The `remove_fields` processor deletes specified fields from logs.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         fields:
           description: A list of field names to be removed from each log event.
           example:
@@ -37115,13 +37577,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: The `PipelineRemoveFieldsProcessor` `inputs`.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         type:
           $ref: '#/components/schemas/ObservabilityPipelineRemoveFieldsProcessorType'
       required:
@@ -37129,7 +37584,7 @@ components:
       - type
       - include
       - fields
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineRemoveFieldsProcessorType:
       default: remove_fields
@@ -37143,6 +37598,10 @@ components:
     ObservabilityPipelineRenameFieldsProcessor:
       description: The `rename_fields` processor changes field names.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         fields:
           description: A list of rename rules specifying which fields to rename in
             the event, what to rename them to, and whether to preserve the original
@@ -37161,14 +37620,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         type:
           $ref: '#/components/schemas/ObservabilityPipelineRenameFieldsProcessorType'
       required:
@@ -37176,7 +37627,7 @@ components:
       - type
       - include
       - fields
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineRenameFieldsProcessorField:
       description: Defines how to rename a field in log events.
@@ -37282,6 +37733,10 @@ components:
       description: The `sample` processor allows probabilistic sampling of logs at
         a fixed rate.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline (for example, as the `input`
@@ -37293,14 +37748,6 @@ components:
             targets.
           example: service:my-service
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         percentage:
           description: The percentage of logs to sample.
           example: 10.0
@@ -37318,7 +37765,7 @@ components:
       - id
       - type
       - include
-      - inputs
+      - enabled
       type: object
     ObservabilityPipelineSampleProcessorType:
       default: sample
@@ -37333,6 +37780,10 @@ components:
       description: The `sensitive_data_scanner` processor detects and optionally redacts
         sensitive data in log events.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         id:
           description: The unique identifier for this component. Used to reference
             this component in other parts of the pipeline (e.g., as input to downstream
@@ -37344,14 +37795,6 @@ components:
             targets.
           example: source:prod
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the `input`
-            for this component.
-          example:
-          - parse-json-processor
-          items:
-            type: string
-          type: array
         rules:
           description: A list of rules for identifying and acting on sensitive data
             patterns.
@@ -37364,8 +37807,8 @@ components:
       - id
       - type
       - include
-      - inputs
       - rules
+      - enabled
       type: object
     ObservabilityPipelineSensitiveDataScannerProcessorAction:
       description: Defines what action to take when sensitive data is matched.
@@ -38326,6 +38769,10 @@ components:
       description: The `throttle` processor limits the number of events that pass
         through over a given time window.
       properties:
+        enabled:
+          description: Whether this processor is enabled.
+          example: true
+          type: boolean
         group_by:
           description: Optional list of fields used to group events before the threshold
             has been reached.
@@ -38343,14 +38790,6 @@ components:
             targets.
           example: env:prod
           type: string
-        inputs:
-          description: A list of component IDs whose output is used as the input for
-            this processor.
-          example:
-          - datadog-agent-source
-          items:
-            type: string
-          type: array
         threshold:
           description: the number of events allowed in a given time window. Events
             sent after the threshold has been reached, are dropped.
@@ -38368,9 +38807,9 @@ components:
       - id
       - type
       - include
-      - inputs
       - threshold
       - window
+      - enabled
       type: object
     ObservabilityPipelineThrottleProcessorType:
       default: throttle
@@ -44089,38 +44528,13 @@ components:
           description: The `RuleVersionHistory` `data`.
           type: object
       type: object
-    RuleVersionUpdate:
-      description: A change in a rule version.
-      properties:
-        change:
-          description: The new value of the field.
-          example: cloud_provider:aws
-          type: string
-        field:
-          description: The field that was changed.
-          example: Tags
-          type: string
-        type:
-          $ref: '#/components/schemas/RuleVersionUpdateType'
-      type: object
-    RuleVersionUpdateType:
-      description: The type of change.
-      enum:
-      - create
-      - update
-      - delete
-      type: string
-      x-enum-varnames:
-      - CREATE
-      - UPDATE
-      - DELETE
     RuleVersions:
       description: A rule version with a list of updates.
       properties:
         changes:
           description: A list of changes.
           items:
-            $ref: '#/components/schemas/RuleVersionUpdate'
+            $ref: '#/components/schemas/VersionHistoryUpdate'
           type: array
         rule:
           $ref: '#/components/schemas/SecurityMonitoringRuleResponse'
@@ -47194,6 +47608,8 @@ components:
       properties:
         forgetAfter:
           $ref: '#/components/schemas/SecurityMonitoringRuleNewValueOptionsForgetAfter'
+        instantaneousBaseline:
+          $ref: '#/components/schemas/SecurityMonitoringRuleNewValueOptionsInstantaneousBaseline'
         learningDuration:
           $ref: '#/components/schemas/SecurityMonitoringRuleNewValueOptionsLearningDuration'
         learningMethod:
@@ -47219,6 +47635,13 @@ components:
       - TWO_WEEKS
       - THREE_WEEKS
       - FOUR_WEEKS
+    SecurityMonitoringRuleNewValueOptionsInstantaneousBaseline:
+      description: When set to true, Datadog uses previous values that fall within
+        the defined learning window to construct the baseline, enabling the system
+        to establish an accurate baseline more rapidly rather than relying solely
+        on gradual learning over time.
+      example: false
+      type: boolean
     SecurityMonitoringRuleNewValueOptionsLearningDuration:
       default: 0
       description: 'The duration in days during which values are learned, and after
@@ -50937,6 +51360,49 @@ components:
             $ref: '#/components/schemas/ServiceDefinitionData'
           type: array
       type: object
+    ServiceList:
+      properties:
+        data:
+          $ref: '#/components/schemas/ServiceListData'
+      type: object
+    ServiceListData:
+      properties:
+        attributes:
+          $ref: '#/components/schemas/ServiceListDataAttributes'
+        id:
+          type: string
+        type:
+          $ref: '#/components/schemas/ServiceListDataType'
+      required:
+      - type
+      type: object
+    ServiceListDataAttributes:
+      properties:
+        metadata:
+          items:
+            $ref: '#/components/schemas/ServiceListDataAttributesMetadataItems'
+          type: array
+        services:
+          items:
+            type: string
+          type: array
+      type: object
+    ServiceListDataAttributesMetadataItems:
+      properties:
+        isTraced:
+          type: boolean
+        isUsm:
+          type: boolean
+      type: object
+    ServiceListDataType:
+      default: services_list
+      description: Services list resource type.
+      enum:
+      - services_list
+      example: services_list
+      type: string
+      x-enum-varnames:
+      - SERVICES_LIST
     ServiceNowBasicAuth:
       description: The definition of the `ServiceNowBasicAuth` object.
       properties:
@@ -52680,6 +53146,32 @@ components:
           format: double
           type: number
       type: object
+    SuppressionVersionHistory:
+      description: Response object containing the version history of a suppression.
+      properties:
+        count:
+          description: The number of suppression versions.
+          format: int32
+          maximum: 2147483647
+          type: integer
+        data:
+          additionalProperties:
+            $ref: '#/components/schemas/SuppressionVersions'
+            description: A suppression version with a list of updates.
+          description: The version history of a suppression.
+          type: object
+      type: object
+    SuppressionVersions:
+      description: A suppression version with a list of updates.
+      properties:
+        changes:
+          description: A list of changes.
+          items:
+            $ref: '#/components/schemas/VersionHistoryUpdate'
+          type: array
+        suppression:
+          $ref: '#/components/schemas/SecurityMonitoringSuppressionAttributes'
+      type: object
     TableResultV2:
       description: A reference table resource containing its full configuration and
         state.
@@ -57010,6 +57502,31 @@ components:
       example: 1
       format: int64
       type: integer
+    VersionHistoryUpdate:
+      description: A change in a rule version.
+      properties:
+        change:
+          description: The new value of the field.
+          example: cloud_provider:aws
+          type: string
+        field:
+          description: The field that was changed.
+          example: Tags
+          type: string
+        type:
+          $ref: '#/components/schemas/VersionHistoryUpdateType'
+      type: object
+    VersionHistoryUpdateType:
+      description: The type of change.
+      enum:
+      - create
+      - update
+      - delete
+      type: string
+      x-enum-varnames:
+      - CREATE
+      - UPDATE
+      - DELETE
     VirusTotalAPIKey:
       description: The definition of the `VirusTotalAPIKey` object.
       properties:
@@ -57207,6 +57724,12 @@ components:
           type: array
         risks:
           $ref: '#/components/schemas/VulnerabilityRisks'
+        running_kernel:
+          description: "True if the vulnerability affects a package in the host\u2019s
+            running kernel, false if it affects a non-running kernel, and omit if
+            it is not kernel-related."
+          example: true
+          type: boolean
         status:
           $ref: '#/components/schemas/VulnerabilityStatus'
         title:
@@ -57267,10 +57790,15 @@ components:
       - RubyGems
       - Go
       - Packagist
-      - Ddeb
+      - Deb
       - Rpm
       - Apk
       - Windows
+      - Generic
+      - MacOs
+      - Oci
+      - BottleRocket
+      - None
       type: string
       x-enum-varnames:
       - PYPI
@@ -57280,10 +57808,15 @@ components:
       - RUBY_GEMS
       - GO
       - PACKAGIST
-      - D_DEB
+      - DEB
       - RPM
       - APK
       - WINDOWS
+      - GENERIC
+      - MAC_OS
+      - OCI
+      - BOTTLE_ROCKET
+      - NONE
     VulnerabilityRelationships:
       description: Related entities object.
       properties:
@@ -57384,12 +57917,14 @@ components:
       - IAST
       - SCA
       - Infra
+      - SAST
       example: SCA
       type: string
       x-enum-varnames:
       - IAST
       - SCA
       - INFRA
+      - SAST
     VulnerabilityType:
       description: The vulnerability type.
       enum:
@@ -61130,6 +61665,26 @@ paths:
         permissions:
         - apm_retention_filter_write
         - apm_pipelines_write
+  /api/v2/apm/services:
+    get:
+      operationId: GetServiceList
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ServiceList'
+          description: OK
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ:
+        - apm_read
+      summary: Get service list
+      tags:
+      - APM
   /api/v2/app-builder/apps:
     delete:
       description: Delete multiple apps in a single request from a list of app IDs.
@@ -66236,6 +66791,50 @@ paths:
 
         If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/deployment_gates/{gate_id}/rules:
+    get:
+      description: Endpoint to get rules for a deployment gate.
+      operationId: GetDeploymentGateRules
+      parameters:
+      - description: The ID of the deployment gate.
+        in: path
+        name: gate_id
+        required: true
+        schema:
+          type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/DeploymentGateRulesResponse'
+          description: OK
+        '400':
+          $ref: '#/components/responses/HTTPCDGatesBadRequestResponse'
+        '401':
+          $ref: '#/components/responses/UnauthorizedResponse'
+        '403':
+          $ref: '#/components/responses/ForbiddenResponse'
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+        '500':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HTTPCIAppErrors'
+          description: Internal Server Error
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      summary: Get rules for a deployment gate
+      tags:
+      - Deployment Gates
+      x-permission:
+        operator: OR
+        permissions:
+        - deployment_gates_read
+      x-unstable: '**Note**: This endpoint is in preview and may be subject to change.
+
+        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
     post:
       description: Endpoint to create a deployment rule. A gate for the rule must
         already exist.
@@ -66790,6 +67389,24 @@ paths:
         '200':
           content:
             application/json:
+              example:
+                data:
+                  attributes:
+                    custom_tags:
+                    - language:java
+                    - department:engineering
+                    - region:us-east-1
+                    env: staging
+                    finished_at: 1693491984000000000
+                    git:
+                      commit_sha: 66adc9350f2cc9b250b69abddab733dd55e1a588
+                      repository_url: https://github.com/organization/example-repository
+                    service: shopist
+                    started_at: 1693491974000000000
+                    team: backend
+                    version: v1.12.07
+                  id: 4242fcdd31586083
+                  type: dora_deployment
               schema:
                 $ref: '#/components/schemas/DORAFetchResponse'
           description: OK
@@ -66908,6 +67525,64 @@ paths:
         '200':
           content:
             application/json:
+              example:
+                data:
+                - attributes:
+                    custom_tags:
+                    - language:java
+                    - department:engineering
+                    - region:us-east-1
+                    env: production
+                    finished_at: 1693491984000000000
+                    git:
+                      commit_sha: 66adc9350f2cc9b250b69abddab733dd55e1a588
+                      repository_url: https://github.com/organization/example-repository
+                    name: Web server is down; all requests are failing.
+                    services:
+                    - shopist
+                    severity: SEV-1
+                    started_at: 1693491974000000000
+                    team: backend
+                  id: 4242fcdd31586085
+                  type: dora_failure
+                - attributes:
+                    custom_tags:
+                    - language:go
+                    - department:platform
+                    env: production
+                    finished_at: 1693492084000000000
+                    git:
+                      commit_sha: 77bdc9350f2cc9b250b69abddab733dd55e1a599
+                      repository_url: https://github.com/organization/api-service
+                    name: Database connection timeout
+                    services:
+                    - api-service
+                    - payment-service
+                    severity: SEV-1
+                    started_at: 1693492074000000000
+                    team: platform
+                    version: v2.1.0
+                  id: 4242fcdd31586086
+                  type: dora_failure
+                - attributes:
+                    custom_tags:
+                    - language:python
+                    - department:payments
+                    - region:eu-west-1
+                    env: staging
+                    finished_at: 1693492204000000000
+                    git:
+                      commit_sha: 99edc9350f2cc9b250b69abddab733dd55e1a601
+                      repository_url: https://github.com/organization/payment-service
+                    name: Payment gateway API rate limit exceeded
+                    services:
+                    - payment-service
+                    severity: SEV-2
+                    started_at: 1693492174000000000
+                    team: payments
+                    version: v1.8.3
+                  id: 4242fcdd31586087
+                  type: dora_failure
               schema:
                 $ref: '#/components/schemas/DORAListResponse'
           description: OK
@@ -66947,6 +67622,26 @@ paths:
         '200':
           content:
             application/json:
+              example:
+                data:
+                  attributes:
+                    custom_tags:
+                    - language:java
+                    - department:engineering
+                    - region:us-east-1
+                    env: staging
+                    finished_at: 1693491984000000000
+                    git:
+                      commit_sha: 66adc9350f2cc9b250b69abddab733dd55e1a588
+                      repository_url: https://github.com/organization/example-repository
+                    name: Web server is down; all requests are failing.
+                    services:
+                    - shopist
+                    severity: High
+                    started_at: 1693491974000000000
+                    team: backend
+                  id: 4242fcdd31586085
+                  type: dora_failure
               schema:
                 $ref: '#/components/schemas/DORAFetchResponse'
           description: OK
@@ -67608,6 +68303,7 @@ paths:
                           rule:
                             datacenter: devcycle.us1.prod
                       category: change
+                      host: hostname
                       integration_id: custom-events
                       message: payment_processed feature flag has been enabled
                       tags:
@@ -67654,6 +68350,7 @@ paths:
             - us3.datadoghq.com
             - us5.datadoghq.com
             - ap1.datadoghq.com
+            - ap2.datadoghq.com
             - datadoghq.eu
             - ddog-gov.com
           subdomain:
@@ -68721,9 +69418,6 @@ paths:
         operator: OR
         permissions:
         - incident_read
-      x-unstable: '**Note**: This endpoint is in Preview.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
     post:
       description: Create an impact for an incident.
       operationId: CreateIncidentImpact
@@ -68767,9 +69461,6 @@ paths:
         operator: OR
         permissions:
         - incident_write
-      x-unstable: '**Note**: This endpoint is in Preview.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/incidents/{incident_id}/impacts/{impact_id}:
     delete:
       description: Delete an incident impact.
@@ -68800,9 +69491,6 @@ paths:
         operator: OR
         permissions:
         - incident_write
-      x-unstable: '**Note**: This endpoint is in Preview.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/incidents/{incident_id}/relationships/integrations:
     get:
       description: Get all integration metadata for an incident.
@@ -75378,6 +76066,184 @@ paths:
         operator: AND
         permissions:
         - on_call_write
+  /api/v2/on-call/users/{user_id}/notification-channels:
+    get:
+      description: List the notification channels for a user. The authenticated user
+        must be the target user or have the `on_call_admin` permission
+      operationId: ListUserNotificationChannels
+      parameters:
+      - description: The user ID
+        in: path
+        name: user_id
+        required: true
+        schema:
+          example: 00000000-0000-0000-0000-000000000000
+          type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ListNotificationChannelsResponse'
+          description: OK
+        '400':
+          $ref: '#/components/responses/BadRequestResponse'
+        '401':
+          $ref: '#/components/responses/UnauthorizedResponse'
+        '403':
+          $ref: '#/components/responses/ForbiddenResponse'
+        '404':
+          $ref: '#/components/responses/NotFoundResponse'
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      summary: List On-Call notification channels for a user
+      tags:
+      - On-Call
+      x-permission:
+        operator: AND
+        permissions:
+        - on_call_read
+    post:
+      description: Create a new notification channel for a user. The authenticated
+        user must be the target user or have the `on_call_admin` permission
+      operationId: CreateUserNotificationChannel
+      parameters:
+      - description: The user ID
+        in: path
+        name: user_id
+        required: true
+        schema:
+          example: 00000000-0000-0000-0000-000000000000
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CreateUserNotificationChannelRequest'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationChannel'
+          description: Created
+        '400':
+          $ref: '#/components/responses/BadRequestResponse'
+        '401':
+          $ref: '#/components/responses/UnauthorizedResponse'
+        '403':
+          $ref: '#/components/responses/ForbiddenResponse'
+        '404':
+          $ref: '#/components/responses/NotFoundResponse'
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      summary: Create an On-Call notification channel for a user
+      tags:
+      - On-Call
+      x-permission:
+        operator: AND
+        permissions:
+        - on_call_respond
+  /api/v2/on-call/users/{user_id}/notification-channels/{channel_id}:
+    delete:
+      description: Delete a notification channel for a user. The authenticated user
+        must be the target user or have the `on_call_admin` permission
+      operationId: DeleteUserNotificationChannel
+      parameters:
+      - description: The user ID
+        in: path
+        name: user_id
+        required: true
+        schema:
+          example: 00000000-0000-0000-0000-000000000000
+          type: string
+      - description: The channel ID
+        in: path
+        name: channel_id
+        required: true
+        schema:
+          example: 00000000-0000-0000-0000-000000000000
+          type: string
+      responses:
+        '204':
+          description: No Content
+        '400':
+          $ref: '#/components/responses/BadRequestResponse'
+        '401':
+          $ref: '#/components/responses/UnauthorizedResponse'
+        '403':
+          $ref: '#/components/responses/ForbiddenResponse'
+        '404':
+          $ref: '#/components/responses/NotFoundResponse'
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      summary: Delete an On-Call notification channel for a user
+      tags:
+      - On-Call
+      x-permission:
+        operator: AND
+        permissions:
+        - on_call_respond
+    get:
+      description: Get a notification channel for a user. The authenticated user must
+        be the target user or have the `on_call_admin` permission
+      operationId: GetUserNotificationChannel
+      parameters:
+      - description: The user ID
+        in: path
+        name: user_id
+        required: true
+        schema:
+          example: 00000000-0000-0000-0000-000000000000
+          type: string
+      - description: The channel ID
+        in: path
+        name: channel_id
+        required: true
+        schema:
+          example: 00000000-0000-0000-0000-000000000000
+          type: string
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NotificationChannel'
+          description: OK
+        '400':
+          $ref: '#/components/responses/BadRequestResponse'
+        '401':
+          $ref: '#/components/responses/UnauthorizedResponse'
+        '403':
+          $ref: '#/components/responses/ForbiddenResponse'
+        '404':
+          $ref: '#/components/responses/NotFoundResponse'
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      summary: Get an On-Call notification channel for a user
+      tags:
+      - On-Call
+      x-permission:
+        operator: AND
+        permissions:
+        - on_call_read
   /api/v2/org_configs:
     get:
       description: Returns all Org Configs (name, description, and value).
@@ -79678,11 +80544,13 @@ paths:
         - security_monitoring_cws_agent_rules_read
   /api/v2/security/findings/cases:
     delete:
-      description: Detach security findings from their case. This operation dissociates
-        security findings from their associated cases without deleting the cases themselves.
-        You can detach security findings from multiple different cases in a single
-        request, with a limit of 50 security findings per request. Security findings
-        that are not currently attached to any case will be ignored.
+      description: 'Detach security findings from their case.
+
+        This operation dissociates security findings from their associated cases without
+        deleting the cases themselves. You can detach security findings from multiple
+        different cases in a single request, with a limit of 50 security findings
+        per request. Security findings that are not currently attached to any case
+        will be ignored.'
       operationId: DetachCase
       requestBody:
         content:
@@ -79713,10 +80581,12 @@ paths:
         - security_monitoring_findings_write
         - appsec_vm_write
     post:
-      description: Create cases for security findings. You can create up to 50 cases
-        per request and associate up to 50 security findings per case. Security findings
-        that are already attached to another case will be detached from their previous
-        case and attached to the newly created case.
+      description: 'Create cases for security findings.
+
+        You can create up to 50 cases per request and associate up to 50 security
+        findings per case. Security findings that are already attached to another
+        case will be detached from their previous case and attached to the newly created
+        case.'
       operationId: CreateCases
       requestBody:
         content:
@@ -79752,14 +80622,14 @@ paths:
         - appsec_vm_write
   /api/v2/security/findings/cases/{case_id}:
     patch:
-      description: Attach security findings to a case. You can attach up to 50 security
-        findings per case. Security findings that are already attached to another
-        case will be detached from their previous case and attached to the specified
-        case.
+      description: 'Attach security findings to a case.
+
+        You can attach up to 50 security findings per case. Security findings that
+        are already attached to another case will be detached from their previous
+        case and attached to the specified case.'
       operationId: AttachCase
       parameters:
-      - description: The unique identifier of the case to attach security findings
-          to
+      - description: Unique identifier of the case to attach security findings to
         in: path
         name: case_id
         required: true
@@ -79799,12 +80669,16 @@ paths:
         - appsec_vm_write
   /api/v2/security/findings/jira_issues:
     patch:
-      description: Attach security findings to a Jira issue by providing the Jira
-        issue URL. You can attach up to 50 security findings per Jira issue. If the
-        Jira issue is not linked to any case, this operation will create a case for
-        the security findings and link the Jira issue to the newly created case. Security
-        findings that are already attached to another Jira issue will be detached
-        from their previous Jira issue and attached to the specified Jira issue.
+      description: 'Attach security findings to a Jira issue by providing the Jira
+        issue URL.
+
+        You can attach up to 50 security findings per Jira issue. If the Jira issue
+        is not linked to any case, this operation will create a case for the security
+        findings and link the Jira issue to the newly created case. To configure the
+        Jira integration, see [Bidirectional ticket syncing with Jira](https://docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira).
+        Security findings that are already attached to another Jira issue will be
+        detached from their previous Jira issue and attached to the specified Jira
+        issue.'
       operationId: AttachJiraIssue
       requestBody:
         content:
@@ -79838,13 +80712,19 @@ paths:
         permissions:
         - security_monitoring_findings_write
         - appsec_vm_write
+      x-unstable: '**Note**: This endpoint is in beta and is subject to change.
+
+        Please check the documentation regularly for updates.'
     post:
-      description: Create Jira issues for security findings. This operation creates
-        a case in Datadog and a Jira issue linked to that case for bidirectional sync
-        between Datadog and Jira. You can create up to 50 Jira issues per request
-        and associate up to 50 security findings per Jira issue. Security findings
-        that are already attached to another Jira issue will be detached from their
-        previous Jira issue and attached to the newly created Jira issue.
+      description: 'Create Jira issues for security findings.
+
+        This operation creates a case in Datadog and a Jira issue linked to that case
+        for bidirectional sync between Datadog and Jira. To configure the Jira integration,
+        see [Bidirectional ticket syncing with Jira](https://docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira).
+        You can create up to 50 Jira issues per request and associate up to 50 security
+        findings per Jira issue. Security findings that are already attached to another
+        Jira issue will be detached from their previous Jira issue and attached to
+        the newly created Jira issue.'
       operationId: CreateJiraIssues
       requestBody:
         content:
@@ -79878,6 +80758,9 @@ paths:
         permissions:
         - security_monitoring_findings_write
         - appsec_vm_write
+      x-unstable: '**Note**: This endpoint is in beta and is subject to change.
+
+        Please check the documentation regularly for updates.'
   /api/v2/security/sboms:
     get:
       description: 'Get a list of assets SBOMs for an organization.
@@ -80000,6 +80883,10 @@ paths:
       summary: List assets SBOMs
       tags:
       - Security Monitoring
+      x-permission:
+        operator: OR
+        permissions:
+        - appsec_vm_read
       x-unstable: '**Note**: This endpoint is a private preview.
 
         If you are interested in accessing this API, [fill out this form](https://forms.gle/kMYC1sDr6WDUBDsx9).'
@@ -80071,6 +80958,10 @@ paths:
       summary: Get SBOM
       tags:
       - Security Monitoring
+      x-permission:
+        operator: OR
+        permissions:
+        - appsec_vm_read
       x-unstable: '**Note**: This endpoint is a private preview.
 
         If you are interested in accessing this API, [fill out this form](https://forms.gle/kMYC1sDr6WDUBDsx9).'
@@ -80185,6 +81076,10 @@ paths:
       summary: List scanned assets metadata
       tags:
       - Security Monitoring
+      x-permission:
+        operator: OR
+        permissions:
+        - appsec_vm_read
       x-unstable: '**Note**: This endpoint is a private preview.
 
         If you are interested in accessing this API, [fill out this form](https://forms.gle/kMYC1sDr6WDUBDsx9).'
@@ -80613,6 +81508,14 @@ paths:
         required: false
         schema:
           type: string
+      - description: Filter for whether the vulnerability affects a running kernel
+          (for vulnerabilities related to a `Host` asset).
+        example: true
+        in: query
+        name: filter[running_kernel]
+        required: false
+        schema:
+          type: boolean
       - description: Filter by asset name. This field supports the usage of wildcards
           (*).
         example: datadog-agent
@@ -80756,6 +81659,10 @@ paths:
       summary: List vulnerabilities
       tags:
       - Security Monitoring
+      x-permission:
+        operator: OR
+        permissions:
+        - appsec_vm_read
       x-unstable: '**Note**: This endpoint is a private preview.
 
         If you are interested in accessing this API, [fill out this form](https://forms.gle/kMYC1sDr6WDUBDsx9).'
@@ -81114,6 +82021,10 @@ paths:
       summary: List vulnerable assets
       tags:
       - Security Monitoring
+      x-permission:
+        operator: OR
+        permissions:
+        - appsec_vm_read
       x-unstable: '**Note**: This endpoint is a private preview.
 
         If you are interested in accessing this API, [fill out this form](https://forms.gle/kMYC1sDr6WDUBDsx9).'
@@ -81690,6 +82601,35 @@ paths:
       summary: Update a suppression rule
       tags:
       - Security Monitoring
+  /api/v2/security_monitoring/configuration/suppressions/{suppression_id}/version_history:
+    get:
+      description: Get a suppression's version history.
+      operationId: GetSuppressionVersionHistory
+      parameters:
+      - $ref: '#/components/parameters/SecurityMonitoringSuppressionID'
+      - $ref: '#/components/parameters/PageSize'
+      - $ref: '#/components/parameters/PageNumber'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GetSuppressionVersionHistoryResponse'
+          description: OK
+        '403':
+          $ref: '#/components/responses/NotAuthorizedResponse'
+        '404':
+          $ref: '#/components/responses/NotFoundResponse'
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ:
+        - security_monitoring_suppressions_read
+      summary: Get a suppression's version history
+      tags:
+      - Security Monitoring
   /api/v2/security_monitoring/rules:
     get:
       description: List rules.
@@ -84251,8 +85191,8 @@ paths:
       x-unstable: '**Note**: This endpoint may be subject to changes.'
   /api/v2/static-analysis/secrets/rules:
     get:
-      description: Returns list of Secrets rules with ID, Pattern, Description, Priority,
-        and SDS ID
+      description: Returns a list of Secrets rules with ID, Pattern, Description,
+        Priority, and SDS ID.
       operationId: GetSecretsRules
       responses:
         '200':
@@ -84268,7 +85208,7 @@ paths:
         appKeyAuth: []
       - AuthZ:
         - code_analysis_read
-      summary: Returns list of Secrets rules
+      summary: Returns a list of Secrets rules
       tags:
       - Security Monitoring
       x-unstable: '**Note**: This endpoint may be subject to changes.'
@@ -85658,7 +86598,13 @@ paths:
         permissions:
         - teams_read
     post:
-      description: Add a user to a team.
+      description: 'Add a user to a team.
+
+
+        **Note**: Each team has a setting that determines who is allowed to modify
+        membership of the team. The `user_access_manage` permission generally grants
+        access to modify membership of any team. To get the full picture, see [Team
+        Membership documentation](https://docs.datadoghq.com/account_management/teams/manage/#team-membership).'
       operationId: CreateTeamMembership
       parameters:
       - description: None
@@ -85711,7 +86657,13 @@ paths:
         - teams_read
   /api/v2/team/{team_id}/memberships/{user_id}:
     delete:
-      description: Remove a user from a team.
+      description: 'Remove a user from a team.
+
+
+        **Note**: Each team has a setting that determines who is allowed to modify
+        membership of the team. The `user_access_manage` permission generally grants
+        access to modify membership of any team. To get the full picture, see [Team
+        Membership documentation](https://docs.datadoghq.com/account_management/teams/manage/#team-membership).'
       operationId: DeleteTeamMembership
       parameters:
       - description: None
@@ -85752,7 +86704,13 @@ paths:
         permissions:
         - teams_read
     patch:
-      description: Update a user's membership attributes on a team.
+      description: 'Update a user''s membership attributes on a team.
+
+
+        **Note**: Each team has a setting that determines who is allowed to modify
+        membership of the team. The `user_access_manage` permission generally grants
+        access to modify membership of any team. To get the full picture, see [Team
+        Membership documentation](https://docs.datadoghq.com/account_management/teams/manage/#team-membership).'
       operationId: UpdateTeamMembership
       parameters:
       - description: None
@@ -87703,6 +88661,9 @@ servers:
 tags:
 - description: Configure your API endpoints through the Datadog API.
   name: API Management
+- description: Observe, troubleshoot, and improve cloud-scale applications with all
+    telemetry in context
+  name: APM
 - description: Manage configuration of [APM retention filters](https://app.datadoghq.com/apm/traces/retention-filters)
     for your organization. You need an API and application key with Admin rights to
     interact with this endpoint. See [retention filters](https://docs.datadoghq.com/tracing/trace_pipeline/trace_retention/#retention-filters)