Need some clarification on Caching


From what I’ve read in the documentation, Twitter recommends using caching to help with the REST API rate limits.

“We recommend that you cache API responses in your application or on your site if you expect high-volume usage. For example, don’t try to call the Twitter API on every page load of your hugely popular website. Instead, call our API once a minute and save the response to your local server, displaying your cached version on your site. Refer to the Terms of Service for specific information about caching limitations.”

Can our ‘caching’ call be done on our server to the Twitter REST API, updating every minute or so (to remain below the rate limit), then from our clients’ sites, our code will request the cached results and displayed according to the Twitter Display rules?


It’s best to ask a question like this to our platform operations team at

In a scenario like this, you’re possibly in danger of resyndicating Twitter content (which is against the terms of service) to your clients by transmitting it to them instead of them requesting it directly from Twitter.


Thanks for the reply, I’ll ask the platform operations team.