Slash · OAuth Scopes
Slash OAuth Scopes
OAuth 2.0
searched
Slash 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.
CompanyBankingPaymentsFinancial ServicesFintechCorporate CardsBusiness BankingInvoicingExpense ManagementTreasuryFDX
Scopes: 0
Flows:
Method: searched
Scopes (0)
Slash 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.
Slash's public API authenticates primarily with API keys (X-API-Key), so the OpenAPI declares no oauth2 securityScheme and the derive-oauth-scopes pass found no flows. Slash DOES run a third-party OAuth/OIDC surface for developer applications: an OIDC discovery document plus a fine-grained permission-key model attached to developer applications. Both are captured below.
Slash's public API authenticates primarily with API keys (X-API-Key), so the OpenAPI declares no oauth2 securityScheme and the derive-oauth-scopes pass found no flows. Slash DOES run a third-party OAuth/OIDC surface for developer applications: an OIDC discovery document plus a fine-grained permission-key model attached to developer applications. Both are captured below.
📄 Provider scope reference: https://docs.slash.com/introduction