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

The Integrations API from Cisco Secure Firewall — 7 operation(s) for integrations.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cisco Secure Firewall Integrations 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 Integration. 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 10 operations across 7 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

10 operations 7 paths 14 schemas 1 DELETE7 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.us.security.cisco.com/firewall
Authentication
HTTP Bearer
Contact
Sindhu Gopi
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — security scheme

Paths & Operations 10

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

Integrations 10
GET
/integrationHub/details/{integrationType}
Get data to load the ISE integration details page
getIntegrationDetails 2 params → 200400401403404500
GET
/integrationHub/instructions/{integrationType}
Get data to load the add new ISE integration page
getIntegrationInstructions 2 params → 200400401403404500
GET
/integrationHub/integrationApps
Get data to load the integrations hub page
getIntegrationsHubData → 200400401403500
GET
/integrationHub/integrationApps/logo/{integrationType}
Get icon by type
getISEIntegrationIcon 1 param → 200400401403500
GET
/integrations
Get all integrations which are part of provided Enterprise
getAllEnterprisesIntegration 5 params → 200400401403404500
GET
/ise
Get all integrations
getAllIntegrations 4 params → 200400401403500
POST
/ise
Create integrations
createIntegrations 2 params body → 200400401403500
DELETE
/ise/{integrationId}
Deletes an integration
deleteIntegration 3 params → 204400401403404500
GET
/ise/{integrationId}
Fetches an integration
fetchIntegration 3 params → 200400401403404500
PATCH
/ise/{integrationId}
Updates an integration
updateIntegration 3 params body → 204400401403404500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Integration (10 properties), IntegrationDetails (5 properties), 403 (4 properties), IntegrationList (4 properties). Each schema is shown below with its type and property counts.

CreateIntegrationReq
object
Create integration payload object
3 properties 3 required
404
object
Typical 404 response body for Context Service requests
2 properties
400
object
Typical 400 response body for Context Service requests
2 properties
Instruction
object
Main item of IntegrationDetails and CreateIntegrationDetails objects
2 properties 2 required
IntegrationHub
object
IntegrationHub object needed for integration hub page rendering
1 property 1 required
Integration
object
Integration object
10 properties
HelpLink
object
Object needed for Help link components rendering and routing
2 properties 2 required
CreateIntegrationDetails
object
Object needed for create integration related pages and components rendering
2 properties 2 required
401
object
Typical 401 response body for Context Service requests
4 properties
IntegrationDetails
object
Object needed for integration details related pages and components rendering
5 properties 1 required
IntegrationList
object
A page of Integration objects
4 properties
UpdateIntegrationReq
object
Update integration payload object
2 properties
403
object
Typical 403 response body for Context Service requests
4 properties
500
object
Typical 500 response body for Context Service requests
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-integrations-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
#Integration
← Back to C APIs
API Details
ID
cisco-secure-firewall:cisco-secure-firewall-integrations-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-integrations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cisco-secure-firewall-integrations-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 Integrations 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.