Tackle.io · OAuth Scopes
Tackle.io OAuth Scopes
OAuth 2.0
searched
Tackle.io 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.
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.
CompanyCloudCloud MarketplaceCo-SellAWS MarketplaceAzure MarketplaceGoogle Cloud MarketplacePrivate OffersMeteringSCIMWebhookB2B SaaS
Scopes: 0
Flows:
Method: searched
Scopes (0)
Tackle.io 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: https://developers.tackle.io/docs/getting-an-access-token
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.