Subspace · OAuth Scopes

Subspace OAuth Scopes

OAuth 2.0 derived

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

Tokens are issued from https://id.subspace.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.

CompanyNetworkingReal-TimeWebRTCVoIPSIPCDNGamingLatencyInfrastructure

Scopes: 9 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://id.subspace.com/oauth/token

Flows
clientCredentials

Scopes (9)

Scope	Description	Flows
accelerators:read	allows reading details about provisioned PacketAccelerators	clientCredentials
accelerators:write	allows administration of PacketAccelerators	clientCredentials
console:access	allows access to the console	clientCredentials
projects:read	allows reading details about projects	clientCredentials
rtpspeed:read	allows reading details about rtpspeed	clientCredentials
rtpspeed:write	allows administration of rtpspeed	clientCredentials
sipteleport:read	allows reading details about provisioned SIPTeleport	clientCredentials
sipteleport:write	allows administration of SIPTeleport	clientCredentials
webrtccdn:access	allows administration of WebRTC-CDN	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-21'
method: derived
source: openapi/subspace-openapi-original.yml
schemes:
- name: accessCode
  source: openapi/subspace-openapi-original.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://id.subspace.com/oauth/token
scopes:
- scope: accelerators:read
  description: allows reading details about provisioned PacketAccelerators
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: accelerators:write
  description: allows administration of PacketAccelerators
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: console:access
  description: allows access to the console
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: projects:read
  description: allows reading details about projects
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: rtpspeed:read
  description: allows reading details about rtpspeed
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: rtpspeed:write
  description: allows administration of rtpspeed
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: sipteleport:read
  description: allows reading details about provisioned SIPTeleport
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: sipteleport:write
  description: allows administration of SIPTeleport
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml
- scope: webrtccdn:access
  description: allows administration of WebRTC-CDN
  flows:
  - clientCredentials
  sources:
  - openapi/subspace-openapi-original.yml

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/subspace-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.