Transmit Security · OAuth Scopes
Transmit Security OAuth Scopes
OAuth 2.0
searched
Transmit Security publishes 4 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Transmit Security API on a user’s behalf.
Tokens are issued from /oidc/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.
CIAMIdentityAuthenticationPasskeysWebAuthnFraud DetectionRisk ManagementIdentity VerificationOrchestrationOAuth2SecuritySSO
Scopes: 4
Flows: clientCredentials
Method: searched
OAuth endpoints
Token URL
/oidc/token
/oidc/token
Flows
clientCredentials
clientCredentials
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| openid | Required scope for OIDC authentication requests to /oidc/auth; scopes are passed as a space-delimited string. | |
| offline_access | Allows refreshing access tokens; must be explicitly requested (with prompt=consent) for refresh tokens to be returned in pure OIDC integrations. | |
| Includes the user's email address in the ID token returned upon authentication. | ||
| phone | Documented as an allowed value of the scope parameter in OIDC authentication requests. |
📄 Provider scope reference: https://developer.transmitsecurity.com/guides/user/auth_oidc