Digital Turbine (Fyber) · OAuth Scopes
Digital Turbine (Fyber) OAuth Scopes
OAuth 2.0
none
Digital Turbine (Fyber) 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://console.fyber.com/api/v2/management/auth.
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.
CompanyMobileAdvertisingMonetizationSDK
Scopes: 0
Flows: clientCredentials
Method: none
OAuth endpoints
Token URL
https://console.fyber.com/api/v2/management/auth https://reporting.fyber.com/auth/v1/token
https://console.fyber.com/api/v2/management/auth https://reporting.fyber.com/auth/v1/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Digital Turbine (Fyber) 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.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
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.