Zendesk REST APIs, Rate limiting, and Caching Zendesk Guide/Help Center Data

Hello,

My team is in the process of architecting a help center using several help center/guide Zendesk REST APIs (e.g., articles, categories, sections, votes, search) in our mobile application. Zendesk API documentation reference: https://developer.zendesk.com/api-reference/help_center/help-center-api/introduction/

While we intend to optimize the number of API calls to Zendesk, we are concerned about 1) frequently reaching Zendesk rate limits with our current enterprise license and 2) high network traffic. Per Zendesk best practices documentation for avoiding rate limiting (https://developer.zendesk.com/documentation/ticketing/using-the-zendesk-api/best-practices-for-avoiding-rate-limiting/#reducing-the-number-of-api-requests), caching the help center data is a solution we are considering.

To avoid overloading the Zendesk help system, our architecture team is thinking about fetching and caching help center content once every 24 hours on our severs. From here, the mobile client will fetch the data instead of the Zendesk backend.

Questions:

1. Has anyone else solved for a similar problem with this approach? If so, what challenges did you face?

2. Are there other solutions to this problem that others have successfully implemented?