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: []