zSpace · OAuth Scopes

zSpace OAuth Scopes

OAuth 2.0 probed

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

CompanyEducationAugmented RealityVirtual RealityEdTechHardware3DSimulationCareer and Technical EducationDeveloper SDK

Scopes: 0 Flows: Method: probed

Scopes (0)

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

scopes_supported read verbatim from the production Keycloak OIDC discovery document. These are the Keycloak realm default client scopes; zSpace publishes no scope or permission reference page, so no application-specific scopes (device, content, roster, licensing) could be found. Descriptions below are the standard OIDC/Keycloak meanings of each scope, not zSpace prose.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-05'
method: probed
source: https://auth.zspace.com/auth/realms/master/.well-known/openid-configuration
docs: null
note: >-
  scopes_supported read verbatim from the production Keycloak OIDC discovery document.
  These are the Keycloak realm default client scopes; zSpace publishes no scope or
  permission reference page, so no application-specific scopes (device, content, roster,
  licensing) could be found. Descriptions below are the standard OIDC/Keycloak meanings of
  each scope, not zSpace prose.
issuer: https://auth.zspace.com/auth/realms/master
scope_count: 9
scopes:
- name: openid
  description: Required for OpenID Connect; requests an ID token.
  standard: OpenID Connect Core 1.0
- name: profile
  description: Basic profile claims (name, given_name, family_name, preferred_username).
  standard: OpenID Connect Core 1.0
- name: email
  description: The email and email_verified claims.
  standard: OpenID Connect Core 1.0
- name: address
  description: The address claim.
  standard: OpenID Connect Core 1.0
- name: phone
  description: The phone_number and phone_number_verified claims.
  standard: OpenID Connect Core 1.0
- name: offline_access
  description: Requests a refresh token usable while the user is not present.
  standard: OpenID Connect Core 1.0
- name: roles
  description: Keycloak realm and client role mappings in the token.
  standard: Keycloak default client scope
- name: web-origins
  description: Keycloak scope that populates allowed CORS origins in the token.
  standard: Keycloak default client scope
- name: microprofile-jwt
  description: MicroProfile JWT claims (upn, groups).
  standard: Eclipse MicroProfile JWT RBAC
gaps:
- >-
  No published scope reference. Every scope here is a Keycloak/OIDC default — zSpace has
  not defined an application permission model that an integrator could request against.

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/zspace-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 email required.

GitHub Google LinkedIn

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