Pluggy · OAuth Scopes
Pluggy OAuth Scopes
OAuth 2.0
none
Pluggy 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.
CompanyOpen FinanceBankingFinancial DataPaymentsBrazilFintech
Scopes: 0
Flows:
Method: none
Scopes (0)
Pluggy 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 Pluggy API uses API keys for authentication, not OAuth. The OAuth documentation refers to OAuth flows required by financial institutions for user authentication, not for API access to Pluggy itself. No OAuth scopes are defined for the API.
The Pluggy API uses API keys for authentication, not OAuth. The OAuth documentation refers to OAuth flows required by financial institutions for user authentication, not for API access to Pluggy itself. No OAuth scopes are defined for the API.
📄 Provider scope reference: https://docs.pluggy.ai/en/docs/connect-widget/oauth-support.md
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.