add On-Call Paging spec (#2391)

Co-authored-by: ci.datadog-api-spec <[email protected]>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-05-09 19:42:40.999512",
-            "spec_repo_commit": "c7bad6f6"
+            "regenerated": "2025-05-12 09:40:12.743655",
+            "spec_repo_commit": "c4d0aeef"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-05-09 19:42:41.015393",
-            "spec_repo_commit": "c7bad6f6"
+            "regenerated": "2025-05-12 09:40:12.760163",
+            "spec_repo_commit": "c4d0aeef"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -9471,6 +9471,108 @@ components:
         id:
           $ref: '#/components/schemas/ApiID'
       type: object
+    CreatePageRequest:
+      description: Full request to trigger an On-Call Page.
+      example:
+        data:
+          attributes:
+            description: Page details.
+            tags:
+            - service:test
+            target:
+              identifier: my-team
+              type: team_handle
+            title: Page title
+            urgency: low
+          type: pages
+      properties:
+        data:
+          $ref: '#/components/schemas/CreatePageRequestData'
+      type: object
+    CreatePageRequestData:
+      description: The main request body, including attributes and resource type.
+      properties:
+        attributes:
+          $ref: '#/components/schemas/CreatePageRequestDataAttributes'
+        type:
+          $ref: '#/components/schemas/CreatePageRequestDataType'
+      required:
+      - type
+      type: object
+    CreatePageRequestDataAttributes:
+      description: Details about the On-Call Page you want to create.
+      properties:
+        description:
+          description: A short summary of the issue or context.
+          type: string
+        tags:
+          description: Tags to help categorize or filter the page.
+          items:
+            type: string
+          type: array
+        target:
+          $ref: '#/components/schemas/CreatePageRequestDataAttributesTarget'
+        title:
+          description: The title of the page.
+          example: 'Service: Test is down'
+          type: string
+        urgency:
+          $ref: '#/components/schemas/PageUrgency'
+      required:
+      - target
+      - title
+      - urgency
+      type: object
+    CreatePageRequestDataAttributesTarget:
+      description: Information about the target to notify (such as a team or user).
+      properties:
+        identifier:
+          description: A unique ID for the target (for example, team handle or user
+            UUID).
+          type: string
+        type:
+          description: The kind of target, `team_uuid` | `team_handle` | `user_uuid`.
+          type: string
+      type: object
+    CreatePageRequestDataType:
+      default: pages
+      description: The type of resource used when creating an On-Call Page.
+      enum:
+      - pages
+      example: pages
+      type: string
+      x-enum-varnames:
+      - PAGES
+    CreatePageResponse:
+      description: The full response object after creating a new On-Call Page.
+      example:
+        data:
+          id: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
+          type: pages
+      properties:
+        data:
+          $ref: '#/components/schemas/CreatePageResponseData'
+      type: object
+    CreatePageResponseData:
+      description: The information returned after successfully creating a page.
+      properties:
+        id:
+          description: The unique ID of the created page.
+          type: string
+        type:
+          $ref: '#/components/schemas/CreatePageResponseDataType'
+      required:
+      - type
+      type: object
+    CreatePageResponseDataType:
+      default: pages
+      description: The type of resource used when creating an On-Call Page.
+      enum:
+      - pages
+      example: pages
+      type: string
+      x-enum-varnames:
+      - PAGES
     CreateRuleRequest:
       description: Scorecard create rule request.
       properties:
@@ -27104,6 +27206,17 @@ components:
       - ARRAY_NUMBER
       - ARRAY_BOOLEAN
       - ARRAY_OBJECT
+    PageUrgency:
+      default: high
+      description: On-Call Page urgency level.
+      enum:
+      - low
+      - high
+      example: high
+      type: string
+      x-enum-varnames:
+      - LOW
+      - HIGH
     Pagination:
       description: Pagination object.
       properties:
@@ -38863,6 +38976,7 @@ components:
       - low
       - high
       - dynamic
+      example: low
       type: string
       x-enum-varnames:
       - LOW
@@ -51416,6 +51530,227 @@ paths:
         operator: AND
         permissions:
         - on_call_write
+  /api/v2/on-call/pages:
+    post:
+      description: 'Trigger a new On-Call Page.
+
+        '
+      operationId: CreateOnCallPage
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CreatePageRequest'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/CreatePageResponse'
+          description: OK.
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      servers:
+      - url: https://{site}
+        variables:
+          site:
+            default: navy.oncall.datadoghq.com
+            description: The globally available endpoint for On-Call.
+            enum:
+            - saffron.oncall.datadoghq.com
+            - navy.oncall.datadoghq.com
+            - coral.oncall.datadoghq.com
+            - teal.oncall.datadoghq.com
+            - beige.oncall.datadoghq.eu
+      - url: '{protocol}://{name}'
+        variables:
+          name:
+            default: api.datadoghq.com
+            description: Full site DNS name.
+          protocol:
+            default: https
+            description: The protocol for accessing the API.
+      - url: https://{subdomain}.{site}
+        variables:
+          site:
+            default: datadoghq.com
+            description: Any Datadog deployment.
+          subdomain:
+            default: api
+            description: The subdomain where the API is deployed.
+      summary: Create On-Call Page
+      tags:
+      - On-Call Paging
+  /api/v2/on-call/pages/{page_id}/acknowledge:
+    post:
+      description: 'Acknowledges an On-Call Page.
+
+        '
+      operationId: AcknowledgeOnCallPage
+      parameters:
+      - description: The page ID.
+        in: path
+        name: page_id
+        required: true
+        schema:
+          example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
+          format: uuid
+          type: string
+      responses:
+        '202':
+          description: Accepted.
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      servers:
+      - url: https://{site}
+        variables:
+          site:
+            default: navy.oncall.datadoghq.com
+            description: The globally available endpoint for On-Call.
+            enum:
+            - saffron.oncall.datadoghq.com
+            - navy.oncall.datadoghq.com
+            - coral.oncall.datadoghq.com
+            - teal.oncall.datadoghq.com
+            - beige.oncall.datadoghq.eu
+      - url: '{protocol}://{name}'
+        variables:
+          name:
+            default: api.datadoghq.com
+            description: Full site DNS name.
+          protocol:
+            default: https
+            description: The protocol for accessing the API.
+      - url: https://{subdomain}.{site}
+        variables:
+          site:
+            default: datadoghq.com
+            description: Any Datadog deployment.
+          subdomain:
+            default: api
+            description: The subdomain where the API is deployed.
+      summary: Acknowledge On-Call Page
+      tags:
+      - On-Call Paging
+  /api/v2/on-call/pages/{page_id}/escalate:
+    post:
+      description: 'Escalates an On-Call Page.
+
+        '
+      operationId: EscalateOnCallPage
+      parameters:
+      - description: The page ID.
+        in: path
+        name: page_id
+        required: true
+        schema:
+          example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
+          format: uuid
+          type: string
+      responses:
+        '202':
+          description: Accepted.
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      servers:
+      - url: https://{site}
+        variables:
+          site:
+            default: navy.oncall.datadoghq.com
+            description: The globally available endpoint for On-Call.
+            enum:
+            - saffron.oncall.datadoghq.com
+            - navy.oncall.datadoghq.com
+            - coral.oncall.datadoghq.com
+            - teal.oncall.datadoghq.com
+            - beige.oncall.datadoghq.eu
+      - url: '{protocol}://{name}'
+        variables:
+          name:
+            default: api.datadoghq.com
+            description: Full site DNS name.
+          protocol:
+            default: https
+            description: The protocol for accessing the API.
+      - url: https://{subdomain}.{site}
+        variables:
+          site:
+            default: datadoghq.com
+            description: Any Datadog deployment.
+          subdomain:
+            default: api
+            description: The subdomain where the API is deployed.
+      summary: Escalate On-Call Page
+      tags:
+      - On-Call Paging
+  /api/v2/on-call/pages/{page_id}/resolve:
+    post:
+      description: 'Resolves an On-Call Page.
+
+        '
+      operationId: ResolveOnCallPage
+      parameters:
+      - description: The page ID.
+        in: path
+        name: page_id
+        required: true
+        schema:
+          example: 15e74b8b-f865-48d0-bcc5-453323ed2c8f
+          format: uuid
+          type: string
+      responses:
+        '202':
+          description: Accepted.
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ: []
+      servers:
+      - url: https://{site}
+        variables:
+          site:
+            default: navy.oncall.datadoghq.com
+            description: The globally available endpoint for On-Call.
+            enum:
+            - saffron.oncall.datadoghq.com
+            - navy.oncall.datadoghq.com
+            - coral.oncall.datadoghq.com
+            - teal.oncall.datadoghq.com
+            - beige.oncall.datadoghq.eu
+      - url: '{protocol}://{name}'
+        variables:
+          name:
+            default: api.datadoghq.com
+            description: Full site DNS name.
+          protocol:
+            default: https
+            description: The protocol for accessing the API.
+      - url: https://{subdomain}.{site}
+        variables:
+          site:
+            default: datadoghq.com
+            description: Any Datadog deployment.
+          subdomain:
+            default: api
+            description: The subdomain where the API is deployed.
+      summary: Resolve On-Call Page
+      tags:
+      - On-Call Paging
   /api/v2/on-call/schedules:
     post:
       description: Create a new on-call schedule
@@ -61556,6 +61891,12 @@ tags:
   externalDocs:
     url: https://docs.datadoghq.com/service_management/on-call/
   name: On-Call
+- description: 'Trigger and manage [Datadog On-Call](https://docs.datadoghq.com/service_management/on-call/)
+
+    pages directly through the Datadog API.'
+  externalDocs:
+    url: https://docs.datadoghq.com/service_management/on-call/
+  name: On-Call Paging
 - description: 'Configure your [Datadog Opsgenie integration](https://docs.datadoghq.com/integrations/opsgenie/)
 
     directly through the Datadog API.'