Sublime Security · Authentication Profile

Sublime Security Authentication

Authentication

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

CompanySecurityEmail SecurityPhishingDetection as CodeThreat DetectionCloud Email SecuritySCIM
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer · in: header ()

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/sublime-security-multitenancy-openapi.json, openapi/sublime-security-platform-openapi.json
docs: https://docs.sublime.security/reference/authentication.md
summary:
  types:
  - http
  scheme: api-key-bearer
  detail: >-
    Static API keys generated under Automate > API on the Sublime dashboard and sent as
    an HTTP Bearer token (`Authorization: Bearer <API key>`). The key is displayed only
    once at creation. No OAuth2 flows or scopes; RBAC governs what each key can do.
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  in: header
  header: Authorization
  format: 'Bearer <API key>'
  sources:
  - openapi/sublime-security-multitenancy-openapi.json
  - openapi/sublime-security-platform-openapi.json