Oracle APEX · OAuth Scopes
Oracle APEX OAuth Scopes
OAuth 2.0
derived
Oracle APEX uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from /ords/{schema}/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.
APEXCloudDatabaseDevelopment PlatformEnterpriseGenerative AILow-CodeOracleORDSPL/SQLREST APIWeb ApplicationsWorkflow
Scopes: 0
Flows: clientCredentials, authorizationCode
Method: derived
OAuth endpoints
Authorization URL
/ords/{schema}/oauth/auth
/ords/{schema}/oauth/auth
Token URL
/ords/{schema}/oauth/token
/ords/{schema}/oauth/token
Flows
clientCredentialsauthorizationCode
clientCredentialsauthorizationCode
Scopes (0)
Oracle APEX implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
ORDS OAuth publishes no fixed scope catalog; access is granted through developer-defined ORDS privileges and roles per REST-enabled schema (OAUTH.CREATE_CLIENT p_privilege_names, OAUTH.GRANT_CLIENT_ROLE), with JWT scope claims expected to match privilege names (https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.2/orddg/OAUTH-reference.html).
ORDS OAuth publishes no fixed scope catalog; access is granted through developer-defined ORDS privileges and roles per REST-enabled schema (OAUTH.CREATE_CLIENT p_privilege_names, OAUTH.GRANT_CLIENT_ROLE), with JWT scope claims expected to match privilege names (https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.2/orddg/OAUTH-reference.html).
📄 Provider scope reference: https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/25.2/orddg/OAUTH-reference.html