Cisco Secure Firewall Troubleshoot API

The Troubleshoot API from Cisco Secure Firewall — 12 operation(s) for troubleshoot.

Operations 18

GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules/{profilerFileName} #
DELETE /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files #
DELETE /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName} #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName} #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}/details #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/pcaptraces #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/traces #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/radkit/services #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/radkit/services #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/radkit/services/{id} #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/snortprofiler/{containerUUID}/rules #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/snortprofiler/{containerUUID}/rules #
GET /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/snortprofiler/{containerUUID}/rules/{profilerFileName} #
POST /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/troubleshoot/device #

Work with this as data

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-secure-firewall-troubleshoot-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 Specification

cisco-secure-firewall-troubleshoot-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cisco Secure Firewall Troubleshoot API
  version: 1.13.0
  contact:
    name: Cisco Firepower TAC
    email: ngfw-support@cisco.com
  description: 'Operations tagged Troubleshoot across 2 of this provider''s published API definitions: cdfmc-openapi.yaml, cisco-secure-firewall-cdfmc-openapi.yml. Each path carries the servers of the definition it was published in.'
  x-provenance:
    method: harvested
    first_party: true
    harvested: '2026-08-19'
    source: https://raw.githubusercontent.com/CiscoDevNet/scc-public-api-docs/main/cdo/cdfmc-openapi.yaml
    source_repo: https://github.com/CiscoDevNet/scc-public-api-docs
    note: Verbatim first-party OpenAPI published by Cisco in the CiscoDevNet scc-public-api-docs repository, the source of record for developer.cisco.com/docs/cisco-security-cloud-control-firewall-manager/. Not authored or modified by API Evangelist.
    derived_view: Per-tag view of cisco-secure-firewall-cdfmc-openapi.yml, the provider's source document. Operations and schemas are the provider's, unmodified; only the partition is ours.
    derived_from: cisco-secure-firewall-cdfmc-openapi.yml
    operation_coverage: 18/18
  x-evidence:
    fetched: '2026-08-19'
    url: https://raw.githubusercontent.com/CiscoDevNet/scc-public-api-docs/main/cdo/cdfmc-openapi.yaml
    http_status: 200
servers:
- url: https://api.us.security.cisco.com/firewall
  description: US
- url: https://api.eu.security.cisco.com/firewall
  description: EU
- url: https://api.apj.security.cisco.com/firewall
  description: APJ
- url: https://api.au.security.cisco.com/firewall
  description: AUS
- url: https://api.in.security.cisco.com/firewall
  description: IN
- url: https://api.int.security.cisco.com/firewall
  description: Staging
- url: https://scale.manage.security.cisco.com/api/rest
  description: Scale
- url: https://ci.manage.security.cisco.com/api/rest
  description: CI
- url: https://manage.stg.secure.cisco/api/rest
  description: Stgf9
tags:
- name: Troubleshoot
paths:
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.security.cisco.com/firewall
      description: EU
    - url: https://api.apj.security.cisco.com/firewall
      description: APJ
    - url: https://api.au.security.cisco.com/firewall
      description: AUS
    - url: https://api.in.security.cisco.com/firewall
      description: IN
    - url: https://api.int.security.cisco.com/firewall
      description: Staging
    - url: https://scale.manage.security.cisco.com/api/rest
      description: Scale
    - url: https://ci.manage.security.cisco.com/api/rest
      description: CI
    - url: https://manage.stg.secure.cisco/api/rest
      description: Stgf9
    get:
      deprecated: false
      description: '**Get all CPU profiling data of a Snort3 module on a given device.**'
      operationId: getAllCPUProfiler
      parameters:
      - description: To be used in conjunction with <code>"latest:true"</code> in order to get the latest file of CPU Profiling for the Snort modules.
        in: query
        name: filter
        required: false
        schema:
          type: string
      - description: The container id under which this specific resource is contained.
        in: path
        name: containerUUID
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      - $ref: '#/components/parameters/offset'
        name: offset
      - $ref: '#/components/parameters/limit'
        name: limit
      - $ref: '#/components/parameters/expanded'
        name: expanded
      responses:
        '200':
          content:
            application/json:
              examples:
                ? 'Example 1 : GET /api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules?filter=latest:true ( GET ALL CPU Profiler data filter latest )'
                : value:
                    items:
                    - accessPolicyExported: 10:47:35 04-19-2023
                      accessPolicyName: ACP1
                      endTime: 18:07:45 05-09-2023
                      lsp: lsp-rel-20230417-1250
                      modules:
                      - avgCheckUs: 800779
                        callerPercentage: 96.49
                        checks: 20
                        layer: 1
                        name: daq
                        number: 1
                        timeUs: 16015584.0
                        totalPercentage: 96.49
                      - avgCheckUs: 3
                        callerPercentage: 0
                        checks: 16
                        layer: 1
                        name: firewall
                        number: 3
                        timeUs: 51
                        totalPercentage: 0
                      profilerFileName: cpu_profiling.1778474701.json
                      snortVersion: 3.1.53.0-15
                      startTime: 17:07:45 05-09-2023
                      status: DISABLED
                      swBuild: '1129'
                      swVersion: 7.5.0
                      type: CPUProfiler
                      vdb: '361'
                    links:
                      self: https://u45c01p14-vrouter.cisco.com:32826/api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/cpuprofiler/b1f91ce0-a158-11ed-9bf8-a640b790b57e/modules?filter=latest:true
                    paging:
                      count: 1
                      limit: 0
                      offset: 0
                      pages: 1
              schema:
                $ref: '#/components/schemas/CPUProfilerListContainer'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
    post:
      deprecated: false
      description: '**Create the CPU profiling data of a Snort3 module on a given device. _Check the response section for applicable examples (if any)._**'
      operationId: createCPUProfiler
      parameters:
      - description: The container id under which this specific resource is contained.
        in: path
        name: containerUUID
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      requestBody:
        content:
          application/json:
            examples:
              ? 'Example 1 : POST /api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/cpuprofiler/b1f91ce0-a158-11ed-9bf8-a640b790b57e/modules ( POST request to start CPU Profiler )'
              : value:
                  duration: 23
                  status: ENABLED
                  type: CPUProfiler
              ? 'Example 2 : POST /api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/cpuprofiler/b1f91ce0-a158-11ed-9bf8-a640b790b57e/modules ( POST request to stop CPU Profiler )'
              : value:
                  status: DISABLED
                  type: CPUProfiler
            schema:
              $ref: '#/components/schemas/CPUProfiler'
              type: object
        description: The input for CPU Profiling of Snort modules.
        required: true
      responses:
        '202':
          content:
            application/json:
              examples:
                ? 'Example 1 : POST /api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/cpuprofiler/b1f91ce0-a158-11ed-9bf8-a640b790b57e/modules ( POST request to start CPU Profiler )'
                : value:
                    message: CPU profiling started. Output file (cpu_profiling.1778474702.json) will be generated in 23 minutes.
                    metadata:
                      task:
                        id: '78799348373'
                        message: CPU Profiler generation job is started for device1 (b1f91ce0-a158-11ed-9bf8-a640b790b57e)
                        status: RUNNING
                        taskType: CPU_Profiler
                        type: TaskStatus
                    profilerFileName: cpu_profiling.1778474702.json
                    status: ENABLED
                    type: CPUProfiler
                ? 'Example 2 : POST /api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/cpuprofiler/b1f91ce0-a158-11ed-9bf8-a640b790b57e/modules ( POST request to stop CPU Profiler )'
                : value:
                    message: CPU Modules profiling disabled
                    status: DISABLED
                    type: CPUProfiler
              schema:
                $ref: '#/components/schemas/CPUProfiler'
                type: object
          description: Accepted
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules/{profilerFileName}:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.security.cisco.com/firewall
      description: EU
    - url: https://api.apj.security.cisco.com/firewall
      description: APJ
    - url: https://api.au.security.cisco.com/firewall
      description: AUS
    - url: https://api.in.security.cisco.com/firewall
      description: IN
    - url: https://api.int.security.cisco.com/firewall
      description: Staging
    - url: https://scale.manage.security.cisco.com/api/rest
      description: Scale
    - url: https://ci.manage.security.cisco.com/api/rest
      description: CI
    - url: https://manage.stg.secure.cisco/api/rest
      description: Stgf9
    get:
      deprecated: false
      description: '**Get the CPU Profiling data of Snort modules from the specified profiler file.**'
      operationId: getCPUProfiler
      parameters:
      - description: The name of the file containing the CPU Profiling data.
        in: path
        name: profilerFileName
        required: true
        schema:
          type: string
      - description: The container id under which this specific resource is contained.
        in: path
        name: containerUUID
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      responses:
        '200':
          content:
            application/json:
              examples:
                ? 'Example 1 : GET /api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules/{profilerFileName} ( GET CPUProfiler by file name )'
                : value:
                    accessPolicyExported: 10:47:35 04-19-2023
                    accessPolicyName: ACP1
                    endTime: 18:07:45 05-09-2023
                    links:
                      self: https://u45c01p14-vrouter.cisco.com:32826/api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/cpuprofiler/b1f91ce0-a158-11ed-9bf8-a640b790b57e/modules/cpu_profiling.1778474701.json
                    lsp: lsp-rel-20230417-1250
                    modules:
                    - avgCheckUs: 800779
                      callerPercentage: 96.49
                      checks: 20
                      layer: 1
                      name: daq
                      number: 1
                      timeUs: 16015584.0
                      totalPercentage: 96.49
                    - avgCheckUs: 3
                      callerPercentage: 0
                      checks: 16
                      layer: 1
                      name: firewall
                      number: 3
                      timeUs: 51
                      totalPercentage: 0
                    snortVersion: 3.1.53.0-15
                    startTime: 17:07:45 05-09-2023
                    status: DISABLED
                    swBuild: '1129'
                    swVersion: 7.5.0
                    type: CPUProfiler
                    vdb: '361'
              schema:
                $ref: '#/components/schemas/CPUProfiler'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.security.cisco.com/firewall
      description: EU
    - url: https://api.apj.security.cisco.com/firewall
      description: APJ
    - url: https://api.au.security.cisco.com/firewall
      description: AUS
    - url: https://api.in.security.cisco.com/firewall
      description: IN
    - url: https://api.int.security.cisco.com/firewall
      description: Staging
    - url: https://scale.manage.security.cisco.com/api/rest
      description: Scale
    - url: https://ci.manage.security.cisco.com/api/rest
      description: CI
    - url: https://manage.stg.secure.cisco/api/rest
      description: Stgf9
    delete:
      deprecated: false
      description: '**Delete all PCAP files from the Firewall Management Center. _Check the response section for applicable examples (if any)._**'
      operationId: deleteMultiplePacketTracerPCAPFiles
      parameters:
      - description: Boolean indicating whether this is a bulk operation.
        in: query
        name: bulk
        required: true
        schema:
          type: boolean
      - description: To be used in conjunction with <code>bulk=true</code> for bulk deletion. Various filter criteria can be specified using the format:<br><code>pcapFileNames:file1,file2,file3...</code> will delete only the PCAP files provided in the list.<br><code>deleteAllFiles:true</code> will delete all the PCAP files.
        in: query
        name: filter
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      responses:
        '200':
          content:
            application/json:
              examples:
                ? 'Example 1 : DELETE /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName} ( Example of Packet Tracer PCAP delete file. )'
                : value:
                    deleteAllFiles: ''
                    files:
                    - UDP-ipv6.pcap
                    links:
                      self: /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/UDP-ipv6.pcap
                    pcapFileNames: ''
                ? 'Example 2 : DELETE /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files?filter=deleteAllFiles:true ( Example of bulk delete of Packet Tracer PCAP files. )'
                : value:
                    deleteAllFiles: 'true'
                    files:
                    - UDP-ipv6.pcap
                    - TCP_address_withdrawal_ldp.pcapng
                    - UDPipv4.pcap
                    links:
                      self: /api/fmc_troubleshoot/v1/domain/DomainUUID/packettracer/files?filter=deleteAllFiles:true
                    pcapFileNames: ''
              schema:
                $ref: '#/components/schemas/PacketTracerPCAPFiles'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
    get:
      deprecated: false
      description: '**Get all PCAP files from the Firewall Management Center.**'
      operationId: getAllPacketTracerPCAPFiles
      parameters:
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      - $ref: '#/components/parameters/offset'
        name: offset
      - $ref: '#/components/parameters/limit'
        name: limit
      - $ref: '#/components/parameters/expanded'
        name: expanded
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PacketTracerPCAPFilesListContainer'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
    post:
      deprecated: false
      description: '**Create a PCAP file on the Firewall Management Center. _Check the response section for applicable examples (if any)._**'
      operationId: createPacketTracerPCAPFiles
      parameters:
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      requestBody:
        content:
          multipart/form-data:
            examples:
              'Example 1 : POST /api/fmc_troubleshoot/v1/domain/DomainUUID/packettracer/files ( Example of Packet Tracer PCAP upload. )':
                value:
                  payloadFile: .pcap or .pcapng file
                  replaceFile: true or false
            schema:
              properties:
                payloadFile:
                  description: Select a PCAP file. <code>.pcap and .pcapng</code> are the supported file formats. <code>*required</code>
                  format: binary
                  type: string
                replaceFile:
                  description: Replaces the file on disk if it already exists. This is set to FALSE by default.
                  type: boolean
              type: object
      responses:
        '201':
          content:
            application/json:
              examples:
                'Example 1 : POST /api/fmc_troubleshoot/v1/domain/DomainUUID/packettracer/files ( Example of Packet Tracer PCAP upload. )':
                  value:
                    pcapFileName: GRE.pcap
              schema:
                $ref: '#/components/schemas/PacketTracerPCAPFiles'
                type: object
          description: Created
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.security.cisco.com/firewall
      description: EU
    - url: https://api.apj.security.cisco.com/firewall
      description: APJ
    - url: https://api.au.security.cisco.com/firewall
      description: AUS
    - url: https://api.in.security.cisco.com/firewall
      description: IN
    - url: https://api.int.security.cisco.com/firewall
      description: Staging
    - url: https://scale.manage.security.cisco.com/api/rest
      description: Scale
    - url: https://ci.manage.security.cisco.com/api/rest
      description: CI
    - url: https://manage.stg.secure.cisco/api/rest
      description: Stgf9
    delete:
      deprecated: false
      description: '**Delete the specified PCAP file from the Firewall Management Center. _Check the response section for applicable examples (if any)._**'
      operationId: deletePacketTracerPCAPFiles
      parameters:
      - description: Name of the PCAP file.
        in: path
        name: pcapFileName
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      responses:
        '200':
          content:
            application/json:
              examples:
                ? 'Example 1 : DELETE /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName} ( Example of Packet Tracer PCAP delete file. )'
                : value:
                    deleteAllFiles: ''
                    files:
                    - UDP-ipv6.pcap
                    links:
                      self: /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/UDP-ipv6.pcap
                    pcapFileNames: ''
                ? 'Example 2 : DELETE /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files?filter=deleteAllFiles:true ( Example of bulk delete of Packet Tracer PCAP files. )'
                : value:
                    deleteAllFiles: 'true'
                    files:
                    - UDP-ipv6.pcap
                    - TCP_address_withdrawal_ldp.pcapng
                    - UDPipv4.pcap
                    links:
                      self: /api/fmc_troubleshoot/v1/domain/DomainUUID/packettracer/files?filter=deleteAllFiles:true
                    pcapFileNames: ''
              schema:
                $ref: '#/components/schemas/PacketTracerPCAPFiles'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
    get:
      deprecated: false
      description: '**Get the specified PCAP file from the Firewall Management Center.**'
      operationId: getPacketTracerPCAPFiles
      parameters:
      - description: Name of the PCAP file.
        in: path
        name: pcapFileName
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      responses:
        '200':
          content:
            application/json:
              examples:
                ? 'Example 1 : GET /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files ( Example of Packet Tracer PCAP Files list. )'
                : value:
                    items:
                    - files:
                      - UDP-ipv6.pcap
                      - TCP_address_withdrawal_ldp.pcapng
                      - UDPipv4.pcap
                    links:
                      self: https://ful0026-pod.cisco.com:28991/api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/packettracer/files?offset=0&limit=25
                    paging:
                      count: 1
                      limit: 100
                      offset: 0
                      pages: 1
                ? 'Example 2 : GET /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName} ( Example of Packet Tracer PCAP File list. )'
                : value:
                    items:
                    - files:
                      - udp.pcap
                    links:
                      self: https://ful0026-pod.cisco.com:28991/api/fmc_troubleshoot/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/packettracer/files/udp.pcap
                    paging:
                      count: 1
                      limit: 100
                      offset: 0
                      pages: 1
              schema:
                $ref: '#/components/schemas/PacketTracerPCAPFiles'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}/details:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.security.cisco.com/firewall
      description: EU
    - url: https://api.apj.security.cisco.com/firewall
      description: APJ
    - url: https://api.au.security.cisco.com/firewall
      description: AUS
    - url: https://api.in.security.cisco.com/firewall
      description: IN
    - url: https://api.int.security.cisco.com/firewall
      description: Staging
    - url: https://scale.manage.security.cisco.com/api/rest
      description: Scale
    - url: https://ci.manage.security.cisco.com/api/rest
      description: CI
    - url: https://manage.stg.secure.cisco/api/rest
      description: Stgf9
    get:
      deprecated: false
      description: '**Get the packet details from a PCAP file.**'
      operationId: getPacketTracerPCAPExtract
      parameters:
      - description: The PCAP File Name under which this specific resource is contained.
        in: path
        name: pcapFileName
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      - $ref: '#/components/parameters/offset'
        name: offset
      - $ref: '#/components/parameters/limit'
        name: limit
      - $ref: '#/components/parameters/expanded'
        name: expanded
      responses:
        '200':
          content:
            application/json:
              examples:
                ? 'Example 1 : GET /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}/details ( Packet Tracer PCAP Extract support )'
                : value:
                    items:
                    - destinationIPType: IPv4
                      destinationIPValue: 4.4.4.4
                      destinationPort: 34681
                      protocol: TCP
                      sourceIPType: IPv4
                      sourceIPValue: 3.3.3.3
                      sourcePort: 646
                    links:
                      self: https://ful0026-pod.cisco.com:28991/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/address_withdrawal_ldp.pcapng/details
                    paging:
                      count: 1
                      limit: 100
                      offset: 0
                      pages: 1
              schema:
                $ref: '#/components/schemas/PacketTracerPCAPExtractListContainer'
                type: object
          description: OK
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/pcaptraces:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.security.cisco.com/firewall
      description: EU
    - url: https://api.apj.security.cisco.com/firewall
      description: APJ
    - url: https://api.au.security.cisco.com/firewall
      description: AUS
    - url: https://api.in.security.cisco.com/firewall
      description: IN
    - url: https://api.int.security.cisco.com/firewall
      description: Staging
    - url: https://scale.manage.security.cisco.com/api/rest
      description: Scale
    - url: https://ci.manage.security.cisco.com/api/rest
      description: CI
    - url: https://manage.stg.secure.cisco/api/rest
      description: Stgf9
    post:
      deprecated: false
      description: '**Get the Packet Tracer using a PCAP file command output for Firewall Threat Defense. _Check the response section for applicable examples (if any)._**'
      operationId: createPacketTracerPCAP
      parameters:
      - $ref: '#/components/parameters/domainUUID'
        name: domainUUID
      requestBody:
        content:
          application/json:
            examples:
              'Example 1 : POST /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/pcaptrace ( Packet Tracer PCAP request )':
                value:
                  device:
                    id: 005056B1-FFEF-0ed3-0000-004294968641
                    name: Device_A
                    type: Device
                  interface:
                    id: 005056B1-FFEF-0ed3-0000-004294968640
                    name: Management
                    type: PhysicalInterface
                  pcapFileName: UDP.pcap
            schema:
              $ref: '#/components/schemas/PacketTracerPCAP'
              type: object
        description: Input for Packet Tracer PCAP configuration request.
        required: true
      responses:
        '201':
          content:
            application/json:
              examples:
                'Example 1 : POST /api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/pcaptrace ( Packet Tracer PCAP request )':
                  value:
                    packets:
                    - deviceDetails:
                        id: 3d18ea40-9c32-11eb-964d-dcad50548675
                        name: 192.168.0.155
                        type: Device
                      packetDetails:
                        details: 17:10:07.123456 input WAN tcp 1.1.1.1 1111 2.2.2.2 ssh
                        sourceIP: 1.1.1.1
                      packetID: 1
                      phases:
                      - additionalInformation: Found next-hop 203.0.113.129 using egress ifc  management(vrfid:0)
                        config: ''
                        elapsedTime: 9000 ns
                        id: 1
                        result: ALLOW
                        subtype: Resolve Egress Interface
                        type: ROUTE-LOOKUP
                      - additionalInformation: ''
                        config: ''
                        elapsedTime: 9000 ns
                        id: 2
                        result: DROP
                        subtype: mgmt-deny-all
                        type: ACCESS-LIST
                      result:
                        action: drop
                        'dropDetail:': 'Drop-location: frame snp_classify_table_lookup:5046 flow (NA)/N'
                        dropReason: (acl-drop) Flow is denied by configured rule
                        inputInterface: management(vrfid:0)
                        inputLineStatus: up
                        inputStatus: up
                        outputInterface: management(vrfid:0)
                        outputLineStatus: up
                        outputStatus: up
                        time-taken: 30381 ns
                    - deviceDetails:
                        id: 3d18ea40-9c32-11eb-964d-dcad50548675
                        name: 192.168.0.155
                        type: Device
                      packetDetails:
                        details: 17:10:07.123456 input WAN tcp 3.3.3.3 1111 4.4.4.4 ssh
                        sourceIP: 3.3.3.3
                      packetID: 2
                      phases:
                      - additionalInformation: Found next-hop 203.0.113.129 using egress ifc  management(vrfid:0)
                        config: ''
                        elapsedTime: 9000 ns
                        id: 1
                        result: ALLOW
                        subtype: Resolve Egress Interface
                        type: ROUTE-LOOKUP
                      - additionalInformation: ''
                        config: ''
                        elapsedTime: 9000 ns
                        id: 2
                        result: DROP
                        subtype: mgmt-deny-all
                        type: ACCESS-LIST
                      result:
                        action: drop
                        'dropDetail:': 'Drop-location: frame snp_classify_table_lookup:5046 flow (NA)/N'
                        dropReason: (acl-drop) Flow is denied by configured rule
                        inputInterface: management(vrfid:0)
                        inputLineStatus: up
                        inputStatus: up
                        outputInterface: management(vrfid:0)
                        outputLineStatus: up
                        outputStatus: up
                        time-taken: 30381 ns
                    pcapErrorMessage: ''
              schema:
                $ref: '#/components/schemas/PacketTracerPCAP'
                type: object
          description: Created
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
                type: object
          description: Error
      tags:
      - Troubleshoot
  /v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/traces:
    servers:
    - url: https://api.us.security.cisco.com/firewall
      description: US
    - url: https://api.eu.

# --- truncated at 32 KB (93 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/cisco-secure-firewall/refs/heads/main/openapi/cisco-secure-firewall-troubleshoot-api-openapi.yml