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

Cisco Secure Firewall Inventory API

The Inventory API from Cisco Secure Firewall — 26 operation(s) for inventory.

Cisco Secure Firewall Inventory 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 Inventory. 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 34 operations across 26 paths, and defines 57 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.

34 operations 26 paths 57 schemas 4 DELETE10 GET4 PATCH16 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
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 34

Across 26 paths, the API surfaces 34 operations — 4 DELETE, 10 GET, 4 PATCH, 16 POST. Each is listed below with its method, path, parameters, and response codes.

Inventory 34
GET
/v1/inventory/devices
Get Devices
getDevices 4 params → 200400401403405500
DELETE
/v1/inventory/devices/{deviceUid}
Delete Device
deleteDevice 1 param → 204400401403405500
GET
/v1/inventory/devices/{deviceUid}
Get Device
getDevice 1 param → 200400401403404405500
PATCH
/v1/inventory/devices/{deviceUid}
Modify Device
modifyDevice 1 param body → 200400401403404405500
POST
/v1/inventory/devices/asas
Onboard ASA device
onboardAsaDevice body → 202400401403404500
GET
/v1/inventory/devices/asas/{deviceUid}/configs
Get ASA configuration details
getAsaConfiguration 1 param → 200400401403500
POST
/v1/inventory/devices/asas/{deviceUid}/deploy
Deploy ASA device changes
deployAsaDeviceChanges 1 param → 202400401403404500
POST
/v1/inventory/devices/asas/{deviceUid}/read
Read ASA device configuration
readAsaDeviceConfiguration 1 param → 202400401403500
POST
/v1/inventory/devices/asas/{deviceUid}/reconnect
Reconnect ASA device
reconnectAsaDevice 1 param → 202400401403500
POST
/v1/inventory/devices/asas/acceptCert
Accept certificates for multiple ASA devices
bulkAcceptAsaCertificates body → 202400401403500
POST
/v1/inventory/devices/asas/read
Read configurations for multiple ASA devices
bulkReadAsaDeviceConfigurations body → 202400401403500
POST
/v1/inventory/devices/duoAdminPanels
Onboard Duo Admin Panel
createDuoAdminPanel body → 202400401403500
POST
/v1/inventory/devices/ftds
Onboard FTD device
createFtdDevice body → 202400401403500
POST
/v1/inventory/devices/ftds/{deviceUid}/deploy
(cdFMC-managed FTDs only) Deploy FTD device changes
deployFtdDeviceChanges 1 param body → 202400401403500
POST
/v1/inventory/devices/ftds/cdfmcManaged/{deviceUid}/delete
Delete cdFMC managed FTD device
deleteCdFmcManagedFtdDevice 1 param → 202400401403405500
POST
/v1/inventory/devices/ftds/deploy
(cdFMC-managed FTDs only) Deploy changes to multiple FTD devices
deployChangesToMultipleFtdDevices body → 202400401403500
POST
/v1/inventory/devices/ftds/register
Register FTD device to FMC
finishOnboardingFtdDevice body → 202400401403500
POST
/v1/inventory/devices/ftds/ztp
Onboard FTD device using Zero-Touch Provisioning
onboardFtdDeviceUsingZtp body → 202400401403500
POST
/v1/inventory/devices/ios
Onboard IOS Device
onboardIosDevice body → 202400401403500
GET
/v1/inventory/managers
Get Device Managers
getDeviceManagers 4 params → 200400401403500
DELETE
/v1/inventory/managers/{deviceManagerUid}
Delete Device Manager
deleteDeviceManager 1 param → 204400401403405500
GET
/v1/inventory/managers/{deviceManagerUid}
Get Device Manager
getDeviceManager 1 param → 200400401403404500
PATCH
/v1/inventory/managers/{deviceManagerUid}
Modify Device Manager
modifyDeviceManager 1 param body → 200400401403404500
GET
/v1/inventory/managers/{fmcUid}/health/metrics
Get health metrics on devices managed by the FMC (cdFMC only)
getFmcHealth 2 params → 200400401403405500
POST
/v1/inventory/managers/cdfmc
Provision cdFMC
provisionCdFmc → 202400401403409500
POST
/v1/inventory/managers/mcd
Enable Multicloud Defense
enableMulticloudDefense → 202400401403409500
GET
/v1/inventory/services
Get Cloud Services
getCloudServices 4 params → 200400401403500
DELETE
/v1/inventory/services/{cloudServiceUid}
Delete Cloud Service
deleteCloudService 1 param → 204400401403500
GET
/v1/inventory/services/{cloudServiceUid}
Get Cloud Service
getCloudService 1 param → 200400401403404500
PATCH
/v1/inventory/services/{cloudServiceUid}
Modify Cloud Service
modifyCloudService 1 param body → 200400401403404500
GET
/v1/inventory/templates
Get Template Devices
getTemplateDevices 4 params → 200400401403500
DELETE
/v1/inventory/templates/{templateDeviceUid}
Delete Template Device
deleteTemplateDevice 1 param → 204400401403500
GET
/v1/inventory/templates/{templateDeviceUid}
Get Template Device
getTemplateDevice 1 param → 200400401403404500
PATCH
/v1/inventory/templates/{templateDeviceUid}
Modify Template Device
modifyTemplateDevice 1 param body → 200400401403404500

Schemas 57

The contract defines 57 schemas that model the data the API accepts and returns. The most detailed are Device (44 properties), InterfaceHealthMetrics (16 properties), FmcHealthMetrics (12 properties), CdoTransaction (12 properties). Each schema is shown below with its type and property counts.

CdFmcInfo
object
5 properties
Device
object
44 properties 2 required
ClusterNode
object
4 properties
OnPremFmcInfo
object
3 properties
Labels
object
Labels used to identify/tag Security Cloud Control entities.
2 properties
ConnectorType
string
CommonApiError
object
3 properties
DeviceRole
string
EntityType
string
FtdHaInfo
object
6 properties
BulkOperationAsaDeviceRequest
object
1 property
AsaCreateOrUpdateInput
object
8 properties 4 required
ConnectivityState
string
AuthenticationError
object
2 properties
FmcAccessPolicyReference
object
2 properties
SseDeviceData
object
2 properties
DeviceMetadata
object
2 properties
FtdDeploymentInput
object
3 properties
StateMachineError
object
3 properties
DevicePage
object
4 properties
HaHealthMetrics
object
2 properties
UniversalZtnaSettings
object
5 properties
HaNode
object
5 properties
CpuHealthMetrics
object
3 properties
ConflictDetectionState
string
DiskHealthMetrics
object
1 property
FmcTemplateVariable
object
2 properties 2 required
ZtpOnboardingTemplateConfiguration
object
3 properties 1 required
MemoryHealthMetrics
object
3 properties
S2sVpnTunnelHealthMetrics
object
3 properties
FtdCreateOrUpdateInput
object
7 properties 4 required
InterfaceHealthMetrics
object
16 properties
FmcObjectOverride
object
4 properties 4 required
IosCreateOrUpdateInput
object
7 properties 4 required
ZtpOnboardingInput
object
7 properties 3 required
FtdRegistrationInput
object
2 properties 1 required
CdoTransaction
object
12 properties
ChassisStatsHealthMetrics
object
10 properties
AsaFailoverMode
string
FtdMultiDeviceDeploymentInput
object
4 properties 1 required
FmcDeviceRecord
object
2 properties
SecureAccessMetadata
object
3 properties
ConfigState
string
DuoAdminPanelCreateOrUpdateInput
object
5 properties 3 required
FmcHealthMetrics
object
12 properties
RaVpnSessionHealthMetrics
object
3 properties
DevicePatchInput
object
4 properties
StateMachineDetails
object
2 properties
FtdClusterInfo
object
6 properties
Staged
object
2 properties
AsaFailoverMate
object
4 properties
FmcObjectReference
object
4 properties
AsaConfig
object
2 properties
Deployed
object
2 properties
MerakiDeploymentMode
string
DomainSettings
object
3 properties
Network
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Cisco Secure Firewall publishes across the network.

Cisco Secure Firewall Access Groups API
Cisco Secure Firewall Access Token API
Cisco Secure Firewall Action API
Cisco Secure Firewall Adjacent Zone API
Cisco Secure Firewall AI Assistant API
Cisco Secure Firewall Analysis API
Cisco Secure Firewall API Entitlement API
Cisco Secure Firewall API Keys API
Cisco Secure Firewall App Group API
Cisco Secure Firewall ASA Access Rules API
Cisco Secure Firewall Audit API
Cisco Secure Firewall Audit Logs API
Where this information came from

This is an independent, third-party profile of Cisco Secure Firewall Inventory 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.