Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Expose Repeat Listeners in the public API

Abierto
  • ¿Algo no está bien?
#596 2 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
40/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Área
api, backend-api-design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
JavaScript
Estrellas
259
Forks
54
Merge medio
1 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de soundcloud/api

Todos los issues de soundcloud/api

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.