Cache

We have a builtin caching layer for speed up consecutive API calls based on query parameters.
The first time you query for a resource that not was previously served, it will be created, what is known as cache MISS.
The cache status is reflected using the response header as x-cache-status.
curl -I -s -X GET https://api.microlink.io?url=https://www.reddit.com | grep -i "x-cache-status"
The successive requests for the resource will consume the cached version of the resource, what is known as cache HIT.
curl -I -s -X GET https://api.microlink.io?url=https://www.reddit.com | grep -i "x-cache-status"
The period of time the resource is cached is known as Time To Live (ttl) and it specifies the maximum quantity of time the resource will served from cache.
You can see the remain time before ttl expiration as x-cache-expired-at in the reponse headers.
curl -I -s -X GET https://api.microlink.io?url=https://www.reddit.com | grep -i "x-cache-expired-at"
Also, ttl is properly reflected as cache-control response header to tell browsers how much time they can serve the same resource until refresh it.
If you want to bypass and get a fresh response, you can use force for regenerating the cache copy without waiting ttl expiration time.

Cache

We have a builtin caching layer for speed up consecutive API calls based on query parameters.
The first time you query for a resource that not was previously served, it will be created, what is known as cache MISS.
The cache status is reflected using the response header as x-cache-status.
curl -I -s -X GET https://api.microlink.io?url=https://www.reddit.com | grep -i "x-cache-status"
The successive requests for the resource will consume the cached version of the resource, what is known as cache HIT.
curl -I -s -X GET https://api.microlink.io?url=https://www.reddit.com | grep -i "x-cache-status"
The period of time the resource is cached is known as Time To Live (ttl) and it specifies the maximum quantity of time the resource will served from cache.
You can see the remain time before ttl expiration as x-cache-expired-at in the reponse headers.
curl -I -s -X GET https://api.microlink.io?url=https://www.reddit.com | grep -i "x-cache-expired-at"
Also, ttl is properly reflected as cache-control response header to tell browsers how much time they can serve the same resource until refresh it.
If you want to bypass and get a fresh response, you can use force for regenerating the cache copy without waiting ttl expiration time.

By using this website you agree to ourprivacy.