Fullview OAuth Scopes
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.
OAuth endpoints
https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/auth
https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/protocol/openid-connect/token
authorizationCodeclientCredentials
Scopes (12)
| Scope | Description | Flows |
|---|---|---|
| openid | OpenID Connect authentication; required to receive an ID token. | |
| profile | Access to the user's basic profile claims. | |
| 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). |
📄 Provider scope reference: https://auth.eu1.fullview.io/realms/fullview-idp-users-eu1/.well-known/openid-configuration
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.