Cisco Catalyst Center Assurance Events API

APIs related to assurance events

OpenAPI Specification

cisco-catalyst-center-assuranceevents-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: OpenAPI Spec Assurance Events API
  description: APIs related to assurance events.
  termsOfService: https://www.cisco.com/c/en/us/about/legal/cloud-and-software/end_user_license_agreement.html
  contact:
    name: Cisco TAC World Wide
    url: https://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html
    email: tac@cisco.com
  license:
    name: Cisco Catalyst Center License
    url: https://www.cisco.com/c/en/us/products/collateral/software/dna-software-ebook-cte.html
  version: 1.0.0
  x-provenance:
    method: harvested
    authored_by: Cisco Catalyst Center
    harvested_by: API Evangelist
    harvested_on: '2026-08-19'
    first_party: true
    provider_published: true
    source_host: developer.cisco.com
    note: 27 Cisco-published OpenAPI 3.0 Assurance documents (185 operations). Ownership confirmed from the tac@cisco.com contact, the Cisco EULA terms-of-service URL and the Cisco Catalyst Center license block carried in each document.
  x-evidence:
  - type: source
    url: https://developer.cisco.com/docs/catalyst-center/
  - type: source
    url: https://developer.cisco.com/dnacenter/
servers:
- url: https://developer.cisco.com
tags:
- name: assuranceEvents
  description: APIs related to assurance events
paths:
  /dna/data/api/v1/assuranceEvents:
    get:
      tags:
      - assuranceEvents
      summary: Query assurance events
      description: 'API to fetch the list of assurance events using basic filters. Use the `/assuranceEvents/query` API if you need complex filtering.


        Note that querying of data spanning more than 7 days is not allowed, so difference between `startTime` and `endTime` must not be more than that.

        '
      operationId: readEvents
      parameters:
      - name: deviceFamily
        in: query
        description: 'Device family. Please note that multiple families across network device type and client type is not allowed. For example, choosing `Routers` along with `Wireless Client` or `Unified AP` is not supported.

          Examples:


          `deviceFamily=Switches and Hubs` (single deviceFamily requested)


          `deviceFamily=Switches and Hubs&deviceFamily=Routers` (multiple deviceFamily requested)

          '
        required: true
        style: form
        explode: true
        schema:
          minItems: 1
          type: array
          items:
            type: string
            enum:
            - Switches and Hubs
            - Routers
            - Wireless Controller
            - Third Party Device
            - Unified AP
            - Wired Client
            - Wireless Client
        example:
        - Switches and Hubs
      - name: startTime
        in: query
        description: 'Start time from which API queries the data set related to the resource. It must be specified in UNIX epochtime in milliseconds. Value is inclusive.


          If `startTime` is not provided, API will default to current time minus 24 hours.

          '
        schema:
          type: integer
          format: int64
        example: 1705348800000
      - name: endTime
        in: query
        description: 'End time to which API queries the data set related to the resource. It must be specified in UNIX epochtime in milliseconds. Value is inclusive.


          If `endTime` is not provided, API will default to current time.

          '
        schema:
          type: integer
          format: int64
        example: 1705435200000
      - name: messageType
        in: query
        description: 'Message type for the event.


          Examples:


          `messageType=Syslog` (single messageType requested)


          `messageType=Trap&messageType=Syslog` (multiple messageType requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            enum:
            - Syslog
            - Trap
            - Device
            - Device Controller
            - ISE
            - TDL
        example:
        - Syslog
      - name: severity
        in: query
        description: 'Severity of the event between 0 and 6. This is applicable only for events related to network devices (other than AP) and `Wired Client` events.


          | Value | Severity    |

          | ----- | ----------- |

          | 0     | Emergency   |

          | 1     | Alert       |

          | 2     | Critical    |

          | 3     | Error       |

          | 4     | Warning     |

          | 5     | Notice      |

          | 6     | Info        |


          Examples:


          `severity=0` (single severity requested)


          `severity=0&severity=1` (multiple severity requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            maximum: 6
            minimum: 0
            type: integer
            format: int32
        example:
        - 2
      - name: siteId
        in: query
        description: 'The UUID of the site. (Ex. `flooruuid`)


          Examples:


          `?siteId=id1` (single id requested)


          `?siteId=id1&siteId=id2&siteId=id3` (multiple ids requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteHierarchyId
        in: query
        description: 'The full hierarchy breakdown of the site tree in id form starting from Global site UUID and ending with the specific site UUID. (Ex. `globalUuid/areaUuid/buildingUuid/floorUuid`)


          This field supports wildcard asterisk (`*`) character search support. E.g. `*uuid*, *uuid, uuid*`


          Examples:


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid `(single siteHierarchyId requested)


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid&siteHierarchyId=globalUuid/areaUuid2/buildingUuid2/floorUuid2` (multiple siteHierarchyIds requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: networkDeviceName
        in: query
        description: 'Network device name. This parameter is applicable for network device related families.

          This field supports wildcard (`*`) character-based search. Ex: `*Branch*` or `Branch*` or `*Branch`

          Examples:


          `networkDeviceName=Branch-3-Gateway` (single networkDeviceName requested)


          `networkDeviceName=Branch-3-Gateway&networkDeviceName=Branch-3-Switch` (multiple networkDeviceName requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
        example:
        - Branch-3-Switch
      - name: networkDeviceId
        in: query
        description: 'The list of Network Device Uuids. (Ex. `6bef213c-19ca-4170-8375-b694e251101c`)


          Examples:


          `networkDeviceId=6bef213c-19ca-4170-8375-b694e251101c` (single networkDeviceId requested)


          `networkDeviceId=6bef213c-19ca-4170-8375-b694e251101c&networkDeviceId=32219612-819e-4b5e-a96b-cf22aca13dd9&networkDeviceId=2541e9a7-b80d-4955-8aa2-79b233318ba0` (multiple networkDeviceIds with & separator)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: apMac
        in: query
        description: 'MAC address of the access point. This parameter is applicable for `Unified AP` and `Wireless Client` events.


          This field supports wildcard (`*`) character-based search. Ex: `*50:0F*` or `50:0F*` or `*50:0F`


          Examples:


          `apMac=50:0F:80:0F:F7:E0` (single apMac requested)


          `apMac=50:0F:80:0F:F7:E0&apMac=18:80:90:AB:7E:A0` (multiple apMac requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            pattern: ^([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2})$
            type: string
        example:
        - F3:9B:C7:8A:0B:D0
      - name: clientMac
        in: query
        description: 'MAC address of the client. This parameter is applicable for `Wired Client` and `Wireless Client` events.


          This field supports wildcard (`*`) character-based search. Ex: `*66:2B*` or `66:2B*` or `*66:2B`


          Examples:


          `clientMac=66:2B:B8:D2:01:56` (single clientMac requested)


          `clientMac=66:2B:B8:D2:01:56&clientMac=DC:A6:32:F5:5A:89` (multiple clientMac requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            pattern: ^([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2})$
            type: string
        example:
        - 94:D4:69:F2:56:60
      - name: attribute
        in: query
        description: "The list of attributes that needs to be included in the response. If this parameter is not provided, then basic attributes (`id`, `name`, `timestamp`, `details`, `messageType`, `siteHierarchyId`, `siteHierarchy`, `deviceFamily`, `networkDeviceId`, `networkDeviceName`, `managementIpAddress`) would be part of the response.\n Examples:\n\n`attribute=name` (single attribute requested)\n\n`attribute=name&attribute=networkDeviceName` (multiple attribute requested)\n"
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            enum:
            - affectedClients
            - apMac
            - apRadioOperationState
            - apRole
            - apSwitchId
            - apSwitchName
            - assocRssi
            - assocSnr
            - auditSessionId
            - authServerIp
            - bssid
            - candidateAPs
            - childEvents
            - clientMac
            - connectedInterfaceName
            - currentRadioPowerLevel
            - details
            - deviceFamily
            - dhcpServerIp
            - duid
            - eventStatus
            - facility
            - failureCategory
            - failureIpAddress
            - frequency
            - id
            - identifier
            - invalidIeAPs
            - ipv4
            - ipv6
            - isPrivateMac
            - lastApDisconnectReason
            - lastApResetType
            - managementIpAddress
            - messageType
            - missingResponseAPs
            - mnemonic
            - name
            - networkDeviceId
            - networkDeviceName
            - newRadioChannelList
            - newRadioChannelWidth
            - oldRadioChannelList
            - oldRadioChannelWidth
            - previousRadioPowerLevel
            - radioChannelSlot
            - radioChannelUtilization
            - radioInterference
            - radioNoise
            - reasonDescription
            - replacedDeviceSerialNumber
            - replacingDeviceSerialNumber
            - resultStatus
            - roamType
            - severity
            - siteHierarchy
            - siteHierarchyId
            - ssid
            - subReasonDescription
            - switchNumber
            - timestamp
            - udnId
            - udnName
            - username
            - vlanId
            - wirelessClientEventEndTime
            - wirelessClientEventStartTime
            - wlcId
            - wlcName
      - name: view
        in: query
        description: "The list of events views. Please refer to `EventViews` for the supported list\n Examples:\n\n`view=network` (single view requested)\n\n`view=network&view=ap` (multiple view requested)\n"
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            enum:
            - basic
            - network
            - ap
            - wiredClient
            - wirelessClient
      - name: offset
        in: query
        description: Specifies the starting point within all records returned by the API. It's one based offset. The starting value is 1.
        schema:
          minimum: 1
          type: integer
          default: 1
      - name: limit
        in: query
        description: Maximum number of records to return
        schema:
          maximum: 20
          minimum: 1
          type: integer
          default: 10
      - name: sortBy
        in: query
        description: A field within the response to sort by.
        schema:
          type: string
          default: timestamp
      - name: order
        in: query
        description: The sort order of the field ascending or descending.
        schema:
          type: string
          default: desc
          enum:
          - asc
          - desc
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database. It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: ui:client360
      responses:
        '200':
          description: List of events for the given filter criteria
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/EventListResponse'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
  /dna/data/api/v1/assuranceEvents/count:
    get:
      tags:
      - assuranceEvents
      summary: Count the number of events
      description: 'API to fetch the count of assurance events that match the filter criteria. Use the `/assuranceEvents/query/count` API if you need complex filtering.


        Note that querying of data spanning more than 7 days is not allowed, so difference between `startTime` and `endTime` must not be more than that.

        '
      operationId: countEvents
      parameters:
      - name: deviceFamily
        in: query
        description: 'Device family. Please note that multiple families across network device type and client type is not allowed. For example, choosing `Routers` along with `Wireless Client` or `Unified AP` is not supported.

          Examples:


          `deviceFamily=Switches and Hubs` (single deviceFamily requested)


          `deviceFamily=Switches and Hubs&deviceFamily=Routers` (multiple deviceFamily requested)

          '
        required: true
        style: form
        explode: true
        schema:
          minItems: 1
          type: array
          items:
            type: string
            enum:
            - Switches and Hubs
            - Routers
            - Wireless Controller
            - Third Party Device
            - Unified AP
            - Wired Client
            - Wireless Client
        example:
        - Switches and Hubs
      - name: startTime
        in: query
        description: 'Start time from which API queries the data set related to the resource. It must be specified in UNIX epochtime in milliseconds. Value is inclusive.


          If `startTime` is not provided, API will default to current time minus 24 hours.

          '
        schema:
          type: integer
          format: int64
        example: 1705348800000
      - name: endTime
        in: query
        description: 'End time to which API queries the data set related to the resource. It must be specified in UNIX epochtime in milliseconds. Value is inclusive.


          If `endTime` is not provided, API will default to current time.

          '
        schema:
          type: integer
          format: int64
        example: 1705435200000
      - name: messageType
        in: query
        description: 'Message type for the event.


          Examples:


          `messageType=Syslog` (single messageType requested)


          `messageType=Trap&messageType=Syslog` (multiple messageType requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            enum:
            - Syslog
            - Trap
            - Device
            - Device Controller
            - ISE
            - TDL
        example:
        - Syslog
      - name: severity
        in: query
        description: 'Severity of the event between 0 and 6. This is applicable only for events related to network devices (other than AP) and `Wired Client` events.


          | Value | Severity    |

          | ----- | ----------- |

          | 0     | Emergency   |

          | 1     | Alert       |

          | 2     | Critical    |

          | 3     | Error       |

          | 4     | Warning     |

          | 5     | Notice      |

          | 6     | Info        |


          Examples:


          `severity=0` (single severity requested)


          `severity=0&severity=1` (multiple severity requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            maximum: 6
            minimum: 0
            type: integer
            format: int32
        example:
        - 2
      - name: siteId
        in: query
        description: 'The UUID of the site. (Ex. `flooruuid`)


          Examples:


          `?siteId=id1` (single id requested)


          `?siteId=id1&siteId=id2&siteId=id3` (multiple ids requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: siteHierarchyId
        in: query
        description: 'The full hierarchy breakdown of the site tree in id form starting from Global site UUID and ending with the specific site UUID. (Ex. `globalUuid/areaUuid/buildingUuid/floorUuid`)


          This field supports wildcard asterisk (`*`) character search support. E.g. `*uuid*, *uuid, uuid*`


          Examples:


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid `(single siteHierarchyId requested)


          `?siteHierarchyId=globalUuid/areaUuid/buildingUuid/floorUuid&siteHierarchyId=globalUuid/areaUuid2/buildingUuid2/floorUuid2` (multiple siteHierarchyIds requested)

          '
        required: false
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: networkDeviceName
        in: query
        description: 'Network device name. This parameter is applicable for network device related families.

          This field supports wildcard (`*`) character-based search. Ex: `*Branch*` or `Branch*` or `*Branch`

          Examples:


          `networkDeviceName=Branch-3-Gateway` (single networkDeviceName requested)


          `networkDeviceName=Branch-3-Gateway&networkDeviceName=Branch-3-Switch` (multiple networkDeviceName requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
        example:
        - Branch-3-Switch
      - name: networkDeviceId
        in: query
        description: 'The list of Network Device Uuids. (Ex. `6bef213c-19ca-4170-8375-b694e251101c`)


          Examples:


          `networkDeviceId=6bef213c-19ca-4170-8375-b694e251101c` (single networkDeviceId requested)


          `networkDeviceId=6bef213c-19ca-4170-8375-b694e251101c&networkDeviceId=32219612-819e-4b5e-a96b-cf22aca13dd9&networkDeviceId=2541e9a7-b80d-4955-8aa2-79b233318ba0` (multiple networkDeviceIds with & separator)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
      - name: apMac
        in: query
        description: 'MAC address of the access point. This parameter is applicable for `Unified AP` and `Wireless Client` events.


          This field supports wildcard (`*`) character-based search. Ex: `*50:0F*` or `50:0F*` or `*50:0F`


          Examples:


          `apMac=50:0F:80:0F:F7:E0` (single apMac requested)


          `apMac=50:0F:80:0F:F7:E0&apMac=18:80:90:AB:7E:A0` (multiple apMac requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            pattern: ^([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2})$
            type: string
        example:
        - F3:9B:C7:8A:0B:D0
      - name: clientMac
        in: query
        description: 'MAC address of the client. This parameter is applicable for `Wired Client` and `Wireless Client` events.


          This field supports wildcard (`*`) character-based search. Ex: `*66:2B*` or `66:2B*` or `*66:2B`


          Examples:


          `clientMac=66:2B:B8:D2:01:56` (single clientMac requested)


          `clientMac=66:2B:B8:D2:01:56&clientMac=DC:A6:32:F5:5A:89` (multiple clientMac requested)

          '
        style: form
        explode: true
        schema:
          type: array
          items:
            pattern: ^([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2})$
            type: string
        example:
        - 94:D4:69:F2:56:60
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database. It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: ui:client360
      responses:
        '200':
          description: Count of events for the given filter criteria
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/CountIntegerResponse'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
  /dna/data/api/v1/assuranceEvents/{id}:
    get:
      tags:
      - assuranceEvents
      summary: Get details of a single assurance event
      description: API to fetch the details of an assurance event using event `id`.
      operationId: readEventDetails
      parameters:
      - name: id
        in: path
        description: Unique identifier for the event
        required: true
        style: simple
        explode: false
        schema:
          type: string
      - name: attribute
        in: query
        description: "The list of attributes that needs to be included in the response. If this parameter is not provided, then basic attributes (`id`, `name`, `timestamp`, `details`, `messageType`, `siteHierarchyId`, `siteHierarchy`, `deviceFamily`, `networkDeviceId`, `networkDeviceName`, `managementIpAddress`) would be part of the response.\n Examples:\n\n`attribute=name` (single attribute requested)\n\n`attribute=name&attribute=networkDeviceName` (multiple attribute requested)\n"
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            enum:
            - affectedClients
            - apMac
            - apRadioOperationState
            - apRole
            - apSwitchId
            - apSwitchName
            - assocRssi
            - assocSnr
            - auditSessionId
            - authServerIp
            - bssid
            - candidateAPs
            - childEvents
            - clientMac
            - connectedInterfaceName
            - currentRadioPowerLevel
            - details
            - deviceFamily
            - dhcpServerIp
            - duid
            - eventStatus
            - facility
            - failureCategory
            - failureIpAddress
            - frequency
            - id
            - identifier
            - invalidIeAPs
            - ipv4
            - ipv6
            - isPrivateMac
            - lastApDisconnectReason
            - lastApResetType
            - managementIpAddress
            - messageType
            - missingResponseAPs
            - mnemonic
            - name
            - networkDeviceId
            - networkDeviceName
            - newRadioChannelList
            - newRadioChannelWidth
            - oldRadioChannelList
            - oldRadioChannelWidth
            - previousRadioPowerLevel
            - radioChannelSlot
            - radioChannelUtilization
            - radioInterference
            - radioNoise
            - reasonDescription
            - replacedDeviceSerialNumber
            - replacingDeviceSerialNumber
            - resultStatus
            - roamType
            - severity
            - siteHierarchy
            - siteHierarchyId
            - ssid
            - subReasonDescription
            - switchNumber
            - timestamp
            - udnId
            - udnName
            - username
            - vlanId
            - wirelessClientEventEndTime
            - wirelessClientEventStartTime
            - wlcId
            - wlcName
      - name: view
        in: query
        description: "The list of events views. Please refer to `EventViews` for the supported list\n Examples:\n\n`view=network` (single view requested)\n\n`view=network&view=ap` (multiple view requested)\n"
        style: form
        explode: true
        schema:
          type: array
          items:
            type: string
            enum:
            - basic
            - network
            - ap
            - wiredClient
            - wirelessClient
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database. It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: ui:client360
      responses:
        '200':
          description: Event details for the given identifier
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/EventDetailResponse'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: The client made a request for a resource that does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
  /dna/data/api/v1/assuranceEvents/{id}/childEvents:
    get:
      tags:
      - assuranceEvents
      summary: Get list of child events for the given wireless client event
      description: Wireless client event could have child events and this API can be used to fetch the same using parent event `id` as the input.
      operationId: readEventChildren
      parameters:
      - name: id
        in: path
        description: Unique identifier for the event
        required: true
        style: simple
        explode: false
        schema:
          type: string
      - name: X-CALLER-ID
        in: header
        description: 'Caller ID is used to trace the origin of API calls and their associated queries executed on the database. It''s an optional header parameter that can be added to an API request.

          '
        required: false
        schema:
          type: string
          default: unknown
        example: ui:client360
      responses:
        '200':
          description: List of child events for the given identifier
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/EventChildEventsResponse'
        '400':
          description: The client made a request that the server could not understand (for example, the request syntax is incorrect).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: The client made a request for a resource that does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: The server could not fulfill the request due to internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        1XX:
          description: Informational Responses - The server received the request and sent an informational response.
        2XX:
          description: Successful Responses - The server received the client request, understood it, and accepted it.
        3XX:
          description: Redirection Messages - The client must take additional action to complete the request.
        4XX:
          description: Client Error Responses - The client request caused the error.
        5XX:
          description: Server Error Responses - The server failed to fulfill the request.
        default:
          description: Unexpected Error
  /dna/data/api/v1/assuranceEvents/query:
    post:
      tags:
      - assuranceEvents
      summary: Query assurance events with filters
      description: "Returns the list of events discovered by Catalyst Center, determined by the complex filters.\n\n**The input payload contains the following fields:**\n\n| Field Name              | Description                    |\n| ----------------------  | ------------------------------ |\n| `startTime`             | Start time from which API queries the data set re

# --- truncated at 32 KB (101 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cisco-catalyst-center/refs/heads/main/openapi/cisco-catalyst-center-assuranceevents-api-openapi.yml