How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cisco Secure Firewall

Cisco Secure Firewall Troubleshoot API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

Cisco Secure Firewall Troubleshoot API is one of 108 APIs that Cisco Secure Firewall publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Troubleshoot. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 18 operations across 12 paths, and defines 41 schemas. It is described by OpenAPI 3.2.0, at version 1.13.0.

Requests are made against 9 base URLs: https://api.us.security.cisco.com/firewall, https://api.eu.security.cisco.com/firewall, https://api.apj.security.cisco.com/firewall, https://api.au.security.cisco.com/firewall, https://api.in.security.cisco.com/firewall, https://api.int.security.cisco.com/firewall, https://scale.manage.security.cisco.com/api/rest, https://ci.manage.security.cisco.com/api/rest, https://manage.stg.secure.cisco/api/rest.

18 operations 12 paths 41 schemas 2 DELETE9 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.13.0
Base URL
https://api.us.security.cisco.com/firewall
Authentication
HTTP Bearer
Contact
Cisco Firepower TAC
Resource Areas
1

Authentication & Security 1

Cisco Secure Firewall Troubleshoot API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 18

Across 12 paths, the API surfaces 18 operations — 2 DELETE, 9 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Troubleshoot 18
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules
Get all CPU profiling data of a Snort3 module on a given device.
getAllCPUProfiler 6 params → 200default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules
Create the CPU profiling data of a Snort3 module on a given device. Check the response section for applicable examples (if any).
createCPUProfiler 2 params body → 202default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/cpuprofiler/{containerUUID}/modules/{profilerFileName}
Get the CPU Profiling data of Snort modules from the specified profiler file.
getCPUProfiler 3 params → 200default
DELETE
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files
Delete all PCAP files from the Firewall Management Center. Check the response section for applicable examples (if any).
deleteMultiplePacketTracerPCAPFiles 3 params → 200default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files
Get all PCAP files from the Firewall Management Center.
getAllPacketTracerPCAPFiles 4 params → 200default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files
Create a PCAP file on the Firewall Management Center. Check the response section for applicable examples (if any).
createPacketTracerPCAPFiles 1 param body → 201default
DELETE
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}
Delete the specified PCAP file from the Firewall Management Center. Check the response section for applicable examples (if any).
deletePacketTracerPCAPFiles 2 params → 200default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}
Get the specified PCAP file from the Firewall Management Center.
getPacketTracerPCAPFiles 2 params → 200default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/files/{pcapFileName}/details
Get the packet details from a PCAP file.
getPacketTracerPCAPExtract 5 params → 200default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/pcaptraces
Get the Packet Tracer using a PCAP file command output for Firewall Threat Defense. Check the response section for applicable examples (if any).
createPacketTracerPCAP 1 param body → 201default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/packettracer/traces
Get the Packet Tracer command output for a Firewall Threat Defense or Cluster. Check the response section for applicable examples (if any).
createPacketTracer 1 param body → 202default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/radkit/services
Get all RADKit Service data from the FMC.
getAllRADKitService 4 params → 200default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/radkit/services
Creates the RADKit Service on the FMC. Check the response section for applicable examples (if any).
createRADKitService 1 param body → 202default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/radkit/services/{id}
Get the RADKit Service data from the specified ID.
getRADKitService 2 params → 200default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/snortprofiler/{containerUUID}/rules
Get all Snort Rule Profiling data for a given device.
getAllSnortProfiler 6 params → 200default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/snortprofiler/{containerUUID}/rules
Create Snort Rule Profiling data for a given device. Check the response section for applicable examples (if any).
createSnortProfiler 2 params body → 202default
GET
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/snortprofiler/{containerUUID}/rules/{profilerFileName}
Get the Snort rule profiling data from the specified profiler file.
getSnortProfiler 3 params → 200default
POST
/v1/cdfmc/api/fmc_troubleshoot/v1/domain/{domainUUID}/troubleshoot/device
Trigger troubleshooting for chassis models 3100 and 4200. Check the response section for applicable examples (if any).
createDeviceTroubleshoot 1 param body → 202default

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are PacketTracer (29 properties), CPUProfiler (21 properties), SnortProfiler (21 properties), PacketTracerPCAPExtract (15 properties). Each schema is shown below with its type and property counts.

PacketTracerPCAPExtract
object
Represents the extracted packet details of a PCAP file.
15 properties
IPacketTracerUnitDetails
object
Represents the Packet Tracer Cluster Unit Details.
3 properties
CPUProfilerModule
object
Object representing a Snort module returned by the CPU Profiler.
8 properties
IPacketTracerPhase
object
Represents the Packet Tracer Phase section of the CLI output.
7 properties
PacketTracerPCAPFiles
object
Represents handling operations of the PCAP files on FMC for the Packet Tracer feature.
11 properties
ITroubleshootableDevice
object
9 properties
RADKitServiceListContainer
object
3 properties
IReadonly
object
2 properties
IPacketTracerDeviceResponse
object
Represents the device response for both FTD and Cluster.
4 properties
PacketTracerPCAPExtractListContainer
object
3 properties
ILinks
object
This defines the self referencing links for the given resource.
2 properties
ErrorMessagesContainer
object
7 properties
DeviceTroubleshoot
object
A model representing device troubleshoot attributes
8 properties
TroubleshootMetadata
object
7 properties
CPUProfiler
object
Represents the CPU Profiler of the Snort modules.
21 properties
CPUProfilerListContainer
object
3 properties
IMetadataUser
object
4 properties
IDomain
object
4 properties
SnortProfiler
object
Snort Rule Profiler
21 properties
Domain
object
The details about the domain.
5 properties
ISubTask
object
6 properties
IPacketTracerResult
object
Represents the Packet Tracer Result section of the CLI output.
10 properties
PagingContainer
object
4 properties
PacketTracerPCAP
object
Represents the Trace operation using a PCAP file on the Packet Tracer feature.
12 properties
SnortProfilerMetadata
object
7 properties
ITarget
object
This is the target device.
7 properties
ReadOnly
object
Defines the read only conditions if the referenced resource is read only.
2 properties
TaskStatus
object
11 properties
IPacketTracerPCAPDetails
object
Represents the packet details.
2 properties
IMetadata
object
6 properties
Metadata
object
Defines read only details about the object - whether it is system defined, last user who modified the object etc.
6 properties
MetadataUser
object
This object defines details about the user.
4 properties
IPacketTracerPCAPPackets
object
Represents the object structure of the packets after the Trace operation using a PCAP file on the Packet Tracer feature is run.
5 properties
SnortProfilerListContainer
object
3 properties
PacketTracerPCAPFilesListContainer
object
3 properties
LLFilesMap
object
PacketTracer
object
Represents the Trace operation on the Packet Tracer feature.
29 properties
IReference
object
Contains reference information.
4 properties
ErrorResponse
object
3 properties
RADKitService
object
Cisco Remote Automation Development Kit Service
11 properties
SnortProfilerRule
object
14 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-troubleshoot-api-openapi.yml Raw ↑

Other APIs Cisco Secure Firewall publishes across the network.

Cisco Secure Firewall Access Groups API
AE Profile APIs.io
Cisco Secure Firewall Access Token API
AE Profile APIs.io
Cisco Secure Firewall Action API
AE Profile APIs.io
Cisco Secure Firewall Adjacent Zone API
AE Profile APIs.io
Cisco Secure Firewall AI Assistant API
AE Profile APIs.io
Cisco Secure Firewall Analysis API
AE Profile APIs.io
Cisco Secure Firewall API Entitlement API
AE Profile APIs.io
Cisco Secure Firewall API Keys API
AE Profile APIs.io
Cisco Secure Firewall App Group API
AE Profile APIs.io
Cisco Secure Firewall ASA Access Rules API
AE Profile APIs.io
Cisco Secure Firewall Audit API
AE Profile APIs.io
Cisco Secure Firewall Audit Logs API
AE Profile APIs.io
#Troubleshoot
← Back to C APIs
API Details
ID
cisco-secure-firewall:cisco-secure-firewall-troubleshoot-api
Base URL
https://api.us.security.cisco.com/firewall
Docs
https://developer.cisco.com/docs/cisco-security-cloud-control-firewall-manager/cdfmc-api-overview/
Provider
Cisco Secure Firewall
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cisco-secure-firewall-troubleshoot-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-secure-firewall-troubleshoot-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cisco Secure Firewall Troubleshoot API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.