Totogi · OAuth Scopes
Totogi OAuth Scopes
OAuth 2.0
searched
Totogi 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://oauth.totogi.io/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 StatesBSSOSSChargingMessagingSMSA2P5GTM ForumStandardsNetwork VendorVertical AIGraphQLPolicy Control
Scopes: 0
Flows: clientCredentials
Method: searched
OAuth endpoints
Token URL
https://oauth.totogi.io/oauth2/token
https://oauth.totogi.io/oauth2/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Totogi 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.
Totogi CaaS does not expose OAuth scope strings in its public reference. Authorization is expressed as NAMED ROLES, published per operation as "Authorized Roles" in the GraphQL reference, and carried on the OAuth 2.0 client-credentials token minted for a tenant client. The roles below are transcribed verbatim from the published per-operation authorization statements.
Totogi CaaS does not expose OAuth scope strings in its public reference. Authorization is expressed as NAMED ROLES, published per operation as "Authorized Roles" in the GraphQL reference, and carried on the OAuth 2.0 client-credentials token minted for a tenant client. The roles below are transcribed verbatim from the published per-operation authorization statements.
📄 Provider scope reference: https://docs.api.totogi.com/