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

Expose Fan Support contributions and per-supporter engagement in the public API

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

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, openapi
Ambito
api

Direzione di ricerca

Start with the documented API definition in openapi/api.yaml and review the existing /me endpoints, then read related issues #596 and #68 for context. The issue proposes new contribution and supporter endpoints, per-supporter engagement, privacy constraints, or a UI fallback, but does not identify implementation entry points or settle the scope. Done would require an agreed approach that respects the stated privacy limits and documents the resulting API or UI.

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

Descrizione

enhancement

Scope: this is only for my own tracks. Everything below, API or UI, covers only how fans engage with the authorizing artist's own tracks. Nothing about what fans listen to from other artists.

Please expose Fan Support data through a documented public developer API, so artists can build dashboards that connect fan contributions with listening behavior. Access must require OAuth authorization from the artist and must be limited to that artist's own account, own supporters, and own tracks. No data about other artists, and no listening activity on other artists' tracks.

Today Fan Support payments are only visible in the Fan Support Dashboard, and the documented API (openapi/api.yaml) has no endpoints or fields for contributions or supporters. Artists who want to understand and thank their supporters have to copy figures by hand.

Use case

An artist wants to see, per supporter:

  • How much they have contributed (total, count, first and most recent contribution).
  • How they engage with the artist's own catalog: plays, likes, reposts, comments.
  • Which of the artist's tracks they listen to most.

This lets artists find which tracks turn listeners into supporters, thank top supporters personally, and plan releases around what their supporters actually play.

Requested endpoints (artist's own account only)
  1. GET /me/fan-support/contributions: paginated list of contributions received, with amount, currency, timestamp, and supporter (user object, or an anonymous marker when the supporter chose not to be shown).
  2. GET /me/fan-support/supporters: paginated list of supporters with totals (sum, count, first and last contribution date). Ideally sortable by total, matching the public Top Supporters leaderboard.
  3. GET /me/fan-support/supporters/{user_id}/engagement: that supporter's engagement with the artist's own tracks only: play counts per track, likes, reposts, comments, over a stated reporting period.
Privacy
  • Only the authorizing artist can read their own supporters, and only engagement with that artist's own tracks.
  • Supporters who contributed anonymously, or who opted out of the leaderboard, should be returned without identity, or with aggregate engagement only.
  • If per-supporter listening history is not acceptable, an aggregate version would still cover most of the use case: total plays of each of the artist's tracks by their supporters as a group, versus all listeners.
Fallback: build it into the SoundCloud UI

If public API access is not possible, please build this into the SoundCloud UI instead, especially where artists message fans.

The main reason I want this is to start real conversations with supporters. When a fan supports me and I open a DM to thank them, I want to see which of my tracks they actually listen to, so I can open with something personal ("glad you've been playing X on repeat") instead of a generic thank-you. Right now there is no way to know that from the messaging screen or the Fan Support Dashboard.

Concretely:

  • In the DM / Messages screen: when messaging a fan, a small panel showing their top played tracks of mine, plus whether they've liked, reposted, or commented on my tracks, and their Fan Support history with me (total and most recent contribution).
  • In the Fan Support Dashboard: a per-supporter view with contribution history next to which of my tracks they play most, with a "Message" button that opens the DM with that panel, plus a CSV export.

Same privacy limits as above: only my own tracks, only fans who interact with me, anonymous supporters stay anonymous.

Related: #596 (Repeat Listeners, scoped to the artist's own tracks), #68 (broader Insights API access).

SoundCloud documents Fan Support here: https://help.soundcloud.com/hc/en-us/articles/45965135036443-Fan-Support

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.