Flutterwave · OAuth Scopes
Flutterwave OAuth Scopes
OAuth 2.0
derived
Flutterwave 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://idp.flutterwave.com/realms/flutterwave/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.
PaymentsPayoutsMobile MoneyCardsAfricaFintechRemittanceVirtual AccountsChargebacksMulti-Currency
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://idp.flutterwave.com/realms/flutterwave/protocol/openid-connect/token
https://idp.flutterwave.com/realms/flutterwave/protocol/openid-connect/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Flutterwave 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.
Flutterwave's v4 API uses OAuth 2.0 client_credentials (client_id/client_secret via idp.flutterwave.com) without documented API permission scopes; token responses only carry default OIDC scopes such as "profile email" (https://developer.flutterwave.com/docs/authentication).
Flutterwave's v4 API uses OAuth 2.0 client_credentials (client_id/client_secret via idp.flutterwave.com) without documented API permission scopes; token responses only carry default OIDC scopes such as "profile email" (https://developer.flutterwave.com/docs/authentication).
📄 Provider scope reference: https://developer.flutterwave.com/docs/authentication