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

Ouverte
  • Quelque chose ne va pas ?
#607 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
Active
Stack technique
javascript
Domaine
api

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
JavaScript
Étoiles
262
Forks
52
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de soundcloud/api

Toutes les issues de soundcloud/api

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.