Raid Ai Authentication

generated: '2026-07-20'
method: searched
source: https://docs.raidxai.com/docs/authentication
docs: https://docs.raidxai.com/docs/authentication
summary:
  types: [apiKey, oauth2, openIdConnect]
  api_key_in: [header]
  api_key_scheme: bearer
  oauth2_flows: [authorizationCode, clientCredentials, password, refreshToken]
schemes:
  - name: apiToken
    type: http
    scheme: bearer
    in: header
    header: Authorization
    format: "Authorization: Bearer <your-token>"
    description: >-
      Every request to the Raid AI detection API is authenticated with a secret
      API token, created in the dashboard (API Keys -> Create Key). A key is
      granted one or more detection scopes and an optional expiry, and the token
      is shown only once. A missing/invalid/revoked/expired key returns 401
      Unauthorized; calling an endpoint the key is not scoped for returns 403
      Forbidden. Tokens are server-side secrets — never embed in client code.
    source: docs.raidxai.com/docs/authentication
  - name: OpenIDConnect
    type: openIdConnect
    openIdConnectUrl: https://api.raidxai.com/.well-known/openid-configuration
    description: >-
      Platform / dashboard identity is an OpenIddict OAuth 2.0 + OpenID Connect
      server (separate from the API-key surface used to call detection
      endpoints). Discovery advertises authorization, token, introspection,
      userinfo and logout endpoints and RS256-signed ID tokens.
    source: api.raidxai.com/.well-known/openid-configuration
  - name: OAuth2
    type: oauth2
    flows:
      - flow: authorizationCode
        authorizationUrl: https://api.raidxai.com/connect/authorize
        tokenUrl: https://api.raidxai.com/connect/token
        pkce: [S256, plain]
      - flow: clientCredentials
        tokenUrl: https://api.raidxai.com/connect/token
      - flow: password
        tokenUrl: https://api.raidxai.com/connect/token
    source: api.raidxai.com/.well-known/openid-configuration