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

Aperta
#607 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
api

Direzione di ricerca

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.

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

Descrizione

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

Lingua principale
JavaScript
Stelle
262
Fork
52
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

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.