Cycode · Authentication Profile

Cycode Authentication

Authentication

Cycode secures its APIs with apiToken and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials and browser flow(s).

CompanyCybersecurityApplication SecuritySoftware Supply Chain SecurityASPMDevSecOpsSecrets ScanningSASTSCADeveloper ToolsMCPCLI

Methods: apiToken, oauth2 Schemes: 2 OAuth flows: clientCredentials, browser API key in: header

Security Schemes

apiToken apiKey

scheme: bearer · in: header ()

oauth2-cli oauth2

Source

Authentication Profile

generated: '2026-07-18'
method: searched
source: https://docs.cycode.com/
docs: https://docs.cycode.com/
summary:
  types: [apiToken, oauth2]
  api_key_in: [header]
  oauth2_flows: [clientCredentials, browser]
schemes:
  - name: apiToken
    type: apiKey
    in: header
    scheme: bearer
    description: >-
      A Client ID + Client Secret (personal access token) is exchanged for a
      short-lived JWT at POST /api/v1/auth/api-token; the JWT is sent as a
      Bearer token on subsequent Cycode REST API requests.
    sources: [docs.cycode.com]
  - name: oauth2-cli
    type: oauth2
    flow: clientCredentials
    description: >-
      The cycode CLI authenticates with a browser OAuth login (`cycode auth`)
      or with CYCODE_CLIENT_ID / CYCODE_CLIENT_SECRET client credentials.
    sources: [github.com/cycodehq/cycode-cli]