Apstal · OAuth Scopes

Apstal OAuth Scopes

OAuth 2.0 probed

Apstal publishes 3 OAuth 2.0 scopes via the authorizationCode and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Apstal API on a user’s behalf.

Tokens are issued from https://apstal.com/api/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.

analyticsweb-analyticsprivacysession-replayheatmapsmcpagent-nativecookielessllms-txtbigquerygdpra2aagent-skillsbot-detectioncore-web-vitals

Scopes: 3 Flows: authorizationCode, refreshToken Method: probed

OAuth endpoints

Authorization URL
https://apstal.com/api/auth/callback

Token URL
https://apstal.com/api/auth/token

Flows
authorizationCoderefreshToken

Scopes (3)

Scope	Description	Flows
read		authorizationCode
write		authorizationCode
admin		authorizationCode

📄 Provider scope reference: https://apstal.com/auth.md

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://apstal.com/.well-known/oauth-authorization-server
docs: https://apstal.com/auth.md
note: >-
  Apstal publishes no OpenAPI, so derive-oauth-scopes.py has no spec to read. The scope list
  below is taken from the provider's live RFC 8414 authorization-server metadata and its
  RFC 9728 protected-resource metadata, cross-checked against auth.md. Apstal publishes NO
  per-scope descriptions and NO scope-to-permission mapping; the descriptions below are the
  provider's own wording from auth.md ("Scopes: read, write, admin") and nothing more has been
  inferred.
schemes:
- name: oauth2
  source: https://apstal.com/.well-known/oauth-authorization-server
  issuer: https://apstal.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://apstal.com/api/auth/callback
    tokenUrl: https://apstal.com/api/auth/token
  - flow: refreshToken
scopes:
- scope: read
  description: null
  flows: [authorizationCode]
  sources:
  - https://apstal.com/.well-known/oauth-authorization-server
  - https://apstal.com/.well-known/oauth-protected-resource
- scope: write
  description: null
  flows: [authorizationCode]
  sources:
  - https://apstal.com/.well-known/oauth-authorization-server
  - https://apstal.com/.well-known/oauth-protected-resource
- scope: admin
  description: null
  flows: [authorizationCode]
  sources:
  - https://apstal.com/.well-known/oauth-authorization-server
  - https://apstal.com/.well-known/oauth-protected-resource
gaps:
- No published scopes/permissions reference page.
- No per-scope descriptions anywhere in the provider's public material.
- >-
  API keys (the credential the MCP server and the documented REST endpoints actually use) carry
  no scope model at all; auth.md says only that "API keys grant access to analytics query
  endpoints (/api/analytics/*)" while "OAuth tokens grant access to the full API surface".