Response Headers
RenderScreenshot includes useful HTTP headers with every response.
Standard Headers
Content-Type
The MIME type of the response:
Content-Type: image/png Content-Type: image/jpeg Content-Type: image/webp Content-Type: application/pdf
Content-Length
Size of the response body in bytes:
Content-Length: 245632
Custom Headers
X-Cache-URL
A public CDN URL for the screenshot that requires no authentication:
X-Cache-URL: https://cdn.renderscreenshot.com/screenshots/abc123.png
Use this URL for public embedding without exposing your API key.
X-Request-Id
Unique identifier for the request (useful for debugging):
X-Request-Id: req_1234567890abcdef
X-Cache-Status
Whether the response was served from cache:
X-Cache-Status: HIT X-Cache-Status: MISS
X-Render-Time
Time taken to render the screenshot (in milliseconds):
X-Render-Time: 1234
Only present when X-Cache-Status: MISS.
Rate Limit Headers
X-RateLimit-Limit
Your rate limit per minute:
X-RateLimit-Limit: 60
X-RateLimit-Remaining
Requests remaining in the current window:
X-RateLimit-Remaining: 45
X-RateLimit-Reset
Unix timestamp when the rate limit resets:
X-RateLimit-Reset: 1705312800
Cache Management Headers
These headers are returned by the cache management endpoints.
X-Cache-Key
The full storage key for the cached screenshot:
X-Cache-Key: screenshots/abc123
X-Cache-Hit
Indicates the response was served from cache:
X-Cache-Hit: true
X-Cache-Expires
ISO 8601 timestamp when this cache entry expires:
X-Cache-Expires: 2024-01-19T00:00:00Z
Based on the TTL configured when the screenshot was captured (default: 24 hours).
See Also
- Caching - How screenshot caching works
- Response Formats - Image and PDF response formats
- Rate Limits - Rate limit details by plan
- Cache Management - Retrieve, delete, and purge cached screenshots