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 Request API

The Request API from Cisco Secure Firewall — 12 operation(s) for request.

Cisco Secure Firewall Request 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 Request. 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 12 operations across 12 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 6.0.0.

Requests are made against a single base URL, https://api.security.cisco.com/pinacl/api.

12 operations 12 paths 18 schemas 9 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
6.0.0
Base URL
https://api.us.security.cisco.com/firewall
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Cisco Secure Firewall Request API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (jwt) (BearerJWT). By default, every request must be authenticated.

Paths & Operations 12

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

Request 12
GET
/mpm/requests/{requestId}
Get request details
getRequest 1 param → 200400401403404500
GET
/mpm/requests/{requestId}/status
Get request status
getRequestStatus 1 param → 200400401403404500
GET
/pcm/requests/child-requests/{requestId}/status
Get request status and its child request statuses
getRequestAndChildrenStatuses 1 param → 200400401403404500
POST
/pcm/requests/status
Get PCM request status by request ids
getPcmRequestStatusesBulk body → 200400401403404413500
GET
/pcm/requests/{requestId}
Get PCM request details
getRequest_1 1 param → 200400401403404500
PATCH
/pcm/requests/{requestId}/manual/status/complete
Complete PCM manual request status
completePcmManualRequestStatus 1 param → 204400401403404500
GET
/pcm/requests/{requestId}/status
Get PCM request status
getRequestStatus_1 1 param → 200400401403404500
PATCH
/pcm/requests/{requestId}/status/complete
Complete PCM request status
completePcmRequestStatus 1 param → 204400401403404500
GET
/topology/requests/child-requests/{requestId}
Get child request ids
getChildRequestIds 1 param → 200400401403404500
GET
/topology/requests/child-requests/{requestId}/status
Get request status and its child request statuses
getRequestWithChildren 1 param → 200400401403404500
GET
/topology/requests/{requestId}
Get request details
getRequest1 1 param → 200400401403404500
GET
/topology/requests/{requestId}/status
Get request status
getRequestStatus1 1 param → 200400401403404500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are MpmRequest (11 properties), PcmRequest (10 properties), RequestStatusResponse (9 properties), SdiRequest (8 properties). Each schema is shown below with its type and property counts.

ChildRequestApi
object
2 properties
RequestingSystemRequestDetails
object
8 properties
PcmRequest
object
10 properties
MpmRequest
object
11 properties
RequestStatusResponse
object
9 properties
RequestsResponse
object
1 property
TopologyChangeRequest
object
5 properties
RequestAndChildrenStatusesResponse
object
2 properties
FullRequestDetails
object
7 properties
SdiRequest
object
8 properties
PushGatewayRequest
object
5 properties
RequestStatusResponses
object
1 property
ChildRequestsResponse
object
1 property
ChildRequestStatusResponse
object
2 properties
MpmGovernancePolicyDynamicGroupRequest
object
5 properties
GatewaySetDetails
object
3 properties
ApiRequest
object
1 property
ZoneTopologyRequest
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-request-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 Request 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.