Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Expose Repeat Listeners in the public API

未关闭
#596 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
40/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃

调研方向

Read the SoundCloud help article linked in the issue and the related issue #68 for the broader Insights API ask, plus the current documented track stats endpoints, to see where a repeat-listener field would fit. Scope is a documented OAuth-scoped analytics endpoint or track field with reporting period, update timestamp, and summed-vs-deduplicated semantics defined. Done looks like a written API proposal accepted by maintainers — note this repo is feedback-only, so no code change is available to a contributor.

由索引模型根据 Issue 内容生成。

描述

enhancement

Please expose the Repeat Listeners count through a documented public developer API that third-party developers can use to build artist dashboards. Access to the metric must require OAuth authorization from the artist and must be limited to that artist's own account and tracks; these analytics should not be publicly readable for other artists. This metric already exists in SoundCloud Artist Insights, but it is not exposed in the documented public API.

Artists want to build dashboards that aggregate repeat-listener counts across tracks, alongside plays and recommended plays, to compare audience retention and discovery without manually collecting figures from each track's Insights UI.

A documented analytics endpoint or track-statistics field should provide:

  • Per-track repeat-listener counts, using the same definition as Artist Insights.
  • A consistent reporting period and update timestamp so dashboards can compare metrics reliably.
  • Availability to registered developer applications, with required artist OAuth authorization. Each application may retrieve analytics only for the authorizing artist's own tracks, respecting existing account entitlements.

Please also document whether cross-track totals represent summed per-track counts or deduplicated listeners. Aggregate counts would meet this use case; individual listener identities are not required.

SoundCloud documents the existing UI metric here: https://help.soundcloud.com/hc/en-us/articles/115003451227-Individual-Track-Insights

Related: #68 requests broader Insights API access. This request specifically asks for the existing Repeat Listeners metric to be available through the public API.

If public API access is not possible, please consider adding this as a built-in Artist Pro Insights feature: an account/profile-level dashboard that aggregates Repeat Listeners alongside plays and recommended plays across the artist's tracks. At minimum, let artists select a group of tracks and view the combined metrics for that selection, with clear labeling of summed per-track counts versus deduplicated listeners.

主要语言
JavaScript
星标
256
派生
53
平均合并
1 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

soundcloud/api 的其他 Issue

查看 soundcloud/api 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。