Exabeam · OAuth Scopes

Exabeam OAuth Scopes

OAuth 2.0 searched

Exabeam publishes 3 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Exabeam API on a user’s behalf.

Tokens are issued from https://api.us-west.exabeam.cloud/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyCybersecuritySecuritySIEMUEBAThreat DetectionSecurity OperationsSOCLog ManagementIncident Response
Scopes: 3 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://api.us-west.exabeam.cloud/oauth/authorize
Token URL
https://api.us-west.exabeam.cloud/oauth/token
Flows
authorizationCode

Scopes (3)

ScopeDescriptionFlows
openid OpenID Connect authentication. authorizationCode
profile Access to the authenticated principal's profile. authorizationCode
offline_access Issue a refresh token for continued (offline) access. authorizationCode

Source

OAuth Scopes

exabeam-scopes.yml Raw ↑
generated: '2026-07-19'
method: searched
source: https://api.us-west.exabeam.cloud/.well-known/oauth-authorization-server
docs: https://developers.exabeam.com/exabeam/docs/api-keys
schemes:
- name: OAuth2
  source: https://api.us-west.exabeam.cloud/.well-known/oauth-authorization-server
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.us-west.exabeam.cloud/oauth/authorize
    tokenUrl: https://api.us-west.exabeam.cloud/oauth/token
scopes:
- scope: openid
  description: OpenID Connect authentication.
  flows: [authorizationCode]
  sources: [well-known/exabeam-oauth-authorization-server.json]
- scope: profile
  description: Access to the authenticated principal's profile.
  flows: [authorizationCode]
  sources: [well-known/exabeam-oauth-authorization-server.json]
- scope: offline_access
  description: Issue a refresh token for continued (offline) access.
  flows: [authorizationCode]
  sources: [well-known/exabeam-oauth-authorization-server.json]
notes: >-
  Scopes are taken verbatim from the published RFC 8414 authorization-server
  metadata (scope: "openid profile offline_access"). Fine-grained,
  product-level API permissions are governed by the role assigned to the API
  key in the Exabeam console rather than by additional OAuth scopes.