Syniverse · OAuth Scopes

Syniverse OAuth Scopes

OAuth 2.0 derived

Syniverse 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://api.mt1.messaging-trust.syniverse.com/oauth2/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.

TelecommunicationsUnited StatesCPaaSMessagingSMSRoamingIPXWholesaleIdentity VerificationSIM Swap10DLCOpen GatewayNetwork APIsAggregator

Scopes: 0 Flows: clientCredentials, implicit Method: derived

OAuth endpoints

Authorization URL
https://beta.api.syniverse.com/token

Token URL
https://api.mt1.messaging-trust.syniverse.com/oauth2/token

Flows
clientCredentialsimplicit

Scopes (0)

Syniverse 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:

Source

OAuth Scopes

generated: '2026-07-25'
method: derived
source: openapi/syniverse-messaging-trust-datafeed-openapi.yml, openapi/syniverse-messaging-trust-resolve-openapi.yml,
  openapi/syniverse-whitelisting-service-openapi.json
summary: >-
  Syniverse declares three oauth2 security schemes but publishes ZERO scopes. Every flow
  carries an empty scopes map, no operation names a scope in its security requirement, and
  the Developer Community documentation has no scopes or permissions reference page — the
  docs and support knowledge base were searched on 2026-07-25 and none exists. Authorization
  is coarse: an SDC application access token carries whatever entitlements the account
  holds, and 403 Forbidden means "credentials do not carry the entitlements" rather than
  "missing scope". Recorded as a genuine empty result, not a gap in the harvest.
scopes_documented: false
docs: null
schemes:
- name: OAuth2
  source: openapi/syniverse-messaging-trust-datafeed-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.mt1.messaging-trust.syniverse.com/oauth2/token
- name: OAuth2
  source: openapi/syniverse-messaging-trust-resolve-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.mt1.messaging-trust.syniverse.com/oauth2/token
- name: default
  source: openapi/syniverse-whitelisting-service-openapi.json
  flows:
  - flow: implicit
    authorizationUrl: https://beta.api.syniverse.com/token
scopes: []