Authentication
ScreenshotAPI authenticates requests via API keys. Pass your key as a Bearer token or as the access_key query parameter.
Every request must include a valid API key. Find yours in the Dashboard → API Keys section.
Option 1: Authorization header (recommended)
Pass your key as a Bearer token in the Authorization header. This keeps the key out of server logs and browser history.
Authorization: Bearer YOUR_API_KEYOption 2: Query parameter
Append access_key=YOUR_API_KEY to the request URL. Convenient for quick testing but avoid in production as keys can appear in logs.
https://screenshotcore.com/api/v1/screenshot?access_key=YOUR_KEY&url=https://example.comNote: The API key must be in the header or query string — passing it inside a JSON or form body is not supported. All other capture parameters can be passed in any format.
Requests with a missing or invalid key receive 401 Unauthorized.
Code Examples
# Option 1: Bearer token header (recommended)
curl "https://screenshotcore.com/api/v1/screenshot?url=https://example.com" \
-H "Authorization: Bearer YOUR_API_KEY" \
--output screenshot.png
# Option 2: Query parameter
curl "https://screenshotcore.com/api/v1/screenshot?access_key=YOUR_API_KEY&url=https://example.com" \
--output screenshot.pngResponse
(Raw bytes, Content-Type: image/png. Headers: X-Response-Time, X-Cache, X-Request-Id)