Today I encountered a rate limit issue even though I had configured my own Spotify API key in Customily. After reviewing Spotify’s official documentation and community reports, I’d like to share the following insights and a suggestion for improvement: 🔍 Background & Limitations Spotify API uses a rolling 30-second rate limit window. If too many requests occur within any 30-second period, it returns an HTTP 429 error (Too Many Requests). While the exact limits aren’t officially published, developers generally observe: Per user token: Up to 100 requests/hour Per application token: Up to ~25 requests/second 💡 Suggestion to Improve Stability To enhance the stability of the Spotify music component in Customily, I believe there are two possible approaches: Request higher rate limits from Spotify (Though approval depends on Spotify and may not be guaranteed.) Allow merchants to configure multiple Spotify API keys If Customily could rotate between multiple keys (e.g., Key A for request 1, Key B for request 2, Key C for request 3...), the overall request frequency per key would be reduced. For example, I’ve already created two Spotify API keys myself, but I currently have to switch them manually — which is inefficient and error-prone. Implementing such rotation logic on the Customily side would significantly reduce rate-limit risks and improve the reliability of the music component for all users.