Scalekit · OAuth Scopes

Scalekit OAuth Scopes

OAuth 2.0 derived

Scalekit 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 https://{environment}.scalekit.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.

AuthenticationSSOSCIMIdentityB2B SaaSAgent Auth

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://{environment}.scalekit.com/oauth/token

Flows
clientCredentials

Scopes (0)

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

Scalekit's own API is secured with OAuth 2.0 client credentials and publishes no scopes for its endpoints; the scopes documented at https://docs.scalekit.com/guides/m2m/scopes/ are customer-defined permissions for their own API clients, not Scalekit API scopes (https://docs.scalekit.com/apis/).

📄 Provider scope reference: https://docs.scalekit.com/apis/

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/scalekit-openapi.yml
docs: https://docs.scalekit.com/apis/
note: Scalekit's own API is secured with OAuth 2.0 client credentials and publishes
  no scopes for its endpoints; the scopes documented at
  https://docs.scalekit.com/guides/m2m/scopes/ are customer-defined permissions
  for their own API clients, not Scalekit API scopes
  (https://docs.scalekit.com/apis/).
schemes:
- name: oauth2ClientCredentials
  source: openapi/scalekit-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://{environment}.scalekit.com/oauth/token
scopes: []