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 Change Management API

The Change Management API from Cisco Secure Firewall — 4 operation(s) for change management.

Cisco Secure Firewall Change Management 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 Change Management. 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 6 operations across 4 paths, and defines 29 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.

6 operations 4 paths 29 schemas 4 GET1 POST1 PUT

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 Change Management API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Change Management 6
GET
/v1/cdfmc/api/fmc_config/v1/domain/{domainUUID}/changemanagement/tickets
Get all the tickets for the logged in user.
getAllTicket 6 params → 200default
POST
/v1/cdfmc/api/fmc_config/v1/domain/{domainUUID}/changemanagement/tickets
Create a change management ticket. Check the response section for applicable examples (if any).
createTicket 1 param body → 201default
GET
/v1/cdfmc/api/fmc_config/v1/domain/{domainUUID}/changemanagement/tickets/{containerUUID}/previewchanges
Get ticket-based changes.
getTicketPreviewChange 6 params → 200default
GET
/v1/cdfmc/api/fmc_config/v1/domain/{domainUUID}/changemanagement/tickets/{containerUUID}/validationresults
Get validation results for the specified ticket.
getTicketValidationResult 5 params → 200default
GET
/v1/cdfmc/api/fmc_config/v1/domain/{domainUUID}/changemanagement/tickets/{objectId}
Get information for the specified ticket.
getTicket 3 params → 200default
PUT
/v1/cdfmc/api/fmc_config/v1/domain/{domainUUID}/changemanagement/tickets/{objectId}
Modify the specified ticket. Check the response section for applicable examples (if any).
updateTicket 2 params body → 200default

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are IBaseDevice (19 properties), TicketPreviewChange (16 properties), TicketValidationResult (13 properties), HealthSetting (13 properties). Each schema is shown below with its type and property counts.

HealthAlertConfig
object
3 properties
HealthSetting
object
13 properties
DialHost
object
2 properties
IAdvanced
object
1 property
TicketValidationResultListContainer
object
3 properties
IReadonly
object
2 properties
IValueUpdate
object
3 properties
ILinks
object
This defines the self referencing links for the given resource.
2 properties
ErrorMessagesContainer
object
7 properties
IPolicyModel
object
7 properties
TicketValidationResult
object
13 properties
IDomain
object
4 properties
HealthThreshold
object
2 properties
HealthModule
object
9 properties
IMetadataUser
object
4 properties
IValueAdd
object
2 properties
PagingContainer
object
4 properties
TicketPreviewChangeListContainer
object
3 properties
IValueDelete
object
2 properties
ITicketHistory
object
Contains history of the change management ticket.
4 properties
IImpactedDevice
object
5 properties
IReferenceUpdate
object
3 properties
TicketPreviewChange
object
16 properties
TicketListContainer
object
3 properties
IMetadata
object
6 properties
Ticket
object
Contains the change management ticket data.
12 properties
IHealthPolicy
object
Description of Health Policy.
12 properties
ErrorResponse
object
3 properties
IBaseDevice
object
19 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-change-management-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 Change Management 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.