-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can we pay for a rate limit increase? #284
Comments
Caching is not allowed by the ToC of the api. |
The same thing is what we are searching for: is there a paid option that we can use? |
@antoinerousseau Did you get any updates on paid api ? |
Hi there - we do offer paid API access with our extended partner API - please reach out to our support and they will redirect you to start the conversation with our Business Development team. |
I raised a ticket with the support team but haven't received any reply for a long time |
Fyi, I received this two weeks ago:
|
2 months later: absolutely no answer to my emails, wtf? |
Hi, I searched our ticket system, but couldn't find the ticket - would you mind just providing the ticket ID? Nobody can use it outside of our system, so should be safe... |
Hi @MariaVWSoundCloud, my ticket number is 2799664 ![]() Feel free to start a discussion with me at [email protected] Thanks! |
Hi 👋🏼
We're using your API and it's great! It allows our users to play the most popular song of an artist in our app, which is great for people browsing events and wanting to have an idea of the music style and mood before going.
Thing is, our player is getting popular and we now reached 20k+ stream requests per day, which means only the first 15k work, and the rest get rejected by the
429 Too Many Requests
. Fair enough.Now, I was wondering if there was any way we could get a bigger quota?
I'm also considering caching the stream on our side but it seems tricky (and I'm not sure it's even allowed).
Thanks for your help and for the awesome API!
Antoine at shotgun.live
The text was updated successfully, but these errors were encountered: