Caching

By default we cache the results of each request you make for 5 minutes or 100 further requests, whichever happens first. If you make the same request again, for example if you have multiple users or multiple clients, we'll serve the cached result and it won't count against your monthly requests. This is useful if you're hooking the API into your app directly (although this isn't recommended because it exposes your API key).

You can identify if a result has been cached by checking the X-Cached-Result header on the API response. If the X-Cached-Result header is marked as true then the result is a cached response. The X-Cache-Expires and X-Cache-Remaining headers will also be populated to tell you when the result will expire. The Date header shows you when the request was originally made, so you can use this to calculate current age.

You can disable this functionality on a request level so that the request doesn't return a cached result, nor will it be cached itself. This way the request will always return the freshest data. To do this simply send the X-No-Cache = true HTTP header with your request. You will be able to verify that a response hasn't been cached by checking for the X-Cached-Result = false header on the response.


Sources Client libraries