Bandcamp · OAuth Scopes

Bandcamp OAuth Scopes

OAuth 2.0 derived

Bandcamp 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 https://bandcamp.com/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.

MusicMarketplaceIndieAudioSalesMerch
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://bandcamp.com/oauth_token
Flows
clientCredentials

Scopes (0)

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

Bandcamp's API uses the OAuth 2.0 client_credentials grant (with refresh tokens) and does not define or document any OAuth scopes (https://bandcamp.com/developer).

📄 Provider scope reference: https://bandcamp.com/developer

Source

OAuth Scopes

bandcamp-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/bandcamp-openapi.yml
docs: https://bandcamp.com/developer
note: Bandcamp's API uses the OAuth 2.0 client_credentials grant (with refresh tokens)
  and does not define or document any OAuth scopes (https://bandcamp.com/developer).
schemes:
- name: oauth2
  source: openapi/bandcamp-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://bandcamp.com/oauth_token
scopes: []