GoGift · OAuth Scopes
GoGift OAuth Scopes
OAuth 2.0
probed
GoGift 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.
Gift CardsRewardsIncentivesLoyaltyCommercePaymentsEmployee Recognition
Scopes: 0
Flows:
Method: probed
Scopes (0)
GoGift 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.
The API reference at docs.gogift.io never names a scope. Which of AuthApi / finance_api / retail_api a given client is granted is decided by GoGift when it provisions the client id and secret. Treat the non-standard scopes below as observed-from-discovery, not as a provider-published permissions reference.
The API reference at docs.gogift.io never names a scope. Which of AuthApi / finance_api / retail_api a given client is granted is decided by GoGift when it provisions the client id and secret. Treat the non-standard scopes below as observed-from-discovery, not as a provider-published permissions reference.
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.