Feature Request: User Top Tracks Endpoint
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Provide an endpoint that exposes a user's most-played tracks over different time ranges.
Proposed Endpoint
GET /me/top-tracks?time_range=short_term|medium_term|long_term&limit=50
Use Cases
- Music compatibility applications
- Listening statistics dashboards
- Year-end recap experiences
- Personalized playlist generation
Why This Matters
Likes are not an accurate representation of listening behavior. Users often replay tracks many times without liking them. Exposing top tracks would allow developers to build experiences based on actual listening preferences rather than explicit likes alone.
Privacy
Require explicit OAuth scope such as:
user-top-tracks:read
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.
Research direction
Start with the proposed GET /me/top-tracks endpoint and its time_range and limit parameters. The issue names no files, tests, or implementation entry points; the first step is to clarify the endpoint contract and OAuth scope with maintainers. Done means an agreed design for exposing top tracks.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100