Corridor · Authentication Profile

Corridor Authentication

Authentication

Corridor secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanySecurityApplication SecurityAI CodingCode SecurityDeveloper ToolsGuardrailsMCPStatic AnalysisDevSecOps
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/corridor-openapi.yml
docs: https://docs.corridor.dev/api/reference
summary:
  types:
  - http
  http_schemes:
  - bearer
  token_prefix: cor_
  admin_operations: Require a standard user session; API tokens are rejected for admin operations.
  sso: SSO via Okta available for enterprise accounts (docs.corridor.dev/administration/sso-okta).
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    API token with the `cor_` prefix, generated from Profile > API Tokens in the
    Corridor dashboard (https://app.corridor.dev/settings). Passed as
    `Authorization: Bearer [example key]`. Tokens carry the same access as the user who
    created them but cannot perform admin operations.
  sources:
  - openapi/corridor-openapi.yml