The standard HTTP cache control headers are supported by our services.
Clients are recommended to implement/use cache on their side:
•Store frequently/previously fetched resources in a cache
•Use cache control headers in their GET requests to check if a previously fetched resource has been updated since last time, instead of only requesting the full representation at any time
Example:
•Get first representation
→ GET /v2/accounts/12345 ← 200 OK Date: Fri, 30 Sep 2016 13:46:03 GMT eTag: "abcdef" |
•Get resource representation only if it has changed since last time:
oBy eTag
→ GET /v2/accounts/12345 If-None-Match: "abcdef" ← 304 Not Modified |
oBy date
→ GET /v2/accounts/12345 If-Modified-Since: Fri, 30 Sep 2016 13:46:03 GMT ← 200 OK |
