Cisco Intersight · Authentication Profile

Intersight Authentication

Authentication

Cisco Intersight secures its APIs with apiKey, http, and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

InfrastructureCloud OperationsData-CenterComputeNetworkingEnterpriseStorageVirtualizationKubernetesOrchestrationTelemetryFirmware Management
Methods: apiKey, http, oauth2 Schemes: 3 OAuth flows: authorizationCode, clientCredentials API key in: cookie

Security Schemes

cookieAuth apiKey
· in: cookie (X-Starship-Token)
http_signature http
scheme: signature
oAuth2 oauth2
· flows: authorizationCode, clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-08-19'
method: derived
source: openapi/intersight-fabric-openapi.json, openapi/intersight-hyperflex-openapi.json, openapi/intersight-kubernetes-openapi.json,
  openapi/intersight-nexus-insight-advisor-openapi.json, openapi/intersight-orchestrator-openapi.json,
  openapi/intersight-server-openapi.json, openapi/intersight-storage-openapi.json, openapi/intersight-system-openapi.json,
  openapi/intersight-telemetry-openapi.json, openapi/intersight-virtualization-openapi.json,
  openapi/intersight-workflows-openapi.json
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - cookie
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: cookieAuth
  type: apiKey
  in: cookie
  parameter: X-Starship-Token
  description: The authentication cookie obtained from a Single-Sign-On SAML assertion.
  sources:
  - openapi/intersight-fabric-openapi.json
  - openapi/intersight-hyperflex-openapi.json
  - openapi/intersight-kubernetes-openapi.json
  - openapi/intersight-nexus-insight-advisor-openapi.json
  - openapi/intersight-orchestrator-openapi.json
  - openapi/intersight-server-openapi.json
  - openapi/intersight-storage-openapi.json
  - openapi/intersight-system-openapi.json
  - openapi/intersight-telemetry-openapi.json
  - openapi/intersight-virtualization-openapi.json
  - openapi/intersight-workflows-openapi.json
- name: http_signature
  type: http
  scheme: signature
  description: |-
    The 'HTTP signature' security scheme. Each HTTP request is cryptographically signed
    as specified in https://datatracker.ietf.org/doc/draft-cavage-http-signatures/.
    See [Intersight API and SDK documentation](https://intersight.com/apidocs) for details
    about how to configure the HTTP signature scheme.
    You must include the following fields in the signed headers.
      1. '(request-target)'
      1. '(created
  sources:
  - openapi/intersight-fabric-openapi.json
  - openapi/intersight-hyperflex-openapi.json
  - openapi/intersight-kubernetes-openapi.json
  - openapi/intersight-nexus-insight-advisor-openapi.json
  - openapi/intersight-orchestrator-openapi.json
  - openapi/intersight-server-openapi.json
  - openapi/intersight-storage-openapi.json
  - openapi/intersight-system-openapi.json
  - openapi/intersight-telemetry-openapi.json
  - openapi/intersight-virtualization-openapi.json
  - openapi/intersight-workflows-openapi.json
- name: oAuth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: /iam/app-authorize
    tokenUrl: /iam/token
    scopes: 54
  - flow: clientCredentials
    tokenUrl: /iam/token
    scopes: 3315
  description: |-
    The client uses the OAuth2 security scheme. To use OAuth2, a client application
    must be registered by creating a iam.AppRegistration resource.
    The user who creates the iam.AppRegistration resource can specify a list of OAuth2
    scopes. These iam.AppRegistration scopes restricts which subset of scopes
    a registered client can obtain.
    Supported OAuth2 flows are:
    **Authorization Code**
    In the authorizat
  sources:
  - openapi/intersight-fabric-openapi.json
  - openapi/intersight-hyperflex-openapi.json
  - openapi/intersight-kubernetes-openapi.json
  - openapi/intersight-nexus-insight-advisor-openapi.json
  - openapi/intersight-orchestrator-openapi.json
  - openapi/intersight-server-openapi.json
  - openapi/intersight-storage-openapi.json
  - openapi/intersight-system-openapi.json
  - openapi/intersight-telemetry-openapi.json
  - openapi/intersight-virtualization-openapi.json
  - openapi/intersight-workflows-openapi.json

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/intersight-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.