Jun 6
Support Other Paid Music API Keys for Better Stability
Hi Customily Team,
Thank you for your continued support of the music component feature.
We would like to further raise a concern regarding the stability and long-term risk of the Spotify music component.
Currently, the Spotify music component requires a Spotify API key. However, Spotify has clearly stated that the related keys cannot be used for commercial purposes. At the same time, Spotify does not provide a clear paid commercial API key option. In other words, the keys currently being used are essentially test-mode keys.
In the long term, this creates significant uncertainty and risk for the music component.
If Spotify stops supporting test-mode keys one day, or further restricts their usage, the current Spotify music component may be heavily affected. This could impact the frontend user experience, order generation, and production workflow stability.
Therefore, we would like to ask whether Customily could consider supporting other paid and commercially available music API keys, or providing additional music data source/API integration options, in order to improve the long-term stability of music search, song information retrieval, and the overall music component experience.
Our main requests are:
Support paid music API keys other than Spotify;
Support commercially available and long-term usable music data sources;
Reduce the long-term risk caused by relying on Spotify test-mode keys;
Improve the stability of the music component under high-frequency usage;
Reduce frontend experience issues caused by Spotify API limitations or policy changes;
Provide a more reliable and sustainable commercial solution for the music component.
Pending