Forage · OAuth Scopes
Forage OAuth Scopes
OAuth 2.0
derived
Forage publishes 6 OAuth 2.0 scopes via the password and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Forage API on a user’s behalf.
Tokens are issued from /o/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.
CompanyPaymentsEBTSNAPEBT CashHSA/FSAFintechGovernment BenefitsGroceryCheckoutFinancial Services
Scopes: 6
Flows: password, clientCredentials
Method: derived
OAuth endpoints
Token URL
/o/token/
/o/token/
Flows
passwordclientCredentials
passwordclientCredentials
Scopes (6)
| Scope | Description | Flows |
|---|---|---|
| disbursement | Scope for tokens which can disburse money to merchants. | clientCredentials |
| hosted_checkout | Scope for tokens used by merchant applications which allow Forage to manage split tender processing (i.e. EBT + Credit/Debit). | password |
| internal | Scope for tokens used by Forage internal applications. | clientCredentials |
| pin-protected | Scope for tokens which can access secure storage. | clientCredentials |
| pinpad_only | Scope for tokens used by merchant applications which manage their own split tender (i.e. Forage Checkout is used only for EBT processing). | password |
| reporting |
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.