Hyperscience · OAuth Scopes
Hyperscience OAuth Scopes
OAuth 2.0
derived
Hyperscience 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 https://{server}.{company}.com/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.
AIDocument AIIDPEnterpriseAutomationGenAIFedRAMP
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://{server}.{company}.com/oauth/token
https://{server}.{company}.com/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Hyperscience 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.
Hyperscience's OAuth 2.0 M2M flow does not use published scopes; API access is governed by permission groups (e.g., the API Access permission) rather than OAuth scopes (https://help.hyperscience.ai/deployment/docs/machine-to-machine-authentication-with-oauth-20).
Hyperscience's OAuth 2.0 M2M flow does not use published scopes; API access is governed by permission groups (e.g., the API Access permission) rather than OAuth scopes (https://help.hyperscience.ai/deployment/docs/machine-to-machine-authentication-with-oauth-20).
📄 Provider scope reference: https://help.hyperscience.ai/deployment/docs/machine-to-machine-authentication-with-oauth-20