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 Domains and Identity providers API

The Domains and Identity providers API from Cisco Secure Firewall — 4 operation(s) for domains and identity providers.

Cisco Secure Firewall Domains and Identity providers 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 Domains and Identity providers. 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 10 schemas. It is described by OpenAPI 3.2.0, at version 1.4.0.

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

6 operations 4 paths 10 schemas 2 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.4.0
Base URL
https://api.us.security.cisco.com/firewall
Authentication
OpenID Connect, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Cisco Secure Firewall Domains and Identity providers API declares 3 security schemes for authenticating requests. It supports OpenID Connect (OpenID) discovered at https://auth.example.com/.well-known/openid-configuration. It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (piamServiceTokenSecurity) using the clientCredentials flow, exposing 11 scopes. By default, every request must be authenticated.

Paths & Operations 6

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

Domains and Identity providers 6
POST
/enterprises/{id}/domains/{domain}/verify
Will trigger the backend to attempt to verify the domain for the enterprise
verifyPendingEnterpriseDomain 2 params → 201400404default
GET
/enterprises/{id}/domains
Reads from the domains table first to see if it has any verified domains. If such a one exists, it returns that domain. Else this API will read from the pendingdomains table and return all the unveri…
getEnterpriseDomains 1 param → 200404default
POST
/enterprises/{id}/domains
Will begin the domain verification process for the enterprise. Action needs to done by the admin of the enterprise
initiatePendingEnterpriseDomain 1 param body → 201400default
PUT
/enterprises/{id}/groupMappings
Create or update an IDP group mapping, if a set of group mappings exist for the IDP already, this should be updated in-place. Requires enterprise admin to invoke this endpoint.
createIdpGroupMapping 1 param body → 200default
GET
/enterprises/{id}/authorizedExternalIdps
List authorize external IdP for this enterprise. Requires enterprise admin to invoke this endpoint.
listExternalIdp 1 param → 200default
POST
/enterprises/{id}/authorizedExternalIdps
Authorize external IdP for this enterprise. Requires enterprise admin to invoke this endpoint.
addExternalIdp 1 param body → 201default

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are PendingDomain (7 properties), ExternalIdpGroupMappingListResponse (4 properties), ExternalIdpGroupMappingCreateResponse (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

IDPGroupMappingInput
object
Represent request body for idp group operation
1 property 1 required
ExternalIdpGroupMappingListResponse
object
4 properties
UpdatedIDPGroupMapping
object
2 properties
Error
object
2 properties 2 required
PendingDomain
object
7 properties 2 required
ExternalIdpGroupMappingCreateResponse
object
3 properties
DomainStatus
string
DomainName
string
ExternalIdpGroupMappingInput
object
Request body for authorizedExternalIdps endpoint
1 property
Domain
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-domains-and-identity-providers-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 Domains and Identity providers 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.