How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Epidemic Sound Reporting API

These endpoints will allow you to report how tracks are used in your application.

Epidemic Sound Reporting 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 Reporting. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

2 operations 2 paths 10 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
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 Reporting 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 POST. Each is listed below with its method, path, parameters, and response codes.

Reporting 2

These endpoints will allow you to report how tracks are used in your application.

POST
/v0/analytics/report
Report usage in bulk
POST_Analytics_Report body → 200401429400
POST
/v0/usage
Report usage
POST_Use body → 200401429400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are AnalyticsReportEvent (4 properties), TrackDownloadedEvent (4 properties), TrackUsageRequest (4 properties), TracksExportedEvent (3 properties). Each schema is shown below with its type and property counts.

TracksExportedEvent
object
3 properties
AnalyticsReportRequest
object
1 property 1 required
Error
object
2 properties 2 required
TrackUsageRequest
object
4 properties 2 required
AnalyticsReportEvent
object
4 properties
MessageResponse
object
2 properties 1 required
AnalyticsEvent
object
TrackDownloadedEvent
object
4 properties
TrackPreviewedEvent
object
2 properties
AnalyticsReportResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

epidemic-sound-reporting-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 Safelisting API
Epidemic Sound Sound effects API
Epidemic Sound Tracks API
Epidemic Sound Users API
Where this information came from

This is an independent, third-party profile of Epidemic Sound Reporting API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.