Audius · OAuth Scopes

Audius OAuth Scopes

OAuth 2.0 derived

Audius publishes 2 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Audius API on a user’s behalf.

Tokens are issued from /v1/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.

MusicStreamingDecentralizedWeb3Open SourceBlockchain

Scopes: 2 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
/v1/oauth/authorize

Token URL
/v1/oauth/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
read	Read-only access to user data	authorizationCode
write	Read and write access on behalf of the user	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/audius-openapi.yml
schemes:
- name: OAuth2
  source: openapi/audius-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /v1/oauth/authorize
    tokenUrl: /v1/oauth/token
  description: |-
    OAuth 2.0 Authorization Code flow with PKCE for third-party applications.

    Allows apps to authenticate users and obtain access tokens scoped to read or read+write permissions on behalf of the user.

    **Scopes:**
    - `read` — Read-only access to the user's public and private data.
    - `write` — Read and write access, allowing mutations on behalf of the user.

    **PKCE Required:**
    All authorization code requests must include `code_challenge` and `code_challenge_method=S256` parameters.
scopes:
- scope: read
  description: Read-only access to user data
  flows:
  - authorizationCode
  sources:
  - openapi/audius-openapi.yml
- scope: write
  description: Read and write access on behalf of the user
  flows:
  - authorizationCode
  sources:
  - openapi/audius-openapi.yml