I am experiencing the same issue. Their API appears to incorrectly ignore the query ('q') parameter when determining a server-side cache hit/miss. The other API parameters, such as 'fields' or 'limit', will correctly influence the cache. You can ver...