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

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

📄 Provider scope reference: https://www.ti.com/developer-api/store-api/authentication.html

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/texas-instruments-product-information-openapi.yml, openapi/texas-instruments-store-openapi.yml
docs: https://www.ti.com/developer-api/store-api/authentication.html
note: 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).
schemes:
- name: OAuth2
  source: openapi/texas-instruments-product-information-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://transact.ti.com/v1/oauth/accesstoken
  description: OAuth 2.0 client credentials flow. Obtain access token using client_id and client_secret
    from your myTI developer account.
- name: OAuth2
  source: openapi/texas-instruments-store-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://transact.ti.com/v1/oauth/accesstoken
  description: OAuth 2.0 client credentials flow. Obtain access token using client_id and client_secret
    from your myTI company account.
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/texas-instruments-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.