Fullview · OAuth Scopes

Fullview OAuth Scopes

OAuth 2.0 searched

Fullview publishes 12 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Fullview API on a user’s behalf.

Tokens are issued from https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/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.

CompanyCustomer SupportCobrowsingSession ReplayCustomer ExperienceDeveloper ToolsHelp DeskSaaS
Scopes: 12 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/auth
Token URL
https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/token
Flows
authorizationCodeclientCredentials

Scopes (12)

ScopeDescriptionFlows
openid OpenID Connect authentication; required to receive an ID token.
profile Access to the user's basic profile claims.
email Access to the user's email claim.
address Access to the user's address claim.
phone Access to the user's phone claim.
roles Include realm/client role mappings in the token.
offline_access Issue a refresh token for offline access.
microprofile-jwt MicroProfile JWT claims (groups, upn) for service authorization.
service_account Scope associated with client-credentials service accounts.
web-origins Allowed web origins claim for CORS.
acr Authentication Context Class Reference handling.
basic Keycloak basic client scope (sub, auth_time claims).

Source

OAuth Scopes

Raw ↑
generated: '2026-07-19'
method: searched
source: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/.well-known/openid-configuration
docs: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/.well-known/openid-configuration
schemes:
  - name: fullviewOIDC
    source: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/.well-known/openid-configuration
    flows:
      - flow: authorizationCode
        authorizationUrl: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/auth
        tokenUrl: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/token
      - flow: clientCredentials
        tokenUrl: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/token
scopes:
  - scope: openid
    description: OpenID Connect authentication; required to receive an ID token.
  - scope: profile
    description: Access to the user's basic profile claims.
  - scope: email
    description: Access to the user's email claim.
  - scope: address
    description: Access to the user's address claim.
  - scope: phone
    description: Access to the user's phone claim.
  - scope: roles
    description: Include realm/client role mappings in the token.
  - scope: offline_access
    description: Issue a refresh token for offline access.
  - scope: microprofile-jwt
    description: MicroProfile JWT claims (groups, upn) for service authorization.
  - scope: service_account
    description: Scope associated with client-credentials service accounts.
  - scope: web-origins
    description: Allowed web origins claim for CORS.
  - scope: acr
    description: Authentication Context Class Reference handling.
  - scope: basic
    description: Keycloak basic client scope (sub, auth_time claims).