> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coralogix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List notification deliveries for cases

> Retrieve notification delivery records for one or more cases, including routing, target, and outcome information.

Requires the following permissions:
- `case:Read`



## OpenAPI

````yaml openapi_v5.yaml post /cases/notifications/v1/deliveries
openapi: 3.0.0
info:
  title: ''
  version: 1.0.0
servers:
  - url: https://api.coralogix.com/mgmt/openapi/5
  - url: https://api.eu2.coralogix.com/mgmt/openapi/5
  - url: https://api.coralogix.us/mgmt/openapi/5
  - url: https://api.cx498.coralogix.com/mgmt/openapi/5
  - url: https://api.coralogix.in/mgmt/openapi/5
  - url: https://api.coralogixsg.com/mgmt/openapi/5
  - url: https://api.ap3.coralogix.com/mgmt/openapi/5
security:
  - apiKeyAuth: []
tags:
  - name: AI Applications Service
    description: Manage the catalog of AI applications discovered from spans.
    externalDocs:
      url: ''
  - name: AI Evaluations Service
    description: >-
      Manage AI evaluations and the custom evaluation catalog for AI
      applications.
    externalDocs:
      url: ''
  - name: API Keys Admin Service
    description: Administrative operations for API Keys management.
    externalDocs:
      url: ''
  - name: API Keys Service
    description: Manage your API Keys.
    externalDocs:
      url: ''
  - name: Actions Service
    description: View and manage your Actions.
    externalDocs:
      url: ''
  - name: Alert Scheduler Rule service
    description: Manage your alert scheduler rules.
    externalDocs:
      url: ''
  - name: Alert definitions service
    description: >-
      View and manage your alerts using alert definitions - data structures that
      contain the configuration required to create an alert.
    externalDocs:
      description: Learn more about alerts in our documentation
      url: https://coralogix.com/docs/user-guides/alerting/introduction-to-alerts/
  - name: Alert events service
    description: >-
      Get information regarding your alert events - instances of alerts being
      triggered.
    externalDocs:
      description: Learn more about alert events and incidents in our documentation.
      url: https://coralogix.com/docs/user-guides/alerting/incidents/
  - name: Case Events service
    description: Manage case events, comments, and external thread synchronization.
    externalDocs:
      url: ''
  - name: Case Settings service
    description: Manage case settings team configurations.
    externalDocs:
      url: ''
  - name: Cases notification service
    description: Track notification adjacent data for cases.
    externalDocs:
      url: ''
  - name: Cases service
    description: >-
      Manage cases throughout their lifecycle. Create, view, assign,
      acknowledge, unacknowledge, resolve, and close cases to streamline
      investigations and follow-ups.
    externalDocs:
      description: Learn more about Cases in our documentation
      url: https://coralogix.com/docs/user-guides/cases/
  - name: Connector Schema service
    description: Retrieve connector schemas for notification center integrations
    externalDocs:
      description: Learn more about connectors in our documentation
      url: >-
        https://coralogix.com/docs/user-guides/notification-center/connectors/introduction/
  - name: Connectors service
    description: >-
      View and manage your connectors - integration instances for notification
      destinations
    externalDocs:
      description: Lean more about connectors in our documentation
      url: >-
        https://coralogix.com/docs/user-guides/notification-center/connectors/introduction/
  - name: Contextual data integration service
    description: Query for contextual data integration information.
    externalDocs:
      url: ''
  - name: Custom Enrichments Service
    description: Manage your enrichments.
    externalDocs:
      url: ''
  - name: Dashboard folders service
    description: Manage your dashboard folders.
    externalDocs:
      url: ''
  - name: Dashboard service
    description: Get information about the Coralogix Dashboard catalog.
    externalDocs:
      url: ''
  - name: Data Usage Query service
    description: >-
      Query billable data usage through the public Coralogix API using daily or
      hourly bucketed aggregations over supported labels.
    externalDocs:
      url: ''
  - name: Data Usage Service
    description: A service to manage data usage metrics.
    externalDocs:
      url: ''
  - name: Enrichments Service
    description: Manage your enrichments.
    externalDocs:
      url: ''
  - name: Entities service
    description: Query information about registered entities in the notification center
    externalDocs:
      description: Lean more about the notification center in our documentation
      url: https://coralogix.com/docs/user-guides/notification-center/introduction/
  - name: Events Service
    description: A service for querying events.
    externalDocs:
      description: Learn more about alerts in our documentation
      url: https://coralogix.com/docs/user-guides/alerting/introduction-to-alerts/
  - name: Events2Metrics Service
    description: Manage your events2metrics.
    externalDocs:
      url: ''
  - name: Extension deployment service
    description: A service that enables querying for extension deployment information.
    externalDocs:
      description: Find out more about extensions in our documentation.
      url: https://coralogix.com/docs/integrations/extensions/
  - name: Extension service
    description: A service that enables querying for extension information.
    externalDocs:
      description: Learn more about extensions in our documentation.
      url: https://coralogix.com/docs/integrations/extensions/
  - name: Folders for views service
    description: Create and manage view folders.
    externalDocs:
      url: ''
  - name: Global routers service
    description: >-
      View and manage your global routers - entities that direct notifications
      to configured destinations based on conditions
    externalDocs:
      description: Lean more about global routers in our documentation
      url: >-
        https://coralogix.com/docs/user-guides/notification-center/routing/introduction/
  - name: IP access service
    description: >-
      IP access service provides the API for managing company IP access
      settings.
    externalDocs:
      url: ''
  - name: Incidents service
    description: >-
      Handle all operations related to incident management within Coralogix.
      Identify, manage, and resolve incidents efficiently through automated
      workflows and team collaboration.
    externalDocs:
      description: Find out more about incident management in our documentation
      url: https://coralogix.com/docs/user-guides/alerting/incidents/
  - name: Integration service
    description: A service that enables querying for integration information.
    externalDocs:
      description: Find out more about integrations in our documentation.
      url: https://coralogix.com/docs/integrations/getting-started/
  - name: Metrics Data Archive Service
    description: View and manage your storage targets for metrics.
    externalDocs:
      description: Find out more about archives
      url: >-
        https://coralogix.com/docs/user-guides/data-flow/s3-archive/connect-s3-archive/
  - name: Notifications testing service
    description: >-
      Test your notification center configurations including connectors,
      presets, and templates
    externalDocs:
      description: Lean more about the notification center in our documentation
      url: https://coralogix.com/docs/user-guides/notification-center/introduction/
  - name: Outgoing webhooks service
    externalDocs:
      description: Find out more about outbound webhooks in our documentation.
      url: >-
        https://coralogix.com/docs/user-guides/alerting/outbound-webhooks/generic-outbound-webhooks-alert-webhooks/
  - name: Policies Service
    description: View and manage your TCO policies
    externalDocs:
      url: ''
  - name: Presets service
    description: >-
      View and manage your presets - pre-configured templates for notification
      content rendering
    externalDocs:
      description: Lean more about presets in our documentation
      url: >-
        https://coralogix.com/docs/user-guides/notification-center/presets/introduction/
  - name: Quota Allocation Rule Set service
    description: Manage quota allocation rules for different entity types.
    externalDocs:
      url: ''
  - name: Recording Rules Service
    description: A service to manage recording rules.
    externalDocs:
      url: ''
  - name: Retentions Service
    description: View and manage retentions
    externalDocs:
      url: ''
  - name: Role Management Service
    description: Service for managing system and custom roles.
    externalDocs:
      url: ''
  - name: Rule Groups Service
    description: A service to manage rule groups.
    externalDocs:
      url: ''
  - name: SAML Configuration Service
    description: Manage your SAML configuration
    externalDocs:
      url: ''
  - name: Scopes Service
    description: A service to manage scopes
    externalDocs:
      url: ''
  - name: Slos Service
    description: A service for managing Service Level Objectives (SLOs).
    externalDocs:
      url: ''
  - name: Target Service
    description: View and manage your storage targets for logs.
    externalDocs:
      description: Find out more about archives
      url: >-
        https://coralogix.com/docs/user-guides/data-flow/s3-archive/connect-s3-archive/
  - name: Team Groups Management Service
    description: Manage Team Groups.
    externalDocs:
      url: ''
  - name: Users Management Service
    description: >-
      Manage team members (users) including creation, updates, search, and
      status management.
    externalDocs:
      url: ''
  - name: Views service
    description: Create and manage views.
    externalDocs:
      url: ''
paths:
  /cases/notifications/v1/deliveries:
    post:
      tags:
        - Cases notification service
      summary: List notification deliveries for cases
      description: >-
        Retrieve notification delivery records for one or more cases, including
        routing, target, and outcome information.


        Requires the following permissions:

        - `case:Read`
      operationId: CasesNotificationService_ListNotificationDeliveries
      requestBody:
        content:
          application/json:
            schema:
              description: >-
                Request to retrieve notification delivery records for one or
                more cases.
              properties:
                caseIds:
                  minItems: 0
                  type: array
                  items:
                    minLength: 0
                    type: string
                    description: Case IDs to retrieve notification deliveries for
                  description: Case IDs to retrieve notification deliveries for
                  example:
                    - 3f166e9f-3c88-4af2-b52e-138f339dab3e
                    - a1b2c3d4-e5f6-7890-abcd-ef1234567890
              required:
                - caseIds
              title: List notification deliveries request
              type: object
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListNotificationDeliveriesResponse'
          description: ''
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
          description: Bad Request
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
          description: Unauthorized request
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
          description: Internal server error
      externalDocs:
        url: ''
components:
  schemas:
    ListNotificationDeliveriesResponse:
      title: List notification deliveries response
      required:
        - deliveriesByCase
      type: object
      properties:
        deliveriesByCase:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/CaseNotificationDeliveries'
          description: Notification deliveries keyed by case ID
      description: Response containing a list of notification delivery records for cases.
      externalDocs:
        url: ''
    Error:
      type: object
      properties:
        code:
          maximum: 599
          minimum: 100
          type: integer
          description: HTTP status code of the error (for example 400, 404, 500).
          format: int32
        message:
          maxLength: 4096
          minLength: 0
          pattern: ^[\s\S]*$
          type: string
          description: Human-readable description of the error.
      description: Standard error response body returned for a failed request.
    CaseNotificationDeliveries:
      title: Case notification deliveries
      required:
        - notificationDeliveries
      type: object
      properties:
        notificationDeliveries:
          minItems: 0
          type: array
          items:
            $ref: '#/components/schemas/NotificationDelivery'
          description: Notification deliveries for the case
      description: Notification deliveries for a single case.
      externalDocs:
        url: ''
    NotificationDelivery:
      title: Notification delivery
      required:
        - timestamp
      type: object
      oneOf:
        - required:
            - noRouterMatched
          type: object
        - required:
            - noNotificationCreated
          type: object
        - required:
            - attempted
          type: object
        - type: object
          not:
            anyOf:
              - required:
                  - noRouterMatched
                type: object
              - required:
                  - noNotificationCreated
                type: object
              - required:
                  - attempted
                type: object
      properties:
        attempted:
          $ref: '#/components/schemas/RoutedDelivery'
        noNotificationCreated:
          $ref: '#/components/schemas/NoNotificationCreatedResult'
        noRouterMatched:
          $ref: '#/components/schemas/NoRouterMatchedResult'
        requestNotificationId:
          minLength: 0
          type: string
          description: >-
            The notification request ID that triggered this delivery, used to
            correlate delivery outcomes with their originating requests
          example: a1b2c3d4-5678-90ab-cdef-1234567890ab
        timestamp:
          minLength: 0
          type: string
          description: When the notification was triggered
          format: date-time
          example: '2025-09-22T10:30:00.000Z'
      description: Delivery results for a single notification.
      externalDocs:
        url: ''
    RoutedDelivery:
      title: Routed delivery
      required:
        - router
        - attempts
      type: object
      properties:
        attempts:
          minItems: 0
          type: array
          items:
            $ref: '#/components/schemas/DeliveryAttempt'
          description: Individual delivery attempts to connectors
        router:
          $ref: '#/components/schemas/RouterInfo'
      description: >-
        Delivery attempts routed through a single router to one or more
        connectors.
      externalDocs:
        url: ''
    NoNotificationCreatedResult:
      title: No notification created result
      required:
        - matchedRouters
      type: object
      properties:
        matchedRouters:
          minItems: 0
          type: array
          items:
            $ref: '#/components/schemas/RouterInfo'
          description: Routers that matched the notification request
      description: >-
        Indicates that routers matched but no notification was ultimately
        created.
      externalDocs:
        url: ''
    NoRouterMatchedResult:
      title: No router matched result
      type: object
      additionalProperties: false
      description: Indicates that no router matched the notification request.
      externalDocs:
        url: ''
    DeliveryAttempt:
      title: Delivery attempt
      required:
        - connector
        - outcome
      type: object
      properties:
        connector:
          $ref: '#/components/schemas/ConnectorDetails'
        outcome:
          $ref: '#/components/schemas/DeliveryOutcome'
      description: A single delivery attempt to a specific connector.
      externalDocs:
        url: ''
    RouterInfo:
      title: Router info
      required:
        - routerId
        - routerName
      type: object
      properties:
        routerId:
          minLength: 0
          type: string
          description: Unique identifier of the router
          example: d4e5f678-90ab-cdef-1234-567890abcdef
        routerName:
          minLength: 0
          type: string
          description: Display name of the router
          example: Production alerts router
      description: Information about a notification router.
      externalDocs:
        url: ''
    ConnectorDetails:
      title: Connector details
      required:
        - connectorId
        - connectorType
        - connectorName
      type: object
      properties:
        connectorId:
          minLength: 0
          type: string
          description: Unique identifier of the connector
          example: c1d2e3f4-5678-90ab-cdef-1234567890ab
        connectorName:
          minLength: 0
          type: string
          description: Display name of the connector
          example: Production Slack
        connectorType:
          $ref: '#/components/schemas/v1.ConnectorType'
      description: Details of a notification connector.
      externalDocs:
        url: ''
    DeliveryOutcome:
      title: Delivery outcome
      type: object
      oneOf:
        - required:
            - success
          type: object
        - required:
            - failure
          type: object
        - type: object
          not:
            anyOf:
              - required:
                  - success
                type: object
              - required:
                  - failure
                type: object
      properties:
        failure:
          $ref: '#/components/schemas/DeliveryFailure'
        success:
          $ref: '#/components/schemas/DeliverySuccess'
      description: Outcome of a notification delivery attempt.
      externalDocs:
        url: ''
    v1.ConnectorType:
      enum:
        - CONNECTOR_TYPE_UNSPECIFIED
        - CONNECTOR_TYPE_SLACK
        - CONNECTOR_TYPE_SERVICE_NOW
        - CONNECTOR_TYPE_PAGER_DUTY
        - CONNECTOR_TYPE_EMAIL
        - CONNECTOR_TYPE_GENERIC_HTTPS
        - CONNECTOR_TYPE_MICROSOFT_TEAMS
      type: string
      description: Connector type.
    DeliveryFailure:
      title: Delivery failure
      required:
        - errorMessage
      type: object
      properties:
        errorMessage:
          minLength: 0
          type: string
          description: Error message describing the failure
          example: Connection timeout after 30s
      description: Failed delivery outcome with error details.
      externalDocs:
        url: ''
    DeliverySuccess:
      title: Delivery success
      type: object
      properties:
        evidenceUrl:
          minLength: 0
          type: string
          description: >-
            URL to the delivered notification, if available (e.g. Slack message,
            ServiceNow record)
          example: https://workspace.slack.com/archives/C01ABC23DEF/p1234567890123456
      description: Successful delivery outcome with an optional evidence URL.
      externalDocs:
        url: ''
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: API key authentication

````