We are planning to develop an application using the Apple Music API.
We would like to design our system based on the details of the rate limits mentioned below and have a few questions: https://developer.apple.com/documentation/applemusicapi/generating-developer-tokens#Request-Rate-Limiting
- Regarding the Catalog API
(/v1/catalog/*),
we understand that server-side caching is enabled, making it less likely to reach the rate limit. Is this understanding correct? (Excluding the search API) - For APIs like the Library API
(/v1/me/library/*),
where responses vary by user, we assume they are more likely to reach the rate limit. Is this correct? - We plan to implement optimizations to minimize unnecessary API calls. Given this, would the current Music API be able to handle a significant increase in users? (Assuming a DAU of around 100,000 to 1,000,000)
- If the API cannot support this scale, would it be allowed under Apple’s policy to cache responses from the Catalog API (
/v1/catalog/*
) via our proxy server to avoid hitting the rate limit?
The third question is the one we most want to confirm.