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

Flows
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.

📄 Provider scope reference: https://developer.mashery.com/docs/read/mashery_api/30/Authentication

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/tibco-mashery-openapi.yml
docs: https://developer.mashery.com/docs/read/mashery_api/30/Authentication
note: >-
  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.
schemes:
- name: oauth2
  source: openapi/tibco-mashery-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.mashery.com/v3/token
  description: OAuth 2.0 client credentials for Mashery API access
scopes: []

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/tibco-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.