Spare · OAuth Scopes
Spare OAuth Scopes
OAuth 2.0
searched
Spare 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.
Open BankingOpen FinanceAccount InformationPayment InitiationAISPPISPConsentBank DataTransactionsBalancesPaymentsFintechMENASaudi ArabiaBahrainUAE
Scopes: 0
Flows:
Method: searched
Scopes (0)
Spare 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.
Spare authenticates with OAuth2 client-credentials (see authentication/), but data access is governed by an open-banking CONSENT permission model rather than token scopes. When creating a Consent the client requests a set of AccountInformationPermission values; the end user authorises them in their bank app, and each AIS operation requires specific permissions on the active consent (the API reference lists the required permissions per endpoint). These consent permissions are the effective scope surface and are enumerated verbatim below.
Spare authenticates with OAuth2 client-credentials (see authentication/), but data access is governed by an open-banking CONSENT permission model rather than token scopes. When creating a Consent the client requests a set of AccountInformationPermission values; the end user authorises them in their bank app, and each AIS operation requires specific permissions on the active consent (the API reference lists the required permissions per endpoint). These consent permissions are the effective scope surface and are enumerated verbatim below.
📄 Provider scope reference: https://docs.tryspare.com/docs/consent-1