TIBCO · OAuth Scopes
TIBCO OAuth Scopes
OAuth 2.0
derived
TIBCO 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.mashery.com/v3/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.
AnalyticsAPI ManagementCloudEnterprise SoftwareIntegrationMessagingReal-Time Data
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.mashery.com/v3/token
https://api.mashery.com/v3/token
Flows
clientCredentials
clientCredentials
Scopes (0)
TIBCO 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.
TIBCO does not publish a named OAuth scope catalog — the Mashery V3 API's scope parameter carries the customer's Mashery Area UUID rather than permissions (https://developer.mashery.com/docs/read/mashery_api/30/Authentication), and TIBCO Cloud access tokens are scoped to product domains (e.g. TSC, TCI) with permissions governed by user roles rather than documented scopes.
TIBCO does not publish a named OAuth scope catalog — the Mashery V3 API's scope parameter carries the customer's Mashery Area UUID rather than permissions (https://developer.mashery.com/docs/read/mashery_api/30/Authentication), and TIBCO Cloud access tokens are scoped to product domains (e.g. TSC, TCI) with permissions governed by user roles rather than documented scopes.
📄 Provider scope reference: https://developer.mashery.com/docs/read/mashery_api/30/Authentication