Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Storing Data

Solved!

Storing Data

I'm building an app to help analyze your Spotify data and at first I wanted to rank possibly thousands of artists on all sorts of metrics. However, the API calls to get all the data for each artist even using the many "get several" endpoints would still be too much for a per user basis, and I would have to store a lot of the data to reduce the API calls. But I'm assuming this gets into some muddy water. So in general, what can I store? I know it usually has to be a user requested and not just a large amount of calls to build your own database. But for every request, is saving album ids, artist ids, and track ids along with album images to create a permanent database still within the realm of possibility? My reasoning is that those are  easily accessible, unlike maybe popularity, similar artists, sound profiles, etc.

Reply

Accepted Solutions
Marked as solution

Hey!

 

Building an app to analyze Spotify data requires optimization to avoid excessive API calls and to comply with the platform's terms of service. Storing album, artist, and track IDs is allowed and useful for reducing repeated calls, while volatile data such as popularity and audio features should be fetched in real-time. Implementing a temporary cache, using endpoints that return multiple resources in a single call, and adhering to the API rate limits are effective strategies. Ensure that data storage is always linked to specific requests from authenticated users and regularly consult Spotify's Terms of Service to ensure compliance.

ribezazSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

View solution in original post

2 Replies
Marked as solution

Hey!

 

Building an app to analyze Spotify data requires optimization to avoid excessive API calls and to comply with the platform's terms of service. Storing album, artist, and track IDs is allowed and useful for reducing repeated calls, while volatile data such as popularity and audio features should be fetched in real-time. Implementing a temporary cache, using endpoints that return multiple resources in a single call, and adhering to the API rate limits are effective strategies. Ensure that data storage is always linked to specific requests from authenticated users and regularly consult Spotify's Terms of Service to ensure compliance.

ribezazSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

The Spotify User Guidelines say:

 

The following is not permitted for any reason whatsoever in relation to the Services and the material or content made available through the Services, or any part thereof:

 

5. "crawling" or "scraping", whether manually or by automated means, or otherwise using any automated means (including bots, scrapers, and spiders), to view, access or collect information, or using any part of the Services or Content to train a machine learning or AI model or otherwise ingesting Spotify Content into a machine learning or AI model;

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Suggested posts