Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Currently, the Web API has multiple endpoints that support getting multiple objects at once:
These are very useful to avoid hitting the rate limits that would be imposed by repeatedly using these endpoints' single object counterparts.
I think it would be great to add another endpoint similar to the ones listed above, but for playlists - "Get Multiple Playlists". For context, I am developing a web app that involves getting playlist data for many playlists, and I currently have to facilitate all of that through the Get a Playlist endpoint. As a result, I am having to work around rate limiting which isn't ideal.
Let me know what you think!