Caching

Add cache=true to /v1/capture, /v1/content or /v1/analyze to store the response. Identical requests within the TTL are served from cache without rendering again.

curl -G "http://localhost:4000/v1/capture" \
  --data-urlencode "url=https://example.com" \
  -d cache=true -d cache_ttl=604800 \
  -H "x-api-key: $SNAPLENS_API_KEY" -D - -o shot.png

The x-cache header

Every cacheable response includes:

Cache keys

The cache key includes the endpoint and all parameters that affect the output (URL, format, viewport, device, selectors, blocking options…). Changing any of them produces a separate cache entry. Your API key is not part of the key, but caches are isolated per workspace.

Billing

A cache hit counts as a successful request and uses one credit, but it returns almost instantly and isn't subject to rendering time.

Choosing a TTL

Forcing a refresh

Omit cache=true to always render a fresh result. The new response doesn't replace the cached entry; send it with cache=true again later to re-populate once the TTL expires.