Acceldata · OAuth Scopes
Acceldata OAuth Scopes
OAuth 2.0
searched
Acceldata 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.
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.
AI AgentsData ManagementData ObservabilityData PipelineData QualityIntelligenceObservability
Scopes: 0
Flows:
Method: searched
Scopes (0)
Acceldata 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.
Acceldata does NOT authorize its platform APIs with OAuth 2.0 scopes. Authentication is a static accessKey/secretKey header pair, and authorization is an RBAC permission model attached to the calling identity. The permissions below are not invented: every one is named verbatim in a published operation description ("Requires MODIFY_USERS permission", "Authorization: requires ASSET_VIEW and ASSET_METADATA_VIEW"), and the count is the number of published operations that name it. Roles are assembled from these permissions in the ADOC UI at Control Center > Access Management. derive-oauth-scopes.py was run first and correctly reported 0 oauth2 schemes; this file is the searched replacement that records the authorization model that actually exists.
Acceldata does NOT authorize its platform APIs with OAuth 2.0 scopes. Authentication is a static accessKey/secretKey header pair, and authorization is an RBAC permission model attached to the calling identity. The permissions below are not invented: every one is named verbatim in a published operation description ("Requires MODIFY_USERS permission", "Authorization: requires ASSET_VIEW and ASSET_METADATA_VIEW"), and the count is the number of published operations that name it. Roles are assembled from these permissions in the ADOC UI at Control Center > Access Management. derive-oauth-scopes.py was run first and correctly reported 0 oauth2 schemes; this file is the searched replacement that records the authorization model that actually exists.
📄 Provider scope reference: https://docs.acceldata.io/documentation/roles-and-permissions
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.