Texas Instruments · OAuth Scopes
Texas Instruments OAuth Scopes
OAuth 2.0
derived
Texas Instruments 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://transact.ti.com/v1/oauth/accesstoken.
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.
ElectronicsOrderingSemiconductorsSupply ChainFortune 500
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://transact.ti.com/v1/oauth/accesstoken
https://transact.ti.com/v1/oauth/accesstoken
Flows
clientCredentials
clientCredentials
Scopes (0)
Texas Instruments 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.
TI APIs use the OAuth 2.0 client credentials flow with no published scopes — the token response returns an empty scope field and access is granted per API via myTI API key requests (https://www.ti.com/developer-api/store-api/authentication.html).
TI APIs use the OAuth 2.0 client credentials flow with no published scopes — the token response returns an empty scope field and access is granted per API via myTI API key requests (https://www.ti.com/developer-api/store-api/authentication.html).
📄 Provider scope reference: https://www.ti.com/developer-api/store-api/authentication.html