Switstack · OAuth Scopes

Switstack OAuth Scopes

OAuth 2.0 searched

Switstack 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 auth/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.

CompanyFintech InsurtechPaymentsEMVemv-level-2Card PresentPoint-of-SaleSoftPOSTap to PayPayment TerminalsIn-Store Paymentspci-mpoccertification-testingRetail Paymentsestate-management

Scopes: 0 Flows: password, clientCredentials Method: searched

OAuth endpoints

Token URL
auth/token

Flows
passwordclientCredentials

Scopes (0)

Switstack 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.

Switstack publishes OAuth 2.0 but no scope vocabulary. Both OpenAPI documents declare the password flow with an empty `scopes` map, and the Switcloud security & authentication page describes authorization as three named roles (Super Admin, Organization Admin, Simple User) rather than delegatable scopes; Swittest documents two (Data, Full). There is no published scopes/permissions reference page. The roles are recorded in authentication/switstack-authentication.yml under authorization_model — an honest zero here, not an omission.

📄 Provider scope reference: https://docs.switstack.io/switcloud/security_authentication/

Source

OAuth Scopes

generated: '2026-08-17'
method: searched
source: openapi/switstack-switcloud-openapi.yml, openapi/switstack-swittest-openapi.yml
docs: https://docs.switstack.io/switcloud/security_authentication/
schemes:
- name: OAuth2PasswordBearer
  source: openapi/switstack-switcloud-openapi.yml
  flows:
  - flow: password
    tokenUrl: auth/token
  - flow: clientCredentials
    tokenUrl: auth/token
    source: https://docs.switstack.io/switcloud/security_authentication/
- name: OAuth2PasswordBearer
  source: openapi/switstack-swittest-openapi.yml
  flows:
  - flow: password
    tokenUrl: auth/token
scopes: []
scope_count: 0
note: >-
  Switstack publishes OAuth 2.0 but no scope vocabulary. Both OpenAPI documents declare the password flow with an
  empty `scopes` map, and the Switcloud security & authentication page describes authorization as three named roles
  (Super Admin, Organization Admin, Simple User) rather than delegatable scopes; Swittest documents two (Data,
  Full). There is no published scopes/permissions reference page. The roles are recorded in
  authentication/switstack-authentication.yml under authorization_model — an honest zero here, not an omission.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/switstack-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.