generated: '2026-07-19'
method: searched
source: https://docs.opencti.io/latest/reference/api/ ; https://docs.openaev.io/latest/
docs: https://docs.opencti.io/latest/reference/api/
summary:
  types: [http]
  http_schemes: [bearer]
  api_key_in: [header]
  oauth2_flows: []
  notes: >-
    API access to both OpenCTI and OpenAEV is via a per-user bearer API token
    presented in the Authorization header. OAuth2 / OIDC / SAML are supported
    for interactive user login (SSO) but the programmatic API uses static
    bearer tokens, not OAuth scopes — so no scopes/ artifact is emitted.
schemes:
- name: OpenCTI bearer token
  api: OpenCTI GraphQL API
  type: http
  scheme: bearer
  location: header
  header: Authorization
  format: 'Authorization: Bearer <API_TOKEN>'
  description: >-
    Each OpenCTI user has an API token (Profile > API access). Access rights are
    determined by the privileges of that user account. Content-Type
    application/json is required for GraphQL requests.
  source: https://docs.opencti.io/latest/reference/api/
- name: OpenAEV bearer token
  api: OpenAEV REST API
  type: http
  scheme: bearer
  location: header
  header: Authorization
  format: 'Authorization: Bearer <API_TOKEN>'
  description: >-
    OpenAEV (OpenBAS) REST API authenticates with a per-user bearer token, used
    by the official pyobas client.
  source: https://docs.openaev.io/latest/
sso:
  note: >-
    Interactive platform login additionally supports OpenID Connect, SAML 2.0,
    LDAP, and local authentication providers (user-login only, not API auth).