Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Epidemic Sound Users API

These endpoints allows your application to get user specific information such as liked sounds.

Epidemic Sound Users API is one of 9 APIs that Epidemic Sound publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Users. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, and defines 13 schemas. It is described by OpenAPI 3.0.1, at version 0.1.17.

Requests are made against a single base URL, https://partner-content-api.epidemicsound.com.

2 operations 2 paths 13 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
0.1.17
Base URL
https://partner-content-api.epidemicsound.com
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 4

Epidemic Sound Users API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (ApiKeyAuth). It accepts HTTP bearer tokens (PartnerAuth). It accepts HTTP bearer tokens (UserAuth). It supports OAuth 2.0 (EpidemicSoundConnectAuth) using the authorizationCode flow.

  • ApiKeyAuth — API key authentication for server-to-server communication. Pass your API key as a Bearer token in the Authorization header. API keys are prefixed with epidemic…
  • PartnerAuth — Partner authentication is handled with short lived partner access tokens. Use your api credentials to request these tokens. The access token is of JWT format a…
  • UserAuth — User authentication is handled with short lived user access tokens. Use a partner token to request these tokens. The access token is of JWT format and should b…
  • EpidemicSoundConnectAuth — 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:…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Users 2

These endpoints allows your application to get user specific information such as liked sounds.

GET
/v0/users/me
User details
GET_End_User_Details → 200401429400
GET
/v0/users/me/liked/tracks
List users' liked tracks
GET_Users_Liked_Tracks 1 param → 200401429400

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are TrackResponse (15 properties), ImagesResponse (5 properties), UserInfo (4 properties), TracksResponse (4 properties). Each schema is shown below with its type and property counts.

TrackResponse
object
15 properties 10 required
TaxonomyAggregations
object
2 properties
TaxonomyAggregation
object
3 properties
TracksResponse
object
4 properties 3 required
Error
object
2 properties 2 required
MessageResponse
object
2 properties 1 required
PaginationLinks
object
2 properties
GenreResponse
object
3 properties 2 required
ParentGenreResponse
object
2 properties 2 required
MoodResponse
object
2 properties 2 required
UserInfo
object
4 properties 2 required
ImagesResponse
object
5 properties
Pagination
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

epidemic-sound-users-api-openapi.yml Raw ↑

Other APIs Epidemic Sound publishes across the network.

Epidemic Sound Assets API
Epidemic Sound Authentication API
Epidemic Sound Beta API
Epidemic Sound Browse & search API
Epidemic Sound Reporting API
Epidemic Sound Safelisting API
Epidemic Sound Sound effects API
Epidemic Sound Tracks API