sigma67
API quota values
Recently I've started running into a new error "quota exceeded" when running the tests. The quota limits seem to be hourly as they reset at the full hour.
I think it might be helpful to document the quota unit and limit values, if somebody can find documentation on it or wants to reverse-engineer the values.
To reverse engineer, I would recommend the following procedure:
- set up oauth authentication
- repeatedly call the same endpoint until the quota is exhausted while counting calls (i.e. until an error is returned by the API)
- wait until the full hour to receive quota
- keep going until quota is exhausted for the day (if at all)
Repeat the procedure with all available endpoints. We're mostly interested in manipulation (creation, edit, delete operations), as read operations aren't usually expensive on the server. Although it could still be interesting to determine if there is a quota for search, for example. In my personal experience the quota for search is probably quite high, as you can do at least several hundreds of searches without issue.
I am choosing this project for the open source course I'm taking for school. I'd love to help with this issue.
Sure, I think this is quite a good issue for new contributors. You can get started by writing a small script and testing some playlist manipulation functions with your account to see if you run into any limits.
@jahenner did you find anything?
I'm intending to use this project to make 2700 requests (search and then rate song for 1340 songs to transfer my spotify library). I'm not sure how well that will play with the ratelimits to I want to confirm it before trying
