Feature Request: User Track Play Statistics
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- api, authentication, backend-api-design
Research direction
Review the existing public API patterns for likes, playlists, follows, and OAuth scopes before assessing GET /me/track-stats. Done would require an agreed design for collecting and exposing play counts, listening time, timestamps, completion and replay metrics while enforcing explicit track-stats:read consent.
Written by the indexing model from the issue text.
Description
Summary
Provide per-user listening statistics for tracks, including play counts and listening engagement metrics.
Proposed Endpoint
GET /me/track-stats
Example Response
{
"track_id": 12345,
"play_count": 47,
"total_listening_time_ms": 8923000,
"last_played_at": "2026-06-05T12:34:56Z",
"completion_rate": 0.91
}
Requested Data
- Number of times a user played a track
- Total listening time per track
- Last played timestamp
- Completion rate
- Replay count
Use Cases
Personal Analytics
Users can discover which tracks they actually listen to most, rather than relying on likes as a proxy.
Recommendation Engines
Play frequency often provides a much stronger signal of preference than likes alone.
Music Compatibility Apps
Comparing shared listening behavior becomes much more meaningful when based on actual engagement rather than saved tracks.
DJ & Playlist Tools
Developers can identify tracks that consistently receive high replay rates and engagement.
Why This Matters
Currently, developers can access likes, playlists, and follows, but cannot determine which tracks users truly engage with. A track played 50 times and a track played once appear identical through the current API.
Exposing listening statistics would unlock a richer ecosystem of analytics, recommendation, and discovery applications while remaining compatible with OAuth-based user consent.
Privacy
Access should require explicit OAuth authorization, for example:
track-stats:read
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from soundcloud/api
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#581 · 1 comment ·
-
widget
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#557 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#547 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
soundcloud/api#545 · 2 comments · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
soundcloud/api#537 · 7 comments · 1 reaction ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
neondatabase/website#5944 ·
-
module: core
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bigbluebutton/bigbluebutton#25849 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·