ConnectionMaster · pull · Jun 4, 2026 · Jun 4, 2026 · Jun 4, 2026
diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml
@@ -13177,13 +13177,16 @@ components:
       type: object
     SLOCorrectionCreateRequest:
       description: |-
-        An object that defines a correction to be applied to an SLO.
+        An object that defines a correction to be applied to one or more SLOs.
       properties:
         data:
           $ref: "#/components/schemas/SLOCorrectionCreateData"
       type: object
     SLOCorrectionCreateRequestAttributes:
-      description: The attribute object associated with the SLO correction to be created.
+      description: |-
+        The attribute object associated with the SLO correction to be created.
+
+        Exactly one of `slo_id` or `slo_query` must be provided.
       properties:
         category:
           $ref: "#/components/schemas/SLOCorrectionCategory"
@@ -13207,9 +13210,16 @@ components:
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           type: string
         slo_id:
-          description: ID of the SLO that this correction applies to.
+          description: ID of the single SLO that this correction applies to.
           example: sloId
           type: string
+        slo_query:
+          description: |-
+            Query that matches the SLOs this correction applies to.
+            The query uses the [Events search syntax](https://docs.datadoghq.com/events/explorer/searching/)
+            and can filter SLOs by SLO tags.
+          example: "env:prod service:checkout"
+          type: string
         start:
           description: Starting time of the correction in epoch seconds.
           example: 1600000000
@@ -13220,7 +13230,6 @@ components:
           example: UTC
           type: string
       required:
-        - slo_id
         - start
         - category
       type: object
@@ -13284,7 +13293,12 @@ components:
           nullable: true
           type: string
         slo_id:
-          description: ID of the SLO that this correction applies to.
+          description: ID of the single SLO that this correction applies to.
+          nullable: true
+          type: string
+        slo_query:
+          description: Query that matches the SLOs this correction applies to.
+          nullable: true
           type: string
         start:
           description: Starting time of the correction in epoch seconds.
@@ -13356,6 +13370,13 @@ components:
             are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           type: string
+        slo_query:
+          description: |-
+            Query that matches the SLOs this correction applies to.
+            The query uses the [Events search syntax](https://docs.datadoghq.com/events/explorer/searching/)
+            and can filter SLOs by SLO tags.
+          example: "env:prod service:checkout"
+          type: string
         start:
           description: Starting time of the correction in epoch seconds.
           example: 1600000000
@@ -37493,7 +37514,8 @@ paths:
           - slos_read
     post:
       description: |-
-        Create an SLO Correction.
+        Create an SLO correction. Use `slo_id` to apply the correction to a single SLO, or `slo_query` to apply the
+        correction to SLOs that match a query. Exactly one of `slo_id` or `slo_query` is required.
       operationId: CreateSLOCorrection
       requestBody:
         content:
@@ -37510,6 +37532,17 @@ paths:
                       start: 1600000000
                       timezone: UTC
                     type: correction
+              slo_query:
+                value:
+                  data:
+                    attributes:
+                      category: "Scheduled Maintenance"
+                      description: "Planned maintenance window for checkout services."
+                      end: 1600003600
+                      slo_query: "env:prod service:checkout"
+                      start: 1600000000
+                      timezone: UTC
+                    type: correction
             schema:
               $ref: "#/components/schemas/SLOCorrectionCreateRequest"
         description: Create an SLO Correction
@@ -37669,6 +37702,17 @@ paths:
                       start: 1600000000
                       timezone: UTC
                     type: correction
+              slo_query:
+                value:
+                  data:
+                    attributes:
+                      category: "Scheduled Maintenance"
+                      description: "Updated correction for checkout services."
+                      end: 1600003600
+                      slo_query: "env:prod service:checkout"
+                      start: 1600000000
+                      timezone: UTC
+                    type: correction
             schema:
               $ref: "#/components/schemas/SLOCorrectionUpdateRequest"
         description: The edited SLO correction object.

diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
@@ -26647,6 +26647,100 @@ components:
       required:
         - data
       type: object
+    CustomerOrgDisableRequest:
+      description: Request payload for disabling the authenticated customer organization.
+      properties:
+        data:
+          $ref: "#/components/schemas/CustomerOrgDisableRequestData"
+      required:
+        - data
+      type: object
+    CustomerOrgDisableRequestAttributes:
+      description: |-
+        Optional attributes for a customer org disable request. When supplied, `org_uuid`
+        must match the authenticated organization or the request is rejected.
+      properties:
+        org_uuid:
+          description: |-
+            Datadog organization UUID. If supplied, must match the authenticated
+            organization.
+          example: "abcdef01-2345-6789-abcd-ef0123456789"
+          type: string
+      type: object
+    CustomerOrgDisableRequestData:
+      description: Data object for a customer org disable request.
+      properties:
+        attributes:
+          $ref: "#/components/schemas/CustomerOrgDisableRequestAttributes"
+        id:
+          description: |-
+            Optional client-supplied identifier for the request. Useful for client-side
+            correlation; the server does not use this value.
+          example: "1"
+          type: string
+        type:
+          $ref: "#/components/schemas/CustomerOrgDisableType"
+      required:
+        - type
+      type: object
+    CustomerOrgDisableResponse:
+      description: Response describing the outcome of disabling the customer organization.
+      properties:
+        data:
+          $ref: "#/components/schemas/CustomerOrgDisableResponseData"
+      required:
+        - data
+      type: object
+    CustomerOrgDisableResponseAttributes:
+      description: Attributes describing the outcome of the disable action on the customer organization.
+      properties:
+        status:
+          $ref: "#/components/schemas/CustomerOrgDisableStatus"
+      required:
+        - status
+      type: object
+    CustomerOrgDisableResponseData:
+      description: Data object returned after disabling the customer organization.
+      properties:
+        attributes:
+          $ref: "#/components/schemas/CustomerOrgDisableResponseAttributes"
+        id:
+          description: Identifier of the disabled organization.
+          example: "abcdef01-2345-6789-abcd-ef0123456789"
+          type: string
+        type:
+          $ref: "#/components/schemas/CustomerOrgDisableResponseType"
+      required:
+        - type
+        - id
+        - attributes
+      type: object
+    CustomerOrgDisableResponseType:
+      description: JSON:API resource type for a customer org disable response.
+      enum:
+        - org_disable
+      example: "org_disable"
+      type: string
+      x-enum-varnames:
+        - ORG_DISABLE
+    CustomerOrgDisableStatus:
+      description: Resulting lifecycle status of the organization after the disable action.
+      enum:
+        - disabled
+        - pending_disable
+      example: "disabled"
+      type: string
+      x-enum-varnames:
+        - DISABLED
+        - PENDING_DISABLE
+    CustomerOrgDisableType:
+      description: JSON:API resource type for a customer org disable request.
+      enum:
+        - customer_org_disable
+      example: "customer_org_disable"
+      type: string
+      x-enum-varnames:
+        - CUSTOMER_ORG_DISABLE
     DORACustomTags:
       description: A list of user-defined tags. The tags must follow the `key:value` pattern. Up to 100 may be added per event.
       example:
@@ -144869,6 +144963,81 @@ paths:
         permissions:
           - org_management
           - org_connections_write
+  /api/v2/org/disable:
+    post:
+      description: |-
+        Disable the Datadog organization associated with the authenticated user or API key.
+        The request body uses JSON:API format. If `org_uuid` is supplied, it must match
+        the authenticated org or the request is rejected. Successful calls disable the org
+        and return the resulting state from the downstream service. Requires the
+        `org_management` permission.
+      operationId: DisableCustomerOrg
+      requestBody:
+        content:
+          application/json:
+            examples:
+              default:
+                value:
+                  data:
+                    attributes:
+                      org_uuid: "abcdef01-2345-6789-abcd-ef0123456789"
+                    id: "1"
+                    type: "customer_org_disable"
+            schema:
+              $ref: "#/components/schemas/CustomerOrgDisableRequest"
+        required: true
+      responses:
+        "200":
+          content:
+            application/json:
+              examples:
+                default:
+                  value:
+                    data:
+                      attributes:
+                        status: "disabled"
+                      id: "abcdef01-2345-6789-abcd-ef0123456789"
+                      type: "org_disable"
+              schema:
+                $ref: "#/components/schemas/CustomerOrgDisableResponse"
+          description: OK
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Bad Request
+        "401":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Unauthorized
+        "403":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Forbidden
+        "429":
+          $ref: "#/components/responses/TooManyRequestsResponse"
+        "500":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Internal Server Error
+      security:
+        - apiKeyAuth: []
+          appKeyAuth: []
+        - AuthZ:
+            - org_management
+      summary: Disable the authenticated customer organization
+      tags:
+        - Customer Org
+      x-unstable: |-
+        **Note**: This endpoint is in preview and is subject to change.
+        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/org_configs:
     get:
       description: Returns all Org Configs (name, description, and value).
@@ -178361,6 +178530,10 @@ tags:
   - description: |-
       The Containers API allows you to query container data for your organization. See the [Container Monitoring page](https://docs.datadoghq.com/containers/) for more information.
     name: Containers
+  - description: |-
+      Programmatic management of a customer's Datadog organization. Use this API to perform
+      self-service organization lifecycle actions such as disabling the authenticated org.
+    name: Customer Org
   - description: |-
       Search, send, or delete events for DORA Metrics to measure and improve your software delivery performance. See the [DORA Metrics page](https://docs.datadoghq.com/dora_metrics/) for more information.
 

diff --git a/..._objective_corrections/Create-an-SLO-correction-with-slo-query-returns-OK-response.frozen b/..._objective_corrections/Create-an-SLO-correction-with-slo-query-returns-OK-response.frozen
@@ -0,0 +1 @@
+2026-05-27T20:45:22.423Z
diff --git a/...vel_objective_corrections/Create-an-SLO-correction-with-slo-query-returns-OK-response.yml b/...vel_objective_corrections/Create-an-SLO-correction-with-slo-query-returns-OK-response.yml
diff --git a/..._objective_corrections/Update-an-SLO-correction-with-slo-query-returns-OK-response.frozen b/..._objective_corrections/Update-an-SLO-correction-with-slo-query-returns-OK-response.frozen
@@ -0,0 +1 @@
+2026-06-03T15:43:01.600Z