Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Expose Repeat Listeners in the public API

Aperta
  • Qualcosa non va?
#596 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
40/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
api, backend-api-design

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
JavaScript
Stelle
256
Fork
53
Merge medio
1m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di soundcloud/api

Tutte le issue di soundcloud/api

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.