Which requests count toward the 1,500 per 24 hours stream limit, and how to request higher production limits?

Offen
  • Stimmt etwas nicht?
#607 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
api

Rechercherichtung

Start with the repository's Rate Limits page, which the issue cites, and check whether it explains which stream requests count, the daily window, remaining quota headers, and how production apps request higher limits. The issue does not name a documentation file or test. Done means the page answers those questions accurately, including the application requirements.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hi,

I run a small music website (evanvandoren.com) that plays my own SoundCloud tracks through a registered app using client credentials. I'd like to confirm how the stream limit on the Rate Limits page applies to us before we get close to it.

How we call the API:

  1. GET /tracks/{id}/streams to get the HLS URLs. We cache this response for a week, so it's only 5 to 25 calls a day.
  2. A request to the returned hls_aac_160_url (or hls_aac_96_url / hls_mp3_128_url) with the OAuth header, which gives us a signed playlist link. Those links expire after a few minutes, so we fetch a new one for each play. That's about 500 to 1,000 a day.

Questions:

  1. Do the requests in step 2 count toward the 1,500 per 24 hours limit on GET /tracks/:id/stream(s), or does only the /streams call in step 1 count?
  2. Is that 24-hour window rolling, or does it reset at a fixed time? On both kinds of request, the X-Ratelimit-Limit header we get back is 100 (the per-minute budget). Is there a header that shows how much of the daily stream limit is left?
  3. The page says approved production apps can get up to 10 times these limits. How do we apply, and what do you need from us? Happy to send our client ID by DM.

Our busiest day so far was about 1,100 total requests (steps 1 and 2 together), and we haven't had any 429s. If you count every request, we'd like the higher limit before we reach 1,500.

Thanks,
Evan VanDoren

Vorherrschende Sprache
JavaScript
Sterne
262
Forks
52
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus soundcloud/api

Alle Issues in soundcloud/api

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.