Saperly · OAuth Scopes

Saperly OAuth Scopes

OAuth 2.0 searched

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

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.

TelephonyVoiceSMSPhone NumbersAI AgentsConsentComplianceMCPMessagingCommunications
Scopes: 7 Flows: Method: searched

Scopes (7)

ScopeDescriptionFlows
read list and read resources (numbers, connections, messages, calls, usage, consent)
write mutating actions — place calls, send SMS, provision/release numbers, record consent, write connections
admin everything write allows, plus minting, listing, and revoking child keys (keys:admin)
openid OpenID Connect identity scope advertised by the MCP OAuth authorization server
profile advertised by the MCP OAuth authorization server
email advertised by the MCP OAuth authorization server
offline_access refresh-token access (grant_types_supported includes refresh_token)

Source

OAuth Scopes

Raw ↑
generated: '2026-10-07'
method: searched
source: https://saperly.com/docs/guides/authentication (API-key scope grants); https://saperly.com/.well-known/oauth-authorization-server
  (MCP OAuth scopes_supported, probed 2026-10-07)
docs: https://saperly.com/docs/guides/authentication
description: 'Saperly has two scope vocabularies: the coarse read/write/admin grant carried by a scoped sap_sk_
  API key (bounded further by an optional number allow-list and spend cap), and the OpenID scopes the MCP OAuth
  2.1 authorization server at https://saperly.com advertises.'
scopes:
- scope: read
  name: read
  description: list and read resources (numbers, connections, messages, calls, usage, consent)
  issuer: api-key grant
- scope: write
  name: write
  description: mutating actions — place calls, send SMS, provision/release numbers, record consent, write connections
  issuer: api-key grant
- scope: admin
  name: admin
  description: everything write allows, plus minting, listing, and revoking child keys (keys:admin)
  issuer: api-key grant
- scope: openid
  name: openid
  description: OpenID Connect identity scope advertised by the MCP OAuth authorization server
  issuer: https://saperly.com
- scope: profile
  name: profile
  description: advertised by the MCP OAuth authorization server
  issuer: https://saperly.com
- scope: email
  name: email
  description: advertised by the MCP OAuth authorization server
  issuer: https://saperly.com
- scope: offline_access
  name: offline_access
  description: refresh-token access (grant_types_supported includes refresh_token)
  issuer: https://saperly.com
grant_bounds:
  numberScope: optional allow-list of number ids; number-scoped actions are restricted to exactly those numbers
  spendLimitCents: hard spend cap in cents enforced at reserve time
  spendLimitResetPeriod: '''monthly'' (resets at the UTC month boundary) or null for a lifetime cap'
  child_keys: a key with admin can mint child keys whose scopes, allow-list and cap may not exceed its own grant
    (enforced server-side)

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

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