Phone Com · OAuth Scopes

Phone Com OAuth Scopes

OAuth 2.0 searched

Phone Com 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.

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.

CompanyVoIPTelephonyBusiness PhoneSMSVideo ConferencingCommunicationsAPI

Scopes: 0 Flows: Method: searched

Scopes (0)

Phone Com 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.

📄 Provider scope reference: https://docs.phone.com/aboutdevenv/insidephonecomapi/apisecurity.html

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://apidocs.phone.com/docs/access-token
type: OAuthScopes
api: phone-com-api
docs: https://docs.phone.com/aboutdevenv/insidephonecomapi/apisecurity.html
flow: oauth2
token_endpoint: https://api.phone.com/v4/oauth/access-token
notes: >-
  Scopes are provided as a space-separated string when requesting an access
  token and may be combined. Transcribed from the published Phone.com access
  token documentation; no machine-readable OpenAPI is published so the
  derive-oauth-scopes.py baseline could not be generated.
scopes:
- name: account-owner
  description: Identity/permission tier granting account-owner level access across the account's resources.
- name: extension-user
  description: Identity/permission tier scoped to a single extension user rather than the whole account.
- name: oauth-management
  description: >-
    Required for OAuth token management and API-usage endpoints (list/get/delete
    access tokens, API statistics, API errors).
- name: methods:ALL
  description: Grants access to all Phone.com API methods.