Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/cisco-catalyst-center-icap-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: OpenAPI specification for Assurance Intelligent Capture Icap API
description: OpenAPI specification for Assurance Intelligent Capture (ICAP)
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: 3.3.1
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: icap
description: Operations related to Catalyst Center - Assurance Intelligent Capture
externalDocs:
description: Catalyst Center Assurance user guide
url: https://www.cisco.com/c/en/us/support/cloud-systems-management/dna-center/products-user-guide-list.html
paths:
/dna/data/api/v1/icap/captureFiles:
get:
tags:
- icap
summary: Lists ICAP packet capture files matching specified criteria
description: 'Lists the ICAP packet capture (pcap) files matching the specified criteria.
Packet capture file names follow the naming pattern `{macAddress}_{linkType}_{timestamp}.pcap`.
Each type of capture file can only be filtered based on specific MAC address types, as follows:
|Capture Type | MAC Address Type |
| --- | --- |
| `ANOMALY` | Client MAC and/or AP Base Radio MAC |
| `FULL` | Client MAC |
| `ONBOARDING` | Client MAC and/or AP Base Radio MAC |
| `OTA` | AP Base Radio MAC |
At least one MAC address filter must be specified. An error is returned if the capture type and
MAC address(es) specified are incompatible. For `ANOMALY` and `ONBOARDING` capture types, if both
client MAC and AP MAC are specified, then only the capture files that match both criteria are returned.
Note that `ONBOARDING` capture files are created per-AP and contain onboarding packets for multiple
clients attempting to connect to that AP. As a result, when `ONBOARDING` captures are filtered
based on client MAC, the list of capture files returned are the ones that contain packets for the
client of interest (but may also contain packets for other clients as well). Therefore, it may be
necessary to perform additional post-processing of the pcap file after retrieval. Common pcap
analysis tools like Wireshark should also be able to easily display only packets for a certain MAC
address.'
operationId: readIcapCaptureFiles
parameters:
- 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
- name: type
in: query
description: Capture Type
required: true
schema:
type: string
enum:
- FULL
- ONBOARDING
- OTA
- ANOMALY
- name: clientMac
in: query
description: 'The macAddress of client
'
required: false
schema:
type: string
- name: apMac
in: query
description: 'The base radio macAddress of the access point
'
required: false
schema:
type: string
- 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.
'
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.
'
required: false
schema:
type: integer
format: int64
example: 1705435200000
- name: limit
in: query
description: Maximum number of records to return
schema:
maximum: 100
minimum: 1
type: integer
default: 100
- 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: sortBy
in: query
description: A field within the response to sort by.
schema:
type: string
- name: order
in: query
description: The sort order of the field ascending or descending.
schema:
type: string
default: asc
enum:
- asc
- desc
responses:
'200':
$ref: '#/components/responses/CaptureFilesResponseModel'
'400':
$ref: '#/components/responses/400'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/captureFiles/count:
get:
tags:
- icap
summary: Retrieves the total number of packet capture files matching specified criteria
description: 'Retrieves the total number of packet capture files matching the specified criteria.
Packet capture file names follow the naming pattern **{macAddress}_{linkType}_{timestamp}.pcap**.
Each type of capture file can only be filtered based on specific MAC address types, as follows:
|Capture Type | MAC Address Type |
| --- | --- |
| `ANOMALY` | Client MAC or AP Base Radio MAC |
| `FULL` | Client MAC |
| `ONBOARDING` | Client MAC or AP Base Radio MAC |
| `OTA` | AP Base Radio MAC |
At least one MAC address filter must be specified. An error is returned if the capture type and
MAC address(es) specified are incompatible. For `ANOMALY` and `ONBOARDING` capture types, if both
client MAC and AP MAC are specified, then only the capture files that match both criteria are counted.
Note that `ONBOARDING` capture files are created per-AP and contain onboarding packets for multiple
clients attempting to connect to that AP. As a result, when `ONBOARDING` captures are filtered
based on client MAC, the list of capture files returned are the ones that contain packets for the
client of interest (but may also contain packets for other clients as well) and the count returned
is for this list of files.'
operationId: readIcapCaptureFilesCount
parameters:
- 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
- name: type
in: query
description: Capture Type
required: true
schema:
type: string
enum:
- FULL
- ONBOARDING
- OTA
- ANOMALY
- name: clientMac
in: query
description: 'The macAddress of client
'
required: false
schema:
type: string
- name: apMac
in: query
description: 'The base radio macAddress of the access point
'
required: false
schema:
type: string
- 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.
'
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.
'
required: false
schema:
type: integer
format: int64
example: 1705435200000
responses:
'200':
$ref: '#/components/responses/CountIntegerResponse'
'400':
$ref: '#/components/responses/400'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/captureFiles/{id}:
get:
tags:
- icap
summary: Retrieves details of a specific ICAP packet capture file
description: Retrieves details of a specific ICAP packet capture file
operationId: readIcapCaptureFileDetailsById
parameters:
- name: id
in: path
description: 'The name of the packet capture file, as given by the GET /captureFiles API response.
'
required: true
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':
$ref: '#/components/responses/CaptureFileResponseModel'
'400':
$ref: '#/components/responses/400'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/captureFiles/{id}/download:
get:
tags:
- icap
summary: Downloads a specific ICAP packet capture file
description: Downloads a specific ICAP packet capture file
operationId: downloadIcapCaptureFileById
parameters:
- name: id
in: path
description: 'The name of the packet capture file, as given by the GET /captureFiles API response.
'
required: true
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':
$ref: '#/components/responses/DownloadCaptureFileResponseModel'
'400':
$ref: '#/components/responses/400'
'404':
$ref: '#/components/responses/404'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/captureFiles/{id}/analyze:
post:
tags:
- icap
summary: Analyzes a packet capture file
description: 'Analyzes the given packet capture file specified by id of the file. This file should be of type ''ANOMALY'', because currently we are supporting anlysis only for anomaly events. The analysis includes sections such as title, summary, reasoning, highlights, flow and suggested actions. By default all sections are included in the response. We can also request any particular section(s) using `views` field in the request payload.
**The input payload contains the following fields,**
|Field Name | Description |
| --- | --- |
| `clientMacs` | This is used to specify one more client Mac addresses to be analyzed within the given packet capture file. If no Mac is provied, then all the clients that are part of the file will be analyzed. |
| `views` | This is used to specify which section of the analysis need to be included in the response. If this list is empty, then all sections will be included. Refer to `` model for the supported views. |'
operationId: analyzeIcapFile
parameters:
- name: id
in: path
description: 'The name of the packet capture file, as given by the GET /captureFiles API response.
'
required: true
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
requestBody:
$ref: '#/components/requestBodies/CaptureFileAnalysisRequest'
responses:
'200':
$ref: '#/components/responses/CaptureFileAnalysisResponse'
'400':
$ref: '#/components/responses/400'
'404':
$ref: '#/components/responses/404'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/spectrumSensorReports:
get:
tags:
- icap
summary: Retrieves the spectrum sensor reports sent by WLC for provided AP Mac
description: Retrieves the spectrum sensor reports sent by WLC for provided AP Mac
operationId: readIcapSpectrumSensorReportsByApMac
parameters:
- 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
- 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.
'
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.
'
required: false
schema:
type: integer
format: int64
example: 1705435200000
- name: apMac
in: query
description: 'The base ethernet macAddress of the access point
'
required: true
schema:
type: string
- name: dataType
in: query
description: 'Data type reported by the sensor
|Data Type | Description |
| --- | --- |
| `0` | Duty Cycle |
| `1` | Max Power |
| `2` | Average Power |
| `3` | Max Power in dBm with adjusted base of +48 |
| `4` | Average Power in dBm with adjusted base of +48 |
'
required: false
schema:
type: integer
enum:
- 0
- 1
- 2
- 3
- 4
example: 2
- name: limit
in: query
description: Maximum number of records to return
schema:
maximum: 100
minimum: 1
type: integer
default: 100
- 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: timeSortOrder
in: query
description: The sort order of the field ascending or descending.
required: false
schema:
type: string
default: asc
enum:
- asc
- desc
responses:
'200':
$ref: '#/components/responses/SpectrumSensorRawDataQueryResponse'
'400':
$ref: '#/components/responses/400'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/spectrumInterferenceDeviceReports:
get:
tags:
- icap
summary: Retrieves the spectrum interference devices reports sent by WLC for provided AP Mac
description: Retrieves the spectrum interference devices reports sent by WLC for provided AP Mac
operationId: readIcapSpectrumInterferenceDevicesReportsByApMac
parameters:
- 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
- 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.
'
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.
'
required: false
schema:
type: integer
format: int64
example: 1705435200000
- name: apMac
in: query
description: 'The base ethernet macAddress of the access point
'
required: true
schema:
type: string
- name: limit
in: query
description: Maximum number of records to return
schema:
maximum: 100
minimum: 1
type: integer
default: 100
- 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: timeSortOrder
in: query
description: The sort order of the field ascending or descending.
required: false
schema:
type: string
default: asc
enum:
- asc
- desc
responses:
'200':
$ref: '#/components/responses/SpectrumInterferenceDeviceRawDataQueryResponse'
'400':
$ref: '#/components/responses/400'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/intent/api/v1/icap/settings:
get:
tags:
- icap
summary: Fetches ICAP related settings.
description: Use this API operation to get ICAP settings. Optional name and id filters can be passed to filter the results.
operationId: readIcapSettings
parameters:
- 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
- name: id
in: query
description: 'The id of ICAP Settings
'
required: false
schema:
maxItems: 10
type: array
items:
type: string
- name: name
in: query
description: 'The name of ICAP Settings
'
required: false
schema:
type: array
items:
type: string
responses:
'200':
$ref: '#/components/responses/IcapSettingsListResponse'
'400':
$ref: '#/components/responses/400'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/intent/api/v1/icap/settings/{id}:
put:
tags:
- icap
summary: Updates ICAP related settings.
description: Use this API to update ICAP settings. Currently the only available setting is to enable or disable Packet Analysis. By default Packet Analysis would be disabled.
operationId: updateIcapSettings
parameters:
- name: id
in: path
description: 'This is the id of the icap settings, which can be fetched thru GET api.
'
required: true
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
requestBody:
$ref: '#/components/requestBodies/IcapSettingsUpdateRequest'
responses:
'200':
$ref: '#/components/responses/IcapSettingsUpdateResponse'
'400':
$ref: '#/components/responses/400'
'404':
$ref: '#/components/responses/404'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/clients/{id}/stats:
post:
tags:
- icap
summary: Retrieves specific client statistics over specified period of time.
description: 'Retrieves the time series statistics of a specific client by applying complex filters. If startTime and endTime are not provided, the API defaults to the last 24 hours.
**The input payload contains the following fields,**
|Field Name | Description |
| --- | --- |
| `startTime` | The start time indicates when the API begins retrieving data related to the resource. It must be specified in the UNIX epoch time format, measured in milliseconds. This value is inclusive, and if left unspecified, the default is 1 day before the endTime. |
| `endTime` | The end time indicates the upper limit until which the API retrieves data related to the resource. It must be defined in the UNIX epoch time format, measured in milliseconds. This value is inclusive, and if left unspecified, the default is the latest available data. |
|`filters`| This is used to specify one or more conditions for filtering the queried data. Refer to `ClientStatsFilterField` model for the supported filters |
|`page`| It includes the **limit, offset, and timeSortOrder** fields. *limit* denotes the number of records to retrieve per page, *offset* signifies the initial data position, and *timeSortOrder* is used sort the response based on the timestamp either in ascending or descending order. |'
operationId: icapClientsRawDataById
parameters:
- name: id
in: path
description: "id is the client mac address. It can be specified in one of the notational conventions \n01:23:45:67:89:AB or 01-23-45-67-89-AB or 0123.4567.89AB and is case insensitive\n"
required: true
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
requestBody:
$ref: '#/components/requestBodies/ClientStatsRawDataQueryRequest'
responses:
'200':
$ref: '#/components/responses/ClientStatsRawDataQueryResponse'
'400':
$ref: '#/components/responses/400'
'404':
$ref: '#/components/responses/404'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
/dna/data/api/v1/icap/radios/{id}/stats:
post:
tags:
- icap
summary: Retrieves specific radio statistics over specified period of time.
description: 'Retrieves the time series statistics of a specific radio by applying complex filters. If startTime and endTime are not provided, the API defaults to the last 24 hours.
**The input payload contains the following fields,**
|Field Name | Description |
| --- | --- |
| `startTime` | The start time indicates when the API begins retrieving data related to the resource. It must be specified in the UNIX epoch time format, measured in milliseconds. This value is inclusive, and if left unspecified, the default is 1 day before the endTime. |
| `endTime` | The end time indicates the upper limit until which the API retrieves data related to the resource. It must be defined in the UNIX epoch time format, measured in milliseconds. This value is inclusive, and if left unspecified, the default is the latest available data. |
|`filters`| This is used to specify one or more conditions for filtering the queried data. Refer to `RadioStatsFilterField` model for the supported filters |
|`page`| It includes the **limit, offset, and timeSortOrder** fields. *limit* denotes the number of records to retrieve per page, *offset* signifies the initial data position, and *timeSortOrder* is used sort the response based on the timestamp either in ascending or descending order. |'
operationId: icapRadiosRawDataById
parameters:
- name: id
in: path
description: 'id is the composite key made of AP Base Ethernet macAddress and Radio Slot Id. Format apMac_RadioId
'
required: true
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
requestBody:
$ref: '#/components/requestBodies/RadioStatsRawDataQueryRequest'
responses:
'200':
$ref: '#/components/responses/RadioStatsRawDataQueryResponse'
'400':
$ref: '#/components/responses/400'
'404':
$ref: '#/components/responses/404'
'500':
$ref: '#/components/responses/500'
1XX:
$ref: '#/components/responses/1XX'
3XX:
$ref: '#/components/responses/3XX'
default:
$ref: '#/components/responses/defaultError'
components:
schemas:
IcapAnalysisFlowResult:
type: object
properties:
frameNumber:
type: integer
description: Packet frame number in the capture
timestamp:
type: number
description: Packet timestamp in seconds
title:
type: string
description: Short title for the flow entry
description:
type: string
description: Human-readable packet description
direction:
type: string
description: Packet direction relative to the client
channelFrequency:
type: integer
description: Channel frequency in MHz
display:
type: boolean
description: Whether the flow entry should be displayed
group:
type:
- integer
- 'null'
description: Optional group identifier for the flow entry
description: Packet flow entry extracted from the analysis
LogicalOperator:
type: string
description: 'Operator to use when attempting to apply a logical conjunction of more than 1 filter
Logical operations include: ''and'', ''or''.
'
enum:
- and
- or
IcapAnalysisReasoningSection:
type: object
properties:
results:
type: string
description: Reasoning of the analysis
jsonResults:
type: string
description: Frame by frame reasoning of the analysis
description: Reasoning section of the analysis
RadioStatsFilters:
maxItems: 10
type: array
description: 'List of filters to apply when querying the data
Filtering on numerical fields (integer, number,etc.) will support the
numerical operators:
[eq, lt, gt, lte, gte]
Filtering on text fields (string), will support the string operators:
[eq, in, notIn, like]
For the list of supported fields, please refer to the RadioFilterField model
model.
'
items:
$ref: '#/components/schemas/RadioStatsFilterObj'
CountIntegerResponse:
title: Count Integer Response
type: object
properties:
response:
$ref: '#/components/schemas/CountIntegerResponse_response'
version:
type: string
description: The version of the response
example: '1.0'
description: Reports
CaptureFileAnalysisRequest:
type: object
properties:
clientMacs:
maxItems: 100
minItems: 1
type: array
description: Optional list of client mac addresses. When omitted or empty, all the clients in the pcap file will be analyzed.
items:
minLength: 1
type: string
views:
uniqueItems: true
type: array
description: 'Optional list of response sections to fetch. When omitted or empty, the API returns all supported sections.
* `metadata` - Meta data of the pcap file analysis.
* `title` - a short natural language title for the detected issue.
* `summary` - a natural language summary of the pcap (a few sentences).
* `reasoning` - a step-by-step analysis of what happened in the pcap.
* `highlights` - a condensed list of the most relevant flow entries.
* `flow` - the ordered packet flow entries retu
# --- truncated at 32 KB (77 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cisco-catalyst-center/refs/heads/main/openapi/cisco-catalyst-center-icap-api-openapi.yml