Tackle · OAuth Scopes

Tackle OAuth Scopes

OAuth 2.0 derived

Tackle 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 /oauth/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.

CompanyCloud MarketplaceCloud GTMGo-To-MarketPrivate OffersCo-SellMeteringSCIMAWS MarketplaceAzure Marketplace
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/oauth/token
Flows
clientCredentials

Scopes (0)

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

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-21'
method: derived
source: openapi/tackle-api-openapi.json
schemes:
- name: Oauth2AuthCallback
  source: openapi/tackle-api-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth/token
  description: This auth-type is for `oauth2` client credentials flow. We will use the client_id
    and client_secret to call the token_url to get an access token; this is only used for `callbacks`'
scopes: []