Epidemic Sound · OAuth Scopes

Epidemic Sound OAuth Scopes

OAuth 2.0 derived

Epidemic Sound 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://login.epidemicsound.com/auth/realms/accounts/protocol/openid-connect/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.

MusicSound EffectsRoyalty-Free MusicAudioAudio LicensingSoundtrackingSync LicensingCreatorsVideoAI VoiceoverSemantic SearchMCP

Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://login.epidemicsound.com/auth/realms/accounts/protocol/openid-connect/auth

Token URL
https://login.epidemicsound.com/auth/realms/accounts/protocol/openid-connect/token

Flows
authorizationCode

Scopes (0)

Epidemic Sound 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.

Epidemic Sound Connect uses OpenID Connect (authorization code + PKCE) but publishes no OAuth scopes reference — the auth docs (https://developers.epidemicsound.com/docs/auth/) show no scope parameter, and access is governed by the partnership agreement and the user's subscription tier rather than scopes (a token-response example shows only standard OIDC "email profile").

📄 Provider scope reference: https://developers.epidemicsound.com/docs/auth/

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/epidemic-sound-partner-content-api-openapi.yml
docs: https://developers.epidemicsound.com/docs/auth/
note: Epidemic Sound Connect uses OpenID Connect (authorization code + PKCE) but publishes no OAuth scopes reference — the auth docs (https://developers.epidemicsound.com/docs/auth/) show no scope parameter, and access is governed by the partnership agreement and the user's subscription tier rather than scopes (a token-response example shows only standard OIDC "email profile").
schemes:
- name: EpidemicSoundConnectAuth
  source: openapi/epidemic-sound-partner-content-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.epidemicsound.com/auth/realms/accounts/protocol/openid-connect/auth
    tokenUrl: https://login.epidemicsound.com/auth/realms/accounts/protocol/openid-connect/token
  description: |-
    For users signing in with an Epidemic Sound account, user authentication is
    handled with OpenID Connect, which is a layer on top of OAuth 2.0.

    > **Example Header:** `Authorization: Bearer es-connect-token`
scopes: []