VTS · OAuth Scopes

VTS OAuth Scopes

OAuth 2.0 derived

VTS publishes 4 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the VTS API on a user’s behalf.

Tokens are issued from https://sandbox.vts.com/oauth/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.

CompanyCommercial Real EstatePropTechReal EstateLeasingAsset ManagementProperty ManagementTenant Experience

Scopes: 4 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://sandbox.vts.com/oauth/authorize

Token URL
https://sandbox.vts.com/oauth/token

Flows
authorizationCode

Scopes (4)

Scope	Description	Flows
email	Email claim	authorizationCode
openid	OpenID Connect	authorizationCode
profile	Profile claims	authorizationCode
read_write	Read and write access	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-21'
method: derived
source: openapi/vts-openapi.yml
schemes:
- name: oauth2
  source: openapi/vts-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://sandbox.vts.com/oauth/authorize
    tokenUrl: https://sandbox.vts.com/oauth/token
  description: OAuth 2.0 Authorization Code flow with PKCE (VTS Activate / OIDC).
scopes:
- scope: email
  description: Email claim
  flows:
  - authorizationCode
  sources:
  - openapi/vts-openapi.yml
- scope: openid
  description: OpenID Connect
  flows:
  - authorizationCode
  sources:
  - openapi/vts-openapi.yml
- scope: profile
  description: Profile claims
  flows:
  - authorizationCode
  sources:
  - openapi/vts-openapi.yml
- scope: read_write
  description: Read and write access
  flows:
  - authorizationCode
  sources:
  - openapi/vts-openapi.yml