Green Dot Corporation OAuth Scopes

OAuth 2.0 searched

Green Dot Corporation publishes 3 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Green Dot Corporation API on a user’s behalf.

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.

FintechBanking as a ServiceEmbedded FinancePrepaid CardsBankingPaymentsMoney MovementUnited States

Scopes: 3 Flows: Method: searched

Scopes (3)

Scope	Description	Flows
general	Baseline granted scope observed in the documented authentication example token response. Exact grants are partner/program specific.
demo	Demo/sandbox scope observed in the documented example token response.
post:webhook	Scope used to obtain a token for the partner-hosted webhook delivery surface (bank-events auth), per the Webhooks Overview.

📄 Provider scope reference: https://developer.greendot.com/embedded-finance/docs/baas-api-authentication

Source

OAuth Scopes

generated: '2026-07-23'
method: searched
source: https://developer.greendot.com/embedded-finance/docs/baas-api-authentication
docs: https://developer.greendot.com/embedded-finance/docs/baas-api-authentication
summary: >-
  Green Dot BaaS OAuth 2.0 uses the client-credentials flow with an optional,
  space-delimited scope parameter on the token request; the granted scope is
  returned on the token response (e.g. "general demo"). The public developer
  portal does not publish a full scope catalog — scopes are provisioned per
  partner/program during commercial onboarding and constrain a credential to
  its authorized product surface ("out of credential scopes" 401 on overreach).
  Webhook delivery uses a distinct token scope (post:webhook).
schemes:
  - name: oauth2ClientCredentials
    flow: clientCredentials
    token_endpoint: '{BaasUrl}/authentication'
    scope_parameter: optional
    scope_style: space-delimited
scopes:
  - scope: general
    description: >-
      Baseline granted scope observed in the documented authentication example
      token response. Exact grants are partner/program specific.
    source: docs
  - scope: demo
    description: Demo/sandbox scope observed in the documented example token response.
    source: docs
  - scope: 'post:webhook'
    description: >-
      Scope used to obtain a token for the partner-hosted webhook delivery
      surface (bank-events auth), per the Webhooks Overview.
    source: https://developer.greendot.com/embedded-finance/docs/webhooks-overview
notes: >-
  No exhaustive scope/permission reference is published publicly; the full set
  is defined per partner program. This artifact captures the scope MODEL and the
  scopes named in Green Dot's own documentation — no scopes were invented.