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 Org creation API

The Org creation API from Cisco Secure Firewall — 5 operation(s) for org creation.

Cisco Secure Firewall Org creation 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 Org creation. 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 8 operations across 5 paths, and defines 13 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.

8 operations 5 paths 13 schemas 3 GET1 PATCH3 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 Org creation 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 8

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

Org creation 8
GET
/enterprises
With no parameters, returns the list of enterprises the caller is an administrator of
getEnterprises 2 params → 200default
POST
/enterprises
API to create an enterprise
createEnterprise body → 200default
POST
/enterprises/onboardDomain
Use this method to create an enterprise via a claimed domain. The authenticated user calling this method must have already completed the domain verification process for the domain being sent in the r…
createEnterpriseFromDomain body → 200400
POST
/enterprises/createFromUser
Use this method to create an enterprise by inferring a user from attached Authorization Token. Once the enterprise has been created, the authenticated user will be made an admin of that enterprise.
createEnterpriseFromUser body → 200400default
GET
/enterprises/{id}
Returns a single enterprise
getEnterprise 1 param → 200404default
PUT
/enterprises/{id}
Updates different attributes of an existing enterprise
updateEnterprise 1 param body → 200400404default
GET
/enterprises/{id}/supportAccessStatus
Get the enterprise's support access status
getEnterpriseSupportAccess 2 params → 200404
PATCH
/enterprises/{id}/supportAccessStatus
Update the enterprise's support access status
updateEnterpriseSupportAccess 2 params body → 200404

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are UserEnterprise (10 properties), IdpInputs (8 properties), Enterprise (8 properties), IdpOutputs (5 properties). Each schema is shown below with its type and property counts.

EnterpriseSupportAccessStatusResponse
object
2 properties
IdpOutputs
object
5 properties 5 required
EnterpriseSupportAccessStatusRequest
object
1 property
Domain
object
2 properties 2 required
UpdateEnterpriseRequestBody
object
Represent request body for updating enterprise name, displayName and region, required to have at least one param
4 properties
DetailedEnterprise
object
An extension of enterprise that contains more sensitive metadata that only an admin would be permitted to see.
Error
object
2 properties 2 required
Enterprise
object
Represents a specific enterprise, includes metadata all users associated with the enterprise would be permitted to see.
8 properties 4 required
IdpInputs
object
8 properties 4 required
DomainStatus
string
DomainName
string
UserEnterprise
object
Represents an enterprise and the requesting users role in it
10 properties 3 required
Idp
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-org-creation-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 Org creation 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.